• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows 7 mapped network drives shows "not connected"

finbarqs

Diamond Member
I don't know if I need to do a "re-install" but windows will NOT save my credentials. I would have to manually save my credentials in the credential manager section under control panel\users\credential manager.

Even then, it comes up "cannot connect to all your network drives". I will have to go to "computer" and then manually click into each drive to 'activate' them. This poses a problem as I linked some stand-alone programs on my network drive. I don't want to click into the drive each time I boot up. Is this a Windows problem? do I need to reinstall?
 
Mine don't work until I click on them either...

Suggest you make a batch file that runs on login that executes the "net use" command.

Curious if there is a real solution to this problem though.
 
It is a windows problem. I have tried solutions like the following:

Start > Run > type "gpedit.msc" (without quotes) click ok.
Local Computer Policy > Computer Configuration > Administrative Templates > System > Logon > Always wait for the network at computer startup and logon
set this to Enable

Start > Run > type "gpedit.msc" (without quotes) click ok.
User Configuration\Administrative Templates\System\Scripts\Run logon scripts synchronously
set this to Enable

Then reboot.

But I have noticed that two out of three computers the problem has resurfaced. As soon as I go to access the drive, it is there and the red X goes away. It would seem that a simple macro which opens windows explorer and selects each drive would fix the problem. But obviously that's beyond retarded. Windows in general is beyond retarded. This problem has been around for years and like most problems will probably never be truly fixed.
 
I've tried every combo possible, giving myself a static IP (internal) -- didn't work. instead of using the name of the drive, I've used the IP. Still didn't work. I honestly have no idea why it doesn't work... I can click through it, but I shouldn't have to...
 
I think I fixed it. I used the "admin" password and credentials instead of my "account" that I created for myself and that seems to have resolved the "disconnected" issue and clicking through. Thank goodness, as I thought it would've been annoying to create a logon script just to solve this!

I just didn't want to add anymore "startup" items to my start up!

Thanks for the help guys!
 
Back
Top