Thinkpads Forum

I'm not sure if this is model-specific, a problem stemming from Windows, or from something Lenovo installed.

Short-ish descriptor of problem: I have a Z61m, when I attempt to access a shared drive on the network, it asks for a username & password, though the drive is set up without the need for either. The dialog won't let you leave it blank, and entering an account name and password registered on the server just makes it show the same dialog again. Another Z61m has no such problems accessing the drive.

Solutions already tried (in this order, one at a time): uninstall of all preinstalled Symantec products, tool for removing traces left behind by Symantec, manual removal of registry keys created by Symantec & related folders in Program Files & Documents and Settings, deletion/rebuilding the WMI repository used by Windows Security Center, disabling Windows Firewall, removal of Access Connections, using 'Net Use' command to try and mount the drive manually, checking various Local & Group policies against the older Z61 (which can access network drives), installing Online Armor firewall.

Longer explanation: I have numerous Z61m laptops on my shelf as part of my job. I have been using one of them as my work computer. I initially used the Base Software Administrator tool to fine-tune which apps got installed intially (i.e.- pretty much none of the Lenovo apps). It worked fine, but eventually hit an error I've seen before that has always required a fresh OS install (thanks Eclaim, your crappy old Visual Basic 6 programming did it again).

So I got another off the shelf, only this time decided to just use the default Lenovo setup to start. I uninstalled the Symantec products that came with it, then used a tool to go back and scrub any remaining traces. Then I used System Update (just days before Lenovo shut the service down) to update all the drivers and apps. I then requisitioned the necessary ticket tracking software one of my clients uses to be installed. It was only at this point that I tried to access a network drive, and discovered the problem mentioned above in the short explanation. Then I tried the above solutions. I've been searching all over the internet and these forums, but everything I can find is either just an explanation of how to mount a network drive, how to share one on a network, or problems related to Symantec or Access Connections. I'm pretty sure I've done a good job of sanitizing both from the system. I even tried installing the third-party firewall in the hopes that it would overwrite any settings that might have been left behind by Symantec or Windows Firewall.

I'm at my wits end here, I'd rather not start the whole process over, especially since without knowing what went wrong, it could very well happen again. It's also problematic getting the ticketing software I need reinstalled again.

I could almost swear I've run into this problem before, but it's been years and I can't recall the solution (if any).

Can anybody offer me any other things to try than what I already have?

Check if this M$ article helps: http://support.microsoft.com/kb/840634
Also check in your firewall that the shared network drive is set up as a trusted zone.
Simple File Sharing allows remote users to authenticate as guests. This may or may not be enabled.

Thanks for the suggestions.

I tried adding the network port to be trusted by the firewall, but that didn't work.

The other suggestions are about setting up the server machine, which don't really apply (it's not actually a Windows server, it's a Samba share on a Ubuntu Linux server). Besides, I can access it fine with another Z61, and also with a whole host of other laptops when booted from Windows PE.

Update: It occurred to me that whenever the dialog appears I've either been trying to leave it completely blank, or enter in my username and password (which is the same on both the server and client). I tried just entering in 'guest' as a username, and leaving the password blank, and that worked. It seems to remember it when I disconnect from the network and reconnect, too. I suppose I must have done it long ago on the original Z61 and forgotten about it.

Simple solution, big waste of my time.