richtree
asked on
Why XP Pro cannot browse the domain?
I have Windows 2003 server as domain controller (svr_dc) at head office.
I have XP Pro workstation (wk_xp) at remote office connected through tunnel.
I alse have another standalone Windows 2000 server (svr_outsider) which physically connects to remote network, but not logically in myDomain.
Usually wk_xp is able to browse My Network places->Entire Network->Microsoft Windows Network->myDomain->all servers and workstations in myDomain.
But once in a while, wk_xp is unable to browse myDomain: domain is not accessible.
At this moment, svr_outsider is unable to see myDomain entry at all at My Network places->Entire Network->Microsoft Windows Network.
I check and make sure:
1. network connctivity is ok
2. tunnel between remote and head office is ok
3. 'Computer Browser' service is started.
I restarted wk_xp and it can see myDomain and its members; svr_outsider can see myDomain and its members too. I did not have a chance to compare what services are running before and after reboot. So I just ask the lazy question here.
Q#1. What service is necessary to browse its own domain?
Q#2. What causes the service to stop? It started automatically.
Q#3. Any simple way to keep the service started all the time? A batch? A scheduled task?
Thanks.
I have XP Pro workstation (wk_xp) at remote office connected through tunnel.
I alse have another standalone Windows 2000 server (svr_outsider) which physically connects to remote network, but not logically in myDomain.
Usually wk_xp is able to browse My Network places->Entire Network->Microsoft Windows Network->myDomain->all servers and workstations in myDomain.
But once in a while, wk_xp is unable to browse myDomain: domain is not accessible.
At this moment, svr_outsider is unable to see myDomain entry at all at My Network places->Entire Network->Microsoft Windows Network.
I check and make sure:
1. network connctivity is ok
2. tunnel between remote and head office is ok
3. 'Computer Browser' service is started.
I restarted wk_xp and it can see myDomain and its members; svr_outsider can see myDomain and its members too. I did not have a chance to compare what services are running before and after reboot. So I just ask the lazy question here.
Q#1. What service is necessary to browse its own domain?
Q#2. What causes the service to stop? It started automatically.
Q#3. Any simple way to keep the service started all the time? A batch? A scheduled task?
Thanks.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Thank you all.
ASKER
Now I have a better understanding of the browsing issue. Thank you all.
Glad to help. =)
ASKER
wk_xp is configured with the WINS server.
usually wk_xp is able to browse the hosts in myDomain.
I check two workstations: both xp pro.
wk_xp11 at branch#1
wk_xp21, wk_xp22 at branch#2.
branch#1 and branch#2 connect to head office using the exactly the same type of vpn.
wk_xp11 is able to browse all hosts in myDomain (local to branch#1 and remote in head office).
wk_xp21,wk_xp22 are able to browse all hosts local to branch#2, but none in remote head office)
Further wk_xp21, wk_xp22 are able to resolve host names, eg able to broswe share folder by typing \\myDC\share which is connected to head office.
I check the services started on both wk_xp11 and wk_xp21: they are both identical. 'Computer browser" is also started.
Logically it seems to be related to the vpn network, but the two vpn network are identical except the network addressing.
Any idea why there is such browsing difference between wk_xp11 and wk_xp21?
Thanks a lot.