smblient Error When Trying To Connect To XP

Psibur · 08-06-2005, 09:24 PM

When I was connecting to a XP box with Service Pack 1 and a FAT32 drive, smbclient worked just fine out of the box. Now when I try to get to a XP box with Service Pack 2 (SP2) with both a FAT32 and a NTFS partition, I get the following error message after it prompts me for a password:

Quote:

"tree connect failed: NT_STATUS_BAD_NETWORK_NAME"

The full dialog looks like:

Code:

added interface ip=192.168.0.5 bcast=192.168.0.255 nmask=255.255.255.0
Password:
Domain=[WORKGROUP] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

To be honest, I don't even think there was an smb.conf, but here is the one I have now (that was created after I first started receiving the error):

Code:

# Samba config file created using SWAT
# from psibur (192.168.0.5)
# Date: 2005/08/06 20:05:42
 
# Global parameters
[global]
        netbios name = PSIBUR
        security = SHARE
 
[data]
        comment = Data
        path = /export
        read only = No
        guest ok = Yes
        hosts allow = 192.168.0.

Is there some issue with SP2 that wants to be fussy with Samba? Here's some info about the XP box:
[] I have the Winderz Firewall turned off to keep that quiet.
[] I don't have the Guest account turned on.
[] The workgroup on the XP box is named WORKGROUP
[] I do not have a user account named PSIBUR. Should I have one?

TIA.
--Psibur

andy753421 · 08-06-2005, 09:31 PM

No, you shouldnt need a account called PSIBUR. Have you tried connecting to the linux (im guessing) machine from the XP machine? or have you tried connecting to the sp2 machine from another windows machine?

Psibur · 08-07-2005, 09:05 AM

Quote:

Originally posted by andy753421
No, you shouldnt need a account called PSIBUR. Have you tried connecting to the linux (im guessing) machine from the XP machine? or have you tried connecting to the sp2 machine from another windows machine?

Okay, this one was just wierd but I figured it out. When I shared the drives, for testing purposes, I named them C (NTFS) and D (FAT32). I went to go and unshare them this morning and noticed after the C and D in the Share Name fields, there was a single $. I removed them and all started working as normal. Never seen this happen before but I guess wierd things happen.

Thanks.

andy753421 · 08-07-2005, 03:27 PM

I believe $C and $D are administrative shares that are put up by windows and are really hard to get rid of. I think there's also a $WINDOWS. Note that these shares are not visible by most smb browsers, namely windows explorer, and must be typed in manually in the form of \\computer\$C.