Yesterday Samba was working fine on from this PC, but this morning, after a windows update overnight (the PC had rebooted), I can't access our main Linux server any more using this machine.
If I try and access the share using Windows Explorer, I get
"Window cannot find '\\server\share\'. Check the spelling and try again, or try searching for the item by clicking the Start button and then clicking Search"if I use a command prompt and try:
net use \\server\share /u:timo *
I get prompted for a password, as expected and then get
"System error 58 has occured. The specified server cannot perform the requested operation".
If I try and access another server, which is Solaris based rather than than Linux, and which has an older version of Samba on it, it works fine.
Similarly, if I access my account from another Windows XP box, it can access the Linux server OK. This strongly suggests that it's this specific copy of Windows XP which has gone a bit doolally, but I can't work out what,or why.
If I run smbclient on this machine (using Cygwin) it can access the server fine, as obviously can things like Winscp and Putty, so it must be something in the Windows Networking.
I've checked, and even changed a few of the Registry settings, which typically cause problems with Samba, but haven't got anywhere. I've rebooted umpteen times (which is the normal solution to Windows Networking problems), but that's achieved nothing.
I've uninstalled, and reinstalled Windows Networking, to no avail.
I've Googled around, and found nothing useful, and I'm starting to run out of things to try, as well as run out of time!
The Samba logs, as ever, are full of various fairly meaningless entries, none of which are obviously errors.
Can anyone make any suggestions of things which I could look at or try, or any other software that might find any problems?
I hate Windows Networking, it's always causing these sort of intractable problems, but often after a major bit of swearing I can generally solve it, this one, however, is proving to be a git.
