Another variant of the mount_smbfs error

Question

I too am having issues with this problem, however, it is of a different nature.
One night, I can connect and transfer files like always. The next morning, no dice. No changes to anything, nothing. I get the "Windows cannot find xxxx. Check the spelling and try again..." dialog.
I was always able to connect to my mac by either mapping a network drive to //192.168.1.2/Zim or typing that address into an address bar and authenticating. In the past, both methods have worked no problem.
From the Mac side, those familiar with Server 2003 know Windows machines have a hidden share on the root of each drive. In this case, I wanted to connect to C$, the hidden share for my C: drive. I would open the "Connect to server..." dialog from Finder, and type in "smb://192.168.1.3/C$" and it would connect me after authentication, giving me that share in the Finder. It would also work when I used smb://Thinkpad/C$. That method now fails too. I set up an actual share on the drive to test, the share being C, and attempt to connect to smb://192.168.1.3/C, and nothing. I get the -34 error.
When I check my logs, this is what i see:
+mount_smbfs: can't get server address `THINKPAD.':+
+Unknown host+
+mount_smbfs: can't get server address: syserr = Network is down+
(I also tried the IP address of my Thinkpad, same result)
In my Firewall log (which I had on up until trying to diagnose this problem), I have:
+Sep 5 13:22:11 PowerMacG4 ipfw: 12190 Deny TCP 192.168.1.3:1107 192.168.1.2:80 in via en0+
+Sep 5 13:22:14 PowerMacG4 ipfw: 12190 Deny TCP 192.168.1.3:1107 192.168.1.2:80 in via en0+
+Sep 5 13:22:20 PowerMacG4 ipfw: 12190 Deny TCP 192.168.1.3:1107 192.168.1.2:80 in via en0+
Allowing those ports in Firewall doesnt help, as the next attempt uses a different port. Note that I am trying to fix this with the firewall off, but am turning it on to get feedback as to what the network is doing.
My network isnt down, my NetBIOS setting in Windows is set to "Default", the gateway and subnet are the same, and there are no other conflicts. Like I said, worked one night, 12 hours later it did not.
Help!!

Answer 1

Just wondering... have you tried a Permission Repair lately on the Mac?