Hi all I followed the steps given in chapter 10 for getting cross-subnet to
work.
However, the samba server can see the fileshares in the workgroup
but the computers in the other subnet can't see the samba share.
Here's the setup: I'm using a router to share an internet connection between a
Hi all,
I've had cross-subnet browsing working in Samba in the past, though I
tend to struggle with it each time I set it up. For whatever reason, I
can't seem to get things working this time.
Summary: Only my desktop, not the file server, shows up in the desktop's
Network Neighborhood. (I
Hi
On Fri, 2006-07-14 at 19:42 -0500, Todd Pytel wrote:
Hi all,
I've had cross-subnet browsing working in Samba in the past, though I
tend to struggle with it each time I set it up. For whatever reason, I
can't seem to get things working this time.
Summary: Only my desktop, not the
Craig White wrote:
I believe what you want is 'remote announce' - you can get a good
definition of it's usage in the man page for smb.conf
I've tried that as well (using remote announce = 192.168.0.255), but it
didn't seem to make any difference. That might be a routing issue - I
didn't
On Fri, 2006-07-14 at 20:17 -0500, Todd Pytel wrote:
Craig White wrote:
I believe what you want is 'remote announce' - you can get a good
definition of it's usage in the man page for smb.conf
I've tried that as well (using remote announce = 192.168.0.255), but it
didn't seem to make
Craig White wrote:
you probably don't need that option if the clients know where to find
the WINS servers (probably can set multiple WINS servers in DHCP
configuration)
Yeah, the WINS server (which is just the single Samba server) is named
in the DHCP options, so the Windows desktops are
Todd Pytel wrote:
Yeah, the WINS server (which is just the single Samba server) is named
in the DHCP options, so the Windows desktops are set up for it
automatically. Again, all the name resolution works fine - the desktop
can successfully view \\aristotle\username and do nblookups.
Any
Anthony Messina wrote:
Todd Pytel wrote:
Yeah, the WINS server (which is just the single Samba server) is named
in the DHCP options, so the Windows desktops are set up for it
automatically. Again, all the name resolution works fine - the desktop
can successfully view \\aristotle\username and do
Todd.
I already used samba in network with more than one segment and never
needed any remote ... option too, it worked even through a VPN. The
samba books says to use that options when more than one WINS server are
used, for example. Using the same WINS server in both networks, the name
Edmundo,
Edmundo Valle Neto wrote:
I already used samba in network with more than one segment and never
needed any remote ... option too, it worked even through a VPN. The
samba books says to use that options when more than one WINS server are
used, for example. Using the same WINS server
10 matches
Mail list logo
