13 replies
by syscokid
by scndtnr
Need more info, there are no psychics here: "Oh yes, I can see your server now! Yes, it's coming to me! You have a corrupt netlogon service!"
Client:
Are you using MS Client for MS networks?
Protocol?
Protocol configuration?
Workgroup name same as domain?
DHCP?
PDC on same segment?
WAN or LAN?
---------------------------------
Username: |
Password: |
Domain: |
---------------------------------
ABove dialog box appearing?
Correct names for username and domain name in above dialog?
No CAPS?
Server: Protocol? Protocol configuration?
by scndtnr
by winssuresh
1.There was no mention whether the user is able to login to your domain , in another workstation whether it is NT workstation or Windows 95
2. Has the user account is o.k, means is not locked or not.
If the user is not able to logon to domain from any work station, I would check wheter the BDC is in sync with PDC. If Not Sync the BDC with PDC, using server manager.
This is realted to Authentication Issues
Thanks
by scndtnr
by dennisr
by scndtnr
by packratt
Look at your C:\WINNT\SYSTEM32\DRIVERS\ETC\LMHOSTS file and make sure there is an entry for your PDC if you have LMHOSTS enabled, the entry should read:
PDC IP addr PDC name switches Domain
255.255.255.255 PDC #PRE #DOM:PDC_DOMAIN
If the entry is there copy it to the same directory as LMHOSTS.SAM.
Then look at the HOSTS file and make sure there is an entry for the PDC in there as well which should be as follows:
IP addr PDC name
255.255.255.255 PDC
I hope that fixes the problem, we had the same problem here as well connecting to a domain accross the WAN.
by packratt
sorry, lmhosts & lmhosts.sam should read:
pdc ip addr (tab) pdc name (tab) #PRE (tab) #dom:domain name
and hosts should read:
ip addr (tab) pdc name
by packratt
Ooops, and make sure you import the LMHOSTS file in the network settings under TCP/IP settings|WINS.
Good Luck!
by scndtnr
by scndtnr
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending