Adam:
Your suggestions have been great, and have helped me solve a few other problems
on different servers.
Thanks again!
Ryan
>>> Adam Nielsen <[EMAIL PROTECTED]> 12/19/2005 5:49:04 PM >>>
> I can telnet to 139:
Hmm, that's bizarre. It seems like smbd is ignoring the connection on
purpose.
> I can telnet to 139:
Hmm, that's bizarre. It seems like smbd is ignoring the connection on
purpose. I'm afraid I'm out of ideas. You could try adding "hosts
allow = 127." line to smb.conf just in case (along with your other
subnets so they can still access the server) however I don't think it
OK, I've opened port 445 in the iptables config. Further testing shows no
changed after doing this.
I can telnet to 139:
boothost:~# telnet localhost 139
Trying 127.0.0.1...
Connected to localhost.localdomain.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
Trying to smbclient to
> Port 139 is open in the iptables config for both TCP and UDP.
Hmm, I have an additional port open:
tcp0 0 192.168.0.1:139 0.0.0.0:* LISTEN
2694/smbd
tcp0 0 127.0.0.1:139 0.0.0.0:* LISTEN
2694/smbd
Adam:
boothost:~# netstat -lnp|grep smbd
tcp0 0 0.0.0.0:139 0.0.0.0:* LISTEN
2968/smbd
Port 139 is open in the iptables config for both TCP and UDP.
Thanks,
Ryan
>>> Adam Nielsen <[EMAIL PROTECTED]> 12/14/2005 4:58:05 PM >>>
Hi Ryan,
> boothost:~# s
Hi Ryan,
> boothost:~# smbclient -L 172.21.23.1 -Uvalidusr
> added interface ip=172.21.23.1 bcast=172.21.23.255 nmask=255.255.255.0
> Password:
> session setup failed: Call timed out: server did not respond after
> 2 milliseconds
>
> Can bad WINS entries affect results even if WINS isn't in t
No such luck:
in smb.conf:
name resolve order = host bcast
Results:
boothost:~# smbclient -L 172.21.23.1 -Uvalidusr
added interface ip=172.21.23.1 bcast=172.21.23.255 nmask=255.255.255.0
Password:
session setup failed: Call timed out: server did not respond after 2
milliseconds
Can bad WINS
> wins.dat should list the IP address for this host as 172.21.23.1.
In this case using -L 172.21... instead of -L BH1230 should work.
There was a post earlier with the subject "Changed IP address" that
recommended editing wins.dat to fix the IP problem.
Cheers,
Adam.
--
To unsubscribe from this
>> I've got a really odd issue -- a Samba server that can "smbclient -L"
>> everyone but itself.
>> session setup failed: Call timed out: server did not respond after
>> 2 milliseconds
> This looks a lot like a firewall issue - are you sure your machine can
> connect to itself on that interfac
> I've got a really odd issue -- a Samba server that can "smbclient -L"
> everyone but itself.
> session setup failed: Call timed out: server did not respond after
> 2 milliseconds
This looks a lot like a firewall issue - are you sure your machine can
connect to itself on that interface on the
Debian Sarge, Samba 2.2.12 (legacy install), openLDAP 2.2.17, connecting to a
PDC running Samba 2.2.8a. The machine in question failed DIAGNOSIS.txt step 3.
I've got a really odd issue -- a Samba server that can "smbclient -L" everyone
but itself. Samba still serves shares and PDC authentication
11 matches
Mail list logo
