Best Way To Network F13 & F14 Machines

meh101 · #1 13th March 2011, 04:03 AM

Greetings,

I've reported a bug that results in a Gvfs crash when I attempt to mount Windows shares on a laptop running F14 and a PC running F13. I get the same crash on either machine, but can access Windows shares on a third machine running XP.

Is there a better way than using SAMBA to access my home directory from one Fedora machine to the other? It occurred to me that there might be a better way to do this but most of the guides I've been able to find use static IPs instead of DNS. Thanks for your insights.

kurtdriver · #2 13th March 2011, 04:27 AM

I'd set up ssh servers to connect two computers together, this is not difficult. Search the forum and net for howtos. You can connect from one fedora to another and forward X11, meaning you can not only access that computer, but also run programs on that computer. Just run Nautilus and you've got a file browser window on the other machine. I haven't done this in several years, but the net is full of stuff on it.

There's also the Network File Sysytem, (NFS), and probably a couple of other options.

Linux has been designed over networks, so this is something it does quite well.

#3 13th March 2011, 05:07 AM

Dropbox for Linux and Windows works great.

meh101 · #4 14th March 2011, 02:15 AM

Thanks for the ideas kurtdriver and motnahp00. I'll investigate them.

jpollard · #5 14th March 2011, 02:41 AM

Quote:

Originally Posted by meh101

Greetings,

I've reported a bug that results in a Gvfs crash when I attempt to mount Windows shares on a laptop running F14 and a PC running F13. I get the same crash on either machine, but can access Windows shares on a third machine running XP.

Is there a better way than using SAMBA to access my home directory from one Fedora machine to the other? It occurred to me that there might be a better way to do this but most of the guides I've been able to find use static IPs instead of DNS. Thanks for your insights.

Of course there is.

Use NFS.

SAMBA does not preserve security. It has to map what MS considers security into the POSIX environment supported by Linux. Needless to say, it is not a 1-1 mapping. A lot of Linux capabilities (ie. security) are dropped.

Doing two mappings (POSIX->SMB->POSIX) only gets you the lowest common denominator.

NFSv4 provides the complete mapping.