Server:
NT 4.0 PDC (w/ dhcp / wins server installed) x1
WIN2000 member server x 2
WIN2003 member server x 1
Clients:
win2000 pro.
Problem: client pc cannot acces network drive.
Checklist:
- network cable normal.
- can ping PDC server name and ip address from client pc
- Client PC obtain correct ip / wins / dns info from dhcp
- No client pc is using fix IP.
- check that Wins server (is PDC server) - wins database --__MSBROWSE_--[01h] is client pc IP 192.168.168.7, not PDC server itself (192.168.168.250).
Since client needed to work in urgent, I rebooted NT server and solve it that time.
After reboot, wins database --__MSBROWSE_--[01h] is 192.168.168.250 (pdc server). Then network browsing returned to normal too.
That client-pc (192.168.168.7) is seldom turned on as it's just to test program. Moreover, we met same problem (network drive is inaccessible) a week before. But pc (192.168.168.7) didn't turn on that time. I also rebooted server without checking anything that time.
I think the problem is caused by the wrong PC to take the role of master browser. If I find wrong master browser in network, how should I fix it without reboot NT server?
Shoud I modify pdc server registry as follows?
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters]
"IsDomainMaster"="TRUE"
"MaintainServerList"="YES"
NT 4.0 PDC (w/ dhcp / wins server installed) x1
WIN2000 member server x 2
WIN2003 member server x 1
Clients:
win2000 pro.
Problem: client pc cannot acces network drive.
Checklist:
- network cable normal.
- can ping PDC server name and ip address from client pc
- Client PC obtain correct ip / wins / dns info from dhcp
- No client pc is using fix IP.
- check that Wins server (is PDC server) - wins database --__MSBROWSE_--[01h] is client pc IP 192.168.168.7, not PDC server itself (192.168.168.250).
Since client needed to work in urgent, I rebooted NT server and solve it that time.
After reboot, wins database --__MSBROWSE_--[01h] is 192.168.168.250 (pdc server). Then network browsing returned to normal too.
That client-pc (192.168.168.7) is seldom turned on as it's just to test program. Moreover, we met same problem (network drive is inaccessible) a week before. But pc (192.168.168.7) didn't turn on that time. I also rebooted server without checking anything that time.
I think the problem is caused by the wrong PC to take the role of master browser. If I find wrong master browser in network, how should I fix it without reboot NT server?
Shoud I modify pdc server registry as follows?
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters]
"IsDomainMaster"="TRUE"
"MaintainServerList"="YES"
