[andy@fw andy]$ echo "hello" | telnet 192.168.4.1 139
Trying 192.168.4.1...
Connected to 192.168.4.1.
Escape character is '^]'.
Connection closed by foreign host.
[andy@fw andy]$ echo "hello" | telnet 64.218.*.*
Trying 64.218.*.*...
Connected to 64.218.*.*.
Escape character is '^]'.
Connection closed by foreign host.
[andy@fw andy]$
Originally I got one of the messages being connection refused for an
external interface, I fixed the interface line and now I get a connection
closed with every try.
Here is the global section of the smb.conf for 192.168.3.1 with external
address of 64.217.*.*. This is the one that is functioning as the wins
server:
[global]
client code page = 950
workgroup = Irish
netbios name = fw-server
server string = e-smith samba server
hosts allow = 127.0.0.1 192.168.3.0/255.255.255.0
192.168.4.0/255.255.255.0 64.218.*.*
interfaces = 127.0.0.1 192.168.3.1/255.255.255.0 64.217.*.*
log file = /var/log/samba/log.%m
max log size = 50
security = user
guest ok = yes
guest account = public
map to guest = bad user
encrypt passwords = yes
smb passwd file = /etc/smbpasswd
socket options = TCP_NODELAY
strict locking = yes
bind interfaces only = yes
remote browse sync = 192.168.4.1
remote announce = 192.168.4.1
local master = yes
os level = 33
domain master = yes
preferred master = yes
browseable = yes
name resolve order = wins lmhosts bcast
wins support = yes
dns proxy = no
preserve case = yes
short preserve case = yes
case sensitive = no
debug level = 3
domain logons = yes
logon script = netlogon.bat
printcap name = /etc/printcap
load printers = yes
Here is the global portion for the 192.168.4.1 machine with external
interface of 64.218.*.*:
[global]
client code page = 950
workgroup = msp
netbios name = e-smith-server
server string = e-smith samba server
hosts allow = 127.0.0.1 192.168.4.0/255.255.255.0
192.168.3.0/255.255.255.0 64.217.*.*
interfaces = 127.0.0.1 192.168.4.1/255.255.255.0 64.218.*.*
log file = /var/log/samba/log.%m
max log size = 50
security = user
guest ok = yes
guest account = public
map to guest = bad user
encrypt passwords = yes
smb passwd file = /etc/smbpasswd
socket options = TCP_NODELAY
strict locking = yes
bind interfaces only = yes
remote browse sync = 192.168.3.1
remote announce = 192.168.3.1
local master = yes
os level = 33
domain master = yes
preferred master = yes
browseable = yes
name resolve order = wins lmhosts bcast
wins server = 192.168.3.1
dns proxy = no
preserve case = yes
short preserve case = yes
case sensitive = no
debug level = 3
domain logons = yes
logon script = netlogon.bat
printcap name = /etc/printcap
load printers = yes
TIA
Andy
----- Original Message -----
From: "Avantel Systems" <alex@avantel.ca>
To: "Andy Worthington" <andy@rockcity.com>
Cc: <samba@samba.org>
Sent: Thursday, October 26, 2000 6:11 PM
Subject: Re: browsing across subnets
Try this;
from a host on one network to the other subnet
echo hello | telnet remote-server-ip 139
where the remote-server-ip is the ip address of the remote samba server (use
the internal (private) address and try again with the external ip address.
if you get Connection refused, then;
either you're blocking the ports (firewall?)
or samba is not listening on the external interface (see interface option)
If, on the other hand you get a "Connected" message followed by
"Connection closed" message, then;
the problems is something else.
Try that & let me know what happens
Alex @ Avantel
On Thu, 26 Oct 2000, you wrote:> I have changed around settings several times, right now each is the domain
> master browser, local master and preferred, one is setup as the wins
server> with all clients and the other samba server set to use it for wins. In
its> wins.dat file there is an entry for the other samba server and a client on
> the other subnet setup to use it as wins but no one can see the second
> workgroup on the subnet where the wins samba server resides. From that
> machine when I try this for the non-wins samba server:
>
> smbclient -L server
>
> I get this:
> added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
> added interface ip=192.168.3.1 bcast=192.168.3.255 nmask=255.255.255.0
> Got a positive name query response from 127.0.0.1 ( 192.168.4.1 )
> session request to SERVER failed (Not listening for calling name)
> Got a positive name query response from 127.0.0.1 ( 192.168.4.1 )
> session request to *SMBSERVER failed (Not listening for calling name)
>
> 192.168.4.1 is the correct IP for that server.
>
> Any idea what to try next?
>
> Thanks
> Andy
>
> ----- Original Message -----
> From: "Avantel Systems" <alex@avantel.ca>
> To: "Andy Worthington" <andy@rockcity.com>
> Cc: <samba@samba.org>
> Sent: Wednesday, October 25, 2000 6:16 PM
> Subject: Re: browsing across subnets
>
>
> You need to make both samba servers domain master browsers. And you're
> right
> about the wins server - disconnects can cause odd behaviour - especially
> since
> samba cannot (yet?) be a secondary wins server.
>
> Alex @ Avantel
>
> On Wed, 25 Oct 2000, you wrote:
> > I've read through the BROWSING*.txt files in docs/textdocs and I
think I
> set
> > everything up right but I can't get this to work.
> >
> > I am using IPSEC to connect two lans that are seperated by the
internet
> and
> > use dsl lines for internet connection. That is setup and working. I
can> > ping from a client on one subnet to a client on another subnet with no
> > problems. One subnet is 192.168.3.0 and the other is 192.168.4.0
> >
> > The 192.168.3.0 subnet has the workgroup of irish and the 192.168.4.0
has> > the workgroup of msp.
> >
> > I want both of these subnets to see both workgroups. All clients are
> win98
> > and there is a samba server on each network that is also doing the
ipsec
> and
> > acting as the firewall(currently setup to accept everything). Each
subnet> > has the samba server setup as the WINS server for that subnet.
> >
> > in the smb.conf file on 192.168.3.1 I added:
> >
> > remote browse sync = 192.168.4.1
> > remote announce = 192.168.4.1
> >
> > and on 192.168.4.1 I added:
> > remote browse sync = 192.168.3.1
> > remote announce = 192.168.3.1
> >
> > Any ideas how to solve this so that each subnet can see and use both
> > workgroups. Another question about the WINS servers, I read that it
is
> best
> > if only one is used for both subnets. If I do this and the link
drops,
> the
> > subnet without samba setup for wins will of course no longer have a
wins
> > server. Will this Win98, ME clients automatically start using
broadcast
> > based name resolution when the WINS server becomes inaccessable?
> >
> > TIA
> > Andy Worthington
