[ale] Sanba strangeness
Tom Younker
twins at atlnet.com
Thu Jun 7 22:22:04 EDT 2001
All:
I'm stumped.
Caldera's eServer 2.3
Apache / PHP works fine out of the box.
Added Samba, it was working fine.
Added pmfirewall all was still fine.
Added a 2nd NIC (different brand) and got IP masq going.
Now, Samba doesn't work. I noticed in pstree this entry "smbd - smbd"
and added the second interface to smb.conf. Then pstree showed the
usual "smbd". Server still not found.
Disabling the firewall didn't help.
Step 3 of the "Diagnosing Your Samba Server" document fails with this
message:
-----------------------------------------------
#smbclient -L SERVER
Added interface ip=165.121.250.162 bcast 165.121.250.191 nmask
255.255.255.224
error connecting to 208.49.167.83:139 (connection refused)
connection to SERVER failed
-----------------------------------------------
Where did 208.49.167.83 come from ? Traceroute ends with "exodus.net",
then "sd3.mailbank.com"
What is going on here ?
Thanks,
Tom
--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.
More information about the Ale
mailing list