Hello Eric,
I wouldn't be concerned that telnet computername 137 does not work;
in fact I would expect you to get a connection refused.
If nmbd shows up in your ps listing, and if you look at the log file
log.nmbd and it DOESN'T complain about being unable to bind to 137,
then it's up!
Hope this helps,
Don
PS - You should also be able to do the simple test
nmblookup <sambaservername> and get a response....
-----Original Message-----
From: Eric Boucher [mailto:eric_boucher60@yahoo.com]
Sent: Thursday, May 10, 2001 8:45 AM
To: SAMBA
Subject: No response from the port 137
Hi everyone,
I have a big problem. My two samba daemons are started
in my init.d directory. I can see that they are
started with the "ps" command. But when I try to do a
telnet on the port 137, it didn't want to connect. I
read that if you cannot telnet and connect on the 2
ports, this mean that samba daemon is not started (the
ports 139 works!). But what I don't understand is that
I can see it with the "ps" command (the daemons are
started with the -D options).Can somebody help me?
Thanks
Eric
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba