Re: called name not present
On Wed, 5 Feb 2003, David Bear wrote: I've encountered a strange error. I have samba 2.2.7 installed on freebsd 4.7. I've run testparm on the smb.conf and don't see any errors. I can connect to a service from a windows 2k machine using standard net use commands. HOWEVER, when I try to use smbclient from another machine to view my bsd samba, I get the following error: bash-2.05a$ smbclient -L //npcenter added interface ip=129.219.120.183 bcast=129.219.120.191 nmask=255.255.255.192 session request to NPCENTER failed (Called name not present) Password: Anonymous login successful Domain=[CUI] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager] tree connect failed: NT_STATUS_DUPLICATE_NAME == Hmmm, I am not aware of any version of Samba claiming to be Windows 5.0 or Windows 2000 LAN Manager. Are you sure that you are connecting to a Samba server, and not, say, a Win2K server by some accident? Regards - Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org, sharpe[at]ethereal.com, http://www.richardsharpe.com
Re: called name not present
On Wed, Feb 05, 2003 at 10:57:10AM -0800, Richard Sharpe wrote: On Wed, 5 Feb 2003, David Bear wrote: I've encountered a strange error. I have samba 2.2.7 installed on freebsd 4.7. I've run testparm on the smb.conf and don't see any errors. I can connect to a service from a windows 2k machine using standard net use commands. HOWEVER, when I try to use smbclient from another machine to view my bsd samba, I get the following error: bash-2.05a$ smbclient -L //npcenter added interface ip=129.219.120.183 bcast=129.219.120.191 nmask=255.255.255.192 session request to NPCENTER failed (Called name not present) Password: Anonymous login successful Domain=[CUI] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager] tree connect failed: NT_STATUS_DUPLICATE_NAME == Hmmm, I am not aware of any version of Samba claiming to be Windows 5.0 or Windows 2000 LAN Manager. Are you sure that you are connecting to a Samba server, and not, say, a Win2K server by some accident? Richard is being polite. :) That definitley shows that you've connected to a W2K machine. The best guess is that the name NPCENTER is in use by both machines, and that the W2K system is answering first when the query goes out (either that, or you are using WINS and the W2K system has registered that name in the NBNS database). The NT_STATUS_DUPLICATE_NAME error code seems to confirm this, but I'm not sure. A tcpdump trace showing ports 137 and 139 would help. Chris -)- -- Samba Team -- http://www.samba.org/ -)- Christopher R. Hertel jCIFS Team -- http://jcifs.samba.org/ -)- ubiqx development, uninq. ubiqx Team -- http://www.ubiqx.org/ -)- [EMAIL PROTECTED] OnLineBook -- http://ubiqx.org/cifs/-)- [EMAIL PROTECTED]
Re: called name not present
On Wed, Feb 05, 2003 at 10:57:10AM -0800, Richard Sharpe wrote: On Wed, 5 Feb 2003, David Bear wrote: I've encountered a strange error. I have samba 2.2.7 installed on freebsd 4.7. I've run testparm on the smb.conf and don't see any errors. I can connect to a service from a windows 2k machine using standard net use commands. HOWEVER, when I try to use smbclient from another machine to view my bsd samba, I get the following error: bash-2.05a$ smbclient -L //npcenter added interface ip=129.219.120.183 bcast=129.219.120.191 nmask=255.255.255.192 session request to NPCENTER failed (Called name not present) Password: Anonymous login successful Domain=[CUI] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager] tree connect failed: NT_STATUS_DUPLICATE_NAME == Hmmm, I am not aware of any version of Samba claiming to be Windows 5.0 or Windows 2000 LAN Manager. Are you sure that you are connecting to a Samba server, and not, say, a Win2K server by some accident? Yes, I thought that was strange as well, yet, here's what nmblookup finds. bash-2.05a$ winsq npcenter querying npcenter on 129.219.13.105 129.219.120.138 npcenter00 Looking up status of 129.219.120.138 NPCENTER00 - M ACTIVE NPCENTER03 - M ACTIVE NPCENTER20 - M ACTIVE ..__MSBROWSE__. 01 - GROUP M ACTIVE NPCGROUP00 - GROUP M ACTIVE NPCGROUP1b - M ACTIVE NPCGROUP1d - M ACTIVE NPCGROUP1e - GROUP M ACTIVE is there a way to use smbclient with an ip address to bypass any name resolution differences that may be happening between windows and unix? -- David Bear College of Public Programs/ASU Mail Code 0803
Re: called name not present
On Wed, Feb 05, 2003 at 12:52:40PM -0600, Christopher R. Hertel wrote: On Wed, Feb 05, 2003 at 11:35:22AM -0700, David Bear wrote: Are you sure that you are connecting to a Samba server, and not, say, a Win2K server by some accident? Yes, I thought that was strange as well, yet, here's what nmblookup finds. bash-2.05a$ winsq npcenter querying npcenter on 129.219.13.105 129.219.120.138 npcenter00 Looking up status of 129.219.120.138 NPCENTER00 - M ACTIVE NPCENTER03 - M ACTIVE NPCENTER20 - M ACTIVE ..__MSBROWSE__. 01 - GROUP M ACTIVE NPCGROUP00 - GROUP M ACTIVE NPCGROUP1b - M ACTIVE NPCGROUP1d - M ACTIVE NPCGROUP1e - GROUP M ACTIVE is there a way to use smbclient with an ip address to bypass any name resolution differences that may be happening between windows and unix? Which host is at 129.219.120.138, a W2K system or the Samba server? Again, a trace would help. The -I option can be used to specify a unicast destination. 129.219.120.138 is the bsdbox -- its the samba server. here's something to add to the plot. 1) my samba server at 129.219.120.183 seems to have a problem correctly resolving the netbios name npcenter. It can connect using the ip address of 129.219.120.138. 2) another samba server in the same subnet correctly resolves the netbios name npcenter -- finds the right machine and connects. 3) another samba server in a differnet subnet/differnet building/differnet broadcast region successfully connects to the npcenter netbios name 4) so it would seem there is a configuration error on my samba machine at 120.183 -- however, the returned line from smbclient -L ... nonymous login successful Domain=[CUI] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager] tree connect failed: NT_STATUS_DUPLICATE_NAME ... would indicate a connection was made to a machine in a TOTALLY different subnet and domain. the CUI domain is in a very different building/different subnet. things are getting curiouser and curiouser.. Chris -)- -- Samba Team -- http://www.samba.org/ -)- Christopher R. Hertel jCIFS Team -- http://jcifs.samba.org/ -)- ubiqx development, uninq. ubiqx Team -- http://www.ubiqx.org/ -)- [EMAIL PROTECTED] OnLineBook -- http://ubiqx.org/cifs/-)- [EMAIL PROTECTED] -- David Bear College of Public Programs/ASU Mail Code 0803
Re: called name not present SOLVED
sorry to trouble the group on this one. The problem was twofold 1) in my smb.conf on machine at 120.183 I hand the entry dns proxy = yes AND 2) a very old and outdated DNS entry that needs to be removed. whoa.. On Wed, Feb 05, 2003 at 12:35:26PM -0600, Christopher R. Hertel wrote: On Wed, Feb 05, 2003 at 10:57:10AM -0800, Richard Sharpe wrote: On Wed, 5 Feb 2003, David Bear wrote: I've encountered a strange error. I have samba 2.2.7 installed on freebsd 4.7. I've run testparm on the smb.conf and don't see any errors. I can connect to a service from a windows 2k machine using standard net use commands. HOWEVER, when I try to use smbclient from another machine to view my bsd samba, I get the following error: bash-2.05a$ smbclient -L //npcenter added interface ip=129.219.120.183 bcast=129.219.120.191 nmask=255.255.255.192 session request to NPCENTER failed (Called name not present) Password: Anonymous login successful Domain=[CUI] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager] tree connect failed: NT_STATUS_DUPLICATE_NAME == Hmmm, I am not aware of any version of Samba claiming to be Windows 5.0 or Windows 2000 LAN Manager. Are you sure that you are connecting to a Samba server, and not, say, a Win2K server by some accident? Richard is being polite. :) That definitley shows that you've connected to a W2K machine. The best guess is that the name NPCENTER is in use by both machines, and that the W2K system is answering first when the query goes out (either that, or you are using WINS and the W2K system has registered that name in the NBNS database). The NT_STATUS_DUPLICATE_NAME error code seems to confirm this, but I'm not sure. A tcpdump trace showing ports 137 and 139 would help. Chris -)- -- Samba Team -- http://www.samba.org/ -)- Christopher R. Hertel jCIFS Team -- http://jcifs.samba.org/ -)- ubiqx development, uninq. ubiqx Team -- http://www.ubiqx.org/ -)- [EMAIL PROTECTED] OnLineBook -- http://ubiqx.org/cifs/-)- [EMAIL PROTECTED] -- David Bear College of Public Programs/ASU Mail Code 0803
