Tried turning on network discovery and I still can't see other comps
I am running an AMD dual core sustem dual booted with XP Pro/7 RC(64 bit). I disabled the firewall amd turned on network discovery. There are 2 other comps on the network, both running XP, one Pro one Home. When booted in XP I can see and access the other comps shared files. Booted into 7 I can log onto the Inet, but not any of the other comps. Any suggestions? Oh, and the LAN is hardwired.So not having run Vista, I am surprised at the difference in access to the inner workings of the computer. In XP I can change just about any setting I need/want to. Is there a way to go in deeper than the preset system repair or configuring wizards? This is a big frustration, since I used to do some low level IT stuff for multiple retail locations at my last job. Thanks
June 11th, 2009 9:09pm

I'm not shure why but network discovery can sometimes take a looooooong time.Can you access an other pc if you type \\HISNAME in the windows explorer location bar?
Free Windows Admin Tool Kit Click here and download it now
June 11th, 2009 9:21pm

I went to one of the comps on the network. Went to the Control Panel, then System, then Computer Name. Copied down the comps name and typed it in to IE's location bar. It opened a window with that comp's shared stuff. But I still can't see them through the normal network view.So, I assume that since I can seethe other comp if I tellmy comp EXACTLY where to look, and you suggested that network discovery takes a long time, my comp should eventually see the other comps on the network, and I just need to be paitent. I've got my fingers crossed. Thanks
June 11th, 2009 9:52pm

Did you check under Control Panel\All Control Panel Items\Network and Sharing Center\Advanced sharing settings if "Turn on network discovery" is activated for your current profile?
Free Windows Admin Tool Kit Click here and download it now
June 11th, 2009 11:06pm

Ok, update. I can still find the other comps on the network via the explorer bar, but otherwise windows will not automatically see them. I have checked the network discovery settings and they stay on all the time. The comp has been restarted multiple times, booting into both Win7 and XP. XP still has no problem seeing the network. And as I said, I can access the other comps via the explorer bar. So, I am not sure what to think. Once I access another comp on the network, as long as that window is open it will show the comps I access(if I access more than 1). Once that window gets closed, if you look at the network, it does not show the other comps. Also, if I access another comp on the network and keep that window open, then open another window, the second window doesn't show the comps accessed in the other window! Still confused, thanks
June 13th, 2009 10:46pm

As bugs are being worked out, it may just be a glitch at the moment. I'd wait on the next release to see if it gets addressed.
Free Windows Admin Tool Kit Click here and download it now
June 13th, 2009 10:52pm

What do you mean by the next release?If you mean the retail version that is purchased in stores, why should we take the risk of purchasingthe retail versionif our onlyexperience so far is that it doesn't work very well?If you want my advice, I would release updates for the RC to prove that things are actually getting fixed!
June 14th, 2009 3:19am

Reading the user manual you will see that the networking in RC7 is does NOT work with XP...you can browse XP computers from RC7 on your network but NOT XP to RC7...hope this helps
Free Windows Admin Tool Kit Click here and download it now
June 14th, 2009 6:49pm

Mine is the other way around. I can browse/copy-to W7RC from XP and W2K, but W7 will not browse/copy-to them. But they do show up in the W7 Network.
June 15th, 2009 7:33am

No, I'm sure Adam meant the next RC before going Gold.
Free Windows Admin Tool Kit Click here and download it now
June 15th, 2009 11:24am

The next release. Not the final product. Obviously this is just a cosmetic problem, so it is not likely to be an issue.
June 15th, 2009 7:11pm

I noticed you mentioned both of your other machnes are XP. This problem has actually been around sense Vista. You have to install support for LLTD for the XP machines ot be browsable in the network by Vista or newer. The notes say it's just for the network mapper, but I've noticed it fixes the problem for what your descirbing as well. http://www.microsoft.com/downloads/details.aspx?FamilyId=4F01A31D-EE46-481E-BA11-37F485FA34EA&displaylang=en
Free Windows Admin Tool Kit Click here and download it now
June 15th, 2009 7:39pm

Nope... didn't work. Tried to install the suggested fix, and was told that the latest service pack installed is newer than the patch. Also, while I can get the comps to see each other via the explorer bar, they can not access the files on the other comp, weather Win7 looking at one of the XP comps or one of the XP's looking at the Win7 comp. And yes, all the files trying to be accessed are shared universally.
June 16th, 2009 6:08am

I'm having same problem. My XP box and win2k box show up in the work group but the win 7 box does not. The win 7 box doesn't see either of the win2k or xp box. Now, If I search for the win 7 box by name nothing, but if I search by IP...there it is. Likewise, when on win 7 box if type in run window \\computer name...nothing, but if I type in \\IP... it will find the win2k box and the XP box. All folder shares are there. I know this is a BS workaround, but I have just had the win 7 box loaded for less than a week.
Free Windows Admin Tool Kit Click here and download it now
June 17th, 2009 3:26am

Hello magikbike,The problem with the LLTD patch from the link above, ithas to installed in between service pack 2 and service pack 3 when using it in Windows XP. The system will claim that this patch isn't needed as it is supposed to be included in the service pack. Also unistalling the service pack will also not allow it to run. When running any fresh installs of Windows XP i have the LLTD patch handy to install as soon as service pack 2 is finished.-Scott
June 17th, 2009 3:44am

Hello magikbike, The problem with the LLTD patch from the link above, ithas to installed in between service pack 2 and service pack 3 when using it in Windows XP. The system will claim that this patch isn't needed as it is supposed to be included in the service pack. Also unistalling the service pack will also not allow it to run. When running any fresh installs of Windows XP i have the LLTD patch handy to install as soon as service pack 2 is finished. -Scott Can you force the install at a later point? Seems a bit overkill to have to do a full reinstallation because of a patch, no?
Free Windows Admin Tool Kit Click here and download it now
June 17th, 2009 1:25pm

I agree, that's crazy to do a full reinstall. So in the mean time, I have created desktop shortcuts to the various network locations. From Win7 I can see, and access the various network locations and files that way. The XP comps can't access the files on the Win7 comp still. But, like I said, via desktop shortcut, I can at least see the other Win7 comp. Any other suggestions?
June 17th, 2009 9:04pm

Hello magikbike and azynkron,I haven't found a way to install after service pack 3, unfortunately as this has been something I've rather wanted to fix myself. The best workaround I have come up with is to slipstream all the service packs and the patch to my Windows XP install disk and perform a fresh install or upgrade. But as you said a fresh install is a little drastic which is why I chose the slipstreaming route to save time on post installation of service packs.-Scott
Free Windows Admin Tool Kit Click here and download it now
June 18th, 2009 1:55am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics