Samba between XP and OS X 10.3.4

[Guest]

I'm having a horrible problem trying to connect my Mac to my PC running XP Home. File and printer sharing is enabled on the PC, and the network names are the same for the Mac and PC, but every time I try to connect through Samba on the Mac I get an error stating that I've entered the wrong username and password. This error, however, comes up even though I haven't been asked to authenticate. I've checked my Mac Keychain (where passwords are stored) and the old login/password isn't in there. I've tried all variations on the connection line (i.e. smb://computername/share, smb://login@computername, etc.), and upon further investigation into the terminal (comand prompt) I get this response when connecting: NT_STATUS_BAD_NETWORK_NAME I'm completely at a loss here.

On the flipside, if I turn on Windows File Sharing on my Mac and try to connect from my PC using the Add Network Place Wizard, I get the error "The folder you entered does not appear to be valid" even though I am entering the server info correctly (\\ip\share). I have opened up the correct ports for connections through ZoneAlarm and the internal firewall for my Mac... I HATE NETWORKING!

 

[GTS]

XP Home uses the guest logon for filing sharing, which by original default
has no password. I'm not all that familiar with the Mac, but wonder if
creating an account called guest might help.

If on the PC you run Start \\MacComputerName (rather than the wizard), what
error (if any) is then reported? How about
net use \\MacName\Sharename in a cmd prompt?
--

I'm having a horrible problem trying to connect my Mac to my PC running XP

Home. File and printer sharing is enabled on the PC, and the network names
are the same for the Mac and PC, but every time I try to connect through
Samba on the Mac I get an error stating that I've entered the wrong username
and password. This error, however, comes up even though I haven't been
asked to authenticate. I've checked my Mac Keychain (where passwords are
stored) and the old login/password isn't in there. I've tried all
variations on the connection line (i.e. smb://computername/share,
smb://login@computername, etc.), and upon further investigation into the
terminal (comand prompt) I get this response when connecting:
NT_STATUS_BAD_NETWORK_NAME I'm completely at a loss here.

On the flipside, if I turn on Windows File Sharing on my Mac and try to

connect from my PC using the Add Network Place Wizard, I get the error "The
folder you entered does not appear to be valid" even though I am entering
the server info correctly (\\ip\share). I have opened up the correct ports
for connections through ZoneAlarm and the internal firewall for my Mac... I
HATE NETWORKING!

 

[Guest]

I tried both methods and I get "System error 53 has occured. The network path was not found." (by using both the computer name and IP, with and without the sharename). While I was there I double checked connectivity by pinging the Mac, and it goes through fine.

By the way, I realized the solution to the first part of my problem there, it seems I had NetBIOS disabled (the third option in TCP/IP settings) rather than on the first option (sometimes enabled or something...). Fixed the problem in a snap.

 

[GTS]

Good thinking re. the first error.

Error 53 generally indicates a name resolution or connectivity issue (as
contrasted to the other common error 5 involving permissions). Sorry, but
I don't know enough about Mac's to be of help at this point. Perhaps this
link will be of some interest-
http://www.macwindows.com/OSXServer.html It seems to address some common
issues along these lines.

--

I tried both methods and I get "System error 53 has occured. The network

path was not found." (by using both the computer name and IP, with and
without the sharename). While I was there I double checked connectivity by
pinging the Mac, and it goes through fine.

By the way, I realized the solution to the first part of my problem there,

it seems I had NetBIOS disabled (the third option in TCP/IP settings) rather
than on the first option (sometimes enabled or something...). Fixed the
problem in a snap.