INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!

Talk With Other Members
Be Notified Of Responses
To Your Posts
Keyword Search
One-Click Access To Your
Favorite Forums
Automated Signatures
On Your Posts
Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

LINK TO THIS FORUM!

Tek-Tips LinkedIn^® Group

Join our
LinkedIn^® Group!

Hook up with past and present colleagues and classmates quickly.

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site

(Download This Button Today!)

Feedback

"...Your site is a great idea. I should have joined your site years ago. Better late than never..."

More...

Geography

Where in the world do Tek-Tips members come from?

Click Here To Find Out!

Tek-Tips Shirts!

Get your
Tek-Tips Forums
SWAG here!

Home > Forums > MIS/IT > Operating Systems - Hardware Independent > Microsoft: NT 4.0 Server Forum

Client pc cannot acces network drive.

Read More Threads Like This One

eddypc (TechnicalUser)

26 Apr 08 12:49

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"

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Back To Forum

Back To Microsoft: NT 4.0 Server