Fix Alias

If you install an XP service pack that may change the XP firewall settings. Do you have a firewall on the XP?

Also there is a known problem when the server has multiple adapters and you connect via Finder->Network or smb://computername.

What happens if you try to connect via Finder->apple-k->

smb://server ipaddress

or smb://server dnsname

I'm having the exact same problem and can't figure out what the problem is. What he was referring to was command +K, which lets you connect by using smb protocol to link to your computer. But I have also attempted to do it that way and I get a error code -41 or -36. I was using mine fine also until this morning when I attempted to connect to it, it didn't work. Anyone know how to delete the alias or fix it?

I have never been able to "fix" an alias by using that option. Please check the firewall settings to make sure that ports 137 and 139 are enabled, and that the "scope" is appropriate. If the 2 machines are in different subnets, even if 137 and 139 are enabled, if the scope is local subnet only, you will have a problem.

They are all on the same subnet, they are on one router, and I checked the firewall ports and everything seems ok. Any other ideas, because this happened overnight and I didn't change anything prior to this happening. And it did work before without any problems.

On the client machine in a teminal window type

smbclient //servername/sharename -U user%password

If that works, look in Finder->applications->utilities->console->logs

look at the Console Log and System Log for words with "SMB" in them, like mount_smbfs

If smbclient doesn't work there may be a server problem or cable problem.

There are many different problems that can cause a -36 or -41 error in Finder.

This issue has been the bane of my life for the last couple of months and I had hoped a quick and easy solution had appeared - not so it would seem.
I had to reinstall WindowsXP Pro SP2 on our home server last night and had also just installed Tiger on a G4 Powerbook. Interestingly 10.4.2 didn't break the networking - one of the Windows updates actually caused it to break.
For most of the day I had access between both Mac/PC and then just as I was doing the final 9 updates to XP (Pro) it started happening - I don't have a list of which of these updates are but I would assume the they fixed a security bug in XP, but also caused some issue with how OSX authenticates itself to the machine. PC->Mac has always worked but the other way just left the 'beachball of annoyance' and eventually a fix alias message.

I tried the terminal command and it logged in to my XP laptop no probs, doing an LS listed the correct contents of the shared folder also.
As this worked I went back to Finder->Network->Workgroup->RED (my laptop) and pressed connect... Beachball occours.
So I can login via termain but not via finder. After having a look in the console log it reports -
mount_smbfs: negotiate phase failed: syserr = Operation timed out
Under system.log it reports a few errors (308,313,354,371) all basically saying
/usr/sbin/smbd getnameinfo(): Non-recoverable failure in name resolution.

The terminal window itself reports
init_iconv: Conversion from UTF-16LE to CP0 not supported
It then tries about 14 different conversions until its happy on ASCII to ASCII at which point it logs in and sits at smb: \>

So although it would seem its windows that causes it (see previous post) OSX can still log in, just not in the much easier Finder interface.

Could be packet signing. Do you have the setting on XP: digitally sign communications - always?

I think my apple ID might be expiring so, this could be my last post here.

I've discoverd the same thing. I noticed that this problem happened after an update one night, but I'm not sure what update it was. So I can't fix it. Also, the system log says that it can't allocate enough memory. Wierd!

Ah, that could be the mysterious "insufficient server resources" error that Windows returns sometimes. If it's that problem, some users have been successful in tweaking server resources in the registry, others unsuccessful.

I'm confused - what exactly is this "insufficient server resources" windows error you talk of - I'm far more experienced in Winblows networking and have never come accross this problem.
As I mentioned Terminal can log into the smb share without a problem - its finders networking interface that doesn't like it. I'm surprised more ppl reported this issue - every Tiger Mac I get my hands on have problem.

re: insufficient resources...
You say every Tiger...
...or every Tiger that connects to this server has this problem?

Do you have Norton or Symantec 'anything' running on the server?
What verison (Enterprise? Internet Security...you know the routine)

If so, Try stopping and Starting AntiVirus Service.
Also, while you're in Services control panel, turn off ComputerBrowser srvice on the XP. (Stop the service and set it to manual)
Probably reboot XP
Reconnect.

Are your computers member of the same workgroup?
Got shared folder to see when you get there to the XP?
File and Print Sharing turned on?
Dumb XP questions, but I have to ask.

One more thing - you say 'you used to be able to connect with no problem...'

What changed on your network? Win Updates? Mac Updates? new antivirus? Server need a reboot? Firewall change on XP?
Questions only you know the answers to..:)