neumannu47
asked on
Not Able To Browse XP Machine
Machine2 is Windows 2000 SP4. Machine1 is XP Pro SP2 with the firewall disabled. Both machines are on the same subnet behind a Netgear wired router.
When admin1 is logged into Machine2, she can browse the Windows Network ("Computers Near Me") and see Machine1, along with its shared printers and folders. When admin2 is logged into the same machine, Machine2, Machine1 does not show up anywhere in browsing, even after a long wait. She can reach Machine1 with Start | Run "\\Machine1", but she cannot browse there.
The reason that this is a problem is that there is an application that admin2 needs to run that needs to access a folder on Machine1. The application does not allow typing in the UNC path. The folder has to be selected by browsing to Machine1 from Machine2.
Remember, everything is perfect until admin1 logs out of Machine2 and then logs in as admin2. Therefore, the cabling, jacks, NICs, and the like are all fine. Neither machine has any spyware or viruses. (We used to have this problem all the time in Windows 98, but not in 2000/XP.)
I just did a temporary work around by mapping a drive letter on Machine2 to Machine1. (I was able to access the folder by typing in the UNC.) Even then, though, Machine1 still does not show up in Computers Near Me or Network Neighborhood. I'd like to solve the browsing problem, it it can be done. The situation is as if the XP machine is not announcing itself to the network, but that cannot be the problem since everything works fine when admin1 is logged in.
When admin1 is logged into Machine2, she can browse the Windows Network ("Computers Near Me") and see Machine1, along with its shared printers and folders. When admin2 is logged into the same machine, Machine2, Machine1 does not show up anywhere in browsing, even after a long wait. She can reach Machine1 with Start | Run "\\Machine1", but she cannot browse there.
The reason that this is a problem is that there is an application that admin2 needs to run that needs to access a folder on Machine1. The application does not allow typing in the UNC path. The folder has to be selected by browsing to Machine1 from Machine2.
Remember, everything is perfect until admin1 logs out of Machine2 and then logs in as admin2. Therefore, the cabling, jacks, NICs, and the like are all fine. Neither machine has any spyware or viruses. (We used to have this problem all the time in Windows 98, but not in 2000/XP.)
I just did a temporary work around by mapping a drive letter on Machine2 to Machine1. (I was able to access the folder by typing in the UNC.) Even then, though, Machine1 still does not show up in Computers Near Me or Network Neighborhood. I'd like to solve the browsing problem, it it can be done. The situation is as if the XP machine is not announcing itself to the network, but that cannot be the problem since everything works fine when admin1 is logged in.
obviously not running a domain environment.....
can you try a 3rd user for me? when you log in with admin 1 (which works) do you have an identical user setup on the target machine? do you have a replica user of admin 2 on the target machine?
can you try a 3rd user for me? when you log in with admin 1 (which works) do you have an identical user setup on the target machine? do you have a replica user of admin 2 on the target machine?
ASKER
You are correct. These machines are peer-to-peer; therefore, there is no domain. I will try a new profile. Maybe there is a problem with admin2, although it is new. I'll report back.
ok mate let me know how you go
ASKER
Still no solution!
ASKER
At someone's suggestion at another site, I downloaded and ran Advanced WindowsCare, a great, free utility, and the problem is solved. If fixed something down deep in the OS. Thanks for the tries.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
- Make sure that admin1 and admin2 have the same EXACT security permissions. This means both locally and domain-level (for instance, make sure that admin2 is a local administrator).
If those ideas there don't fix it, can you give some more details about the environment, ie., domain setup, etc.