• Advertisement
Sign in to follow this  

Network Neighbourhood / My Network Places Gone!

This topic is 4337 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi... Interesting bug, I think. In testing my networking code (Winsock 2 based UDP & TCP sockets) on XP SP2, I've just noticed that all of the network links disappear (with the exception of a samba fileserver). Any idea on what might be causing this? All the machines are still visible by IP (\\192.168.X.X) and hostname (\\Host), it's just the cached links that get wiped out. Obviously this is a sucky thing to do to someone, so I need to get it fixed. I just can't think what might be doing it. (There's no memory leaks, or any sockets being left open, and winsock IS [apparently] being shut down properly)...

Share this post


Link to post
Share on other sites
Advertisement
I assume this is in XP? If you can, test it in 2K. XP seems quite flakey on workgroups and domains, generally losing track of anything that's not a mapped drive.

Share this post


Link to post
Share on other sites
Is it XP Home? For some reason, it does not want to persist network services; probably to force people to use XP Pro if they want things like a permanently mounted mapped drive...

Anyway, it't un-clear to me what you mean by "networking links" and what "disappearing" actually means. What are the things you set up before running your program, and how do you tell they've changed when they "disappear"?

Share this post


Link to post
Share on other sites
Yes, it's xp home. :-(

Cached shortcuts to network places (network shares) that usually persist are not showing up after running my application (initialising and shutting down winsock), doesn't matter if I actually form connections or send / recv anything. Also when attempting to browse the workgroup, explorer locks up,
so it's something to do with the way XP home browses for available services.

I do suspect it's an XP home limitation. It's fairly low on my bug list, so I'll do some more poking around with it later.

Share this post


Link to post
Share on other sites
Quote:
Also when attempting to browse the workgroup, explorer locks up,


Sounds like a driver bug or other system software bug rather than something that your program does. Especially if you just call WSAStartup() and then WSAShutdown(), and it still happens.

If I were you, I would run a good virus scanner, a good malware scanner, and make sure to update all my drivers -- your experience does not sound normal, and is not a behavior of XP Home.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement