Re: [Samba] what's on port 139
Reply to list firewall setings try run ipchains -L -n Bye. - Original Message - From: Andrew Greenhill [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, February 24, 2003 11:07 AM Subject: [Samba] what's on port 139 Having trouble with Samba. The config file passes the test (testparm) The Server seems to be upa and running fine (smbclient -L localhost) But can't seem to connect to it from other computers (running 2000 or 98) They were able to connect once though. What should be listed on port 139 in services. We have : netbios-ssn Does this sound right? Appreciate any help/suggestions!! Regards, Andrew -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] what's on port 139
On Mon, 2003-02-24 at 05:07, Andrew Greenhill wrote: Having trouble with Samba. The config file passes the test (testparm) The Server seems to be upa and running fine (smbclient -L localhost) But can't seem to connect to it from other computers (running 2000 or 98) They were able to connect once though. What should be listed on port 139 in services. We have : netbios-ssn Does this sound right? Appreciate any help/suggestions!! Regards, Andrew 139 should be the nmbd maybe it's a name resolution problem are you using wins on your clients? i recommend you do. did you tell samba the location of the wins server? did you install samba as the wins server when there is already a wins server on the lan? (ie set wins support = yes) what does log.nmbd say? brad -- Bradley W. Langhorst [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] what's on port 139
What do you see with : netstat -anp | grep mbd Joel Having trouble with Samba. The config file passes the test (testparm) The Server seems to be upa and running fine (smbclient -L localhost) But can't seem to connect to it from other computers (running 2000 or 98) They were able to connect once though. What should be listed on port 139 in services. We have : netbios-ssn Does this sound right? Appreciate any help/suggestions!! Regards, Andrew -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] what's on port 139
Firewall issue? Joel On Mon, Feb 24, 2003 at 10:07:24AM +, Andrew Greenhill wrote: Having trouble with Samba. The config file passes the test (testparm) The Server seems to be upa and running fine (smbclient -L localhost) But can't seem to connect to it from other computers (running 2000 or 98) They were able to connect once though. What should be listed on port 139 in services. We have : netbios-ssn -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] what's on port 139
Yes, this looks ok. Firewall issue? Joel On Mon, Feb 24, 2003 at 11:39:54AM +, Andrew Greenhill wrote: I get: tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 28032/smbd udp 0 0 192.168.2.31:137 0.0.0.0:* 28034/nmbd upd 0 0 0.0.0.0:137 0.0.0.0:* 28034/nmbd upd 0 0 192.168.2.31:138 0.0.0.0:* 28034/nmbd udp 0 0 0.0.0.0:138 0.0.0.0:* 28034/nmbd -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] what's on port 139
On Mon, 2003-02-24 at 06:44, Andrew Greenhill wrote: Looked up in the nmbd.log and it tries to become the domain master for subnet 192.168.2.31 (we wanted it to be the domain master for 192.168.2.0) Would this be a problem? unless you're using an unusual subnet mask these are on the same subnet... so no i don't think this is the problem... you didn't answer my wins questions. this smacks of a a name resolution problem - or maybe a firewall problem try making samba the wins server (or point it to another wins server) and make sure that the clients all reference the same wins server. brad -- Bradley W. Langhorst [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
