- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Networking
- >
- Re: W2k trying to access a ghost share
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2003 07:49 AM
тАО10-14-2003 07:49 AM
W2k trying to access a ghost share
Now, when I double-click anything on the desktop, or try the Start menu, W2k tries to connect to that particular share I was using previously. The system (explorer.exe) seems to hang for about 30 seconds because the share is unaccessible (I'm in a foreign network). This connection attempt can be seen with "nbtstat -s" command, it says "Connecting \\computer\share" and the desktop waits. Even IE hangs at that time if I press the Back button meanwhile. After that 30 seconds everything is fine again, applications continue to start or whatever.
That share name is not mentioned anywhere else in the registry but in the Map Network Drive dialog's Last Recently Used list. The share is not currently mounted to any drive letter.
The computer has been booted several times, it's a few days now when I used the PPTP connection. I experienced the same issue with two different W2k workstations. No domains involved.
So, why W2k is still trying to see the share, and why is it trying it while I'm just starting some software from the desktop (or from the Start menu)? How do I stop W2k from looking for that share?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2003 12:04 PM
тАО10-14-2003 12:04 PM
Re: W2k trying to access a ghost share
If you opened documents, then there is a shortcut to the document in the resently used Documents list (clear this list out).
Jon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-17-2003 06:44 AM
тАО10-17-2003 06:44 AM
Re: W2k trying to access a ghost share
This is really getting me annoyed. Any other ideas?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-17-2003 07:51 AM
тАО10-17-2003 07:51 AM
Re: W2k trying to access a ghost share
Jon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-17-2003 07:56 AM
тАО10-17-2003 07:56 AM
Re: W2k trying to access a ghost share
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-21-2003 07:42 PM
тАО10-21-2003 07:42 PM
Re: W2k trying to access a ghost share
I'm using Eudora, and I had tried starting it with the share name as a parameter (where to fetch the main environment). Therefore Windows registry contained some "Path#x" keys in HKEY_CURRENT_USER\Software\Qualcomm\Eudora\LaunchManager that contained the share names. (I didn't want to believe those would affect the problem.)
When I removed the share-pointing keys, responsiveness came back to my desktop!
This was quite surprising, as Eudora was not needed to be running for Windows to choke. Seemingly Windows checks some paths in the registry (under Eudora tree) when doing *anything* in the desktop.