-
March 15th, 2001, 11:07 PM
#1
System won't log on automatically
I have a client with 1 PC that will not log on. As you all know if you do not log on then network resources are not available. If I just log off and then log on all is well. It just won't log on when you start or restart. I have unistalled all services and clients and TCP. I have removed all PWL files. This is a Win98 SE box, on a all Windows Peer to peer network. Files are located on a snap server, so access is important.
Any ideas?
Thanks
Robyn
------------------
MCSE, MCT, Net +
-
March 16th, 2001, 02:04 PM
#2
What protocol and settings are you using?
Client for MS networks
TCP/IP using DHCP
etc...
The more information the better. Also will the machine not log in at all, or just not log in automatically?
------------------
Death is lighter than a feather - duty heavier than a mountian.
Death is lighter than a feather - duty heavier than a mountian.
The answer to your question is: 00110100 00110010
-
March 16th, 2001, 03:59 PM
#3
Using just:
Client for MS
Network card driver
TCP/IP
File and Print sharing for MS
Private address, proper range. Just will not automatically logon, if you logoff and logon all is well. Think I fixed this issue elsewhere a few years back. Cannot remember the fix.
Thanks
------------------
MCSE, MCT, Net +
-
March 16th, 2001, 09:54 PM
#4
are you saying that your network is currently running as a workgroup?
if so, try using NetBEUI as the default protocol. It should do the trick.
-
March 17th, 2001, 12:48 AM
#5
Had the same problem try this..
start run regedit
hkey_local_machine
-networking
-logon
LMLogon (binary value) set to 00 00 00 00
PolicyHandler (string value) set to "Grouppol.dll,ProcessPolicies
PrimaryProvider (string value) set to "Microsoft Network"
username (string value) set to (there name)
than reboot..
Let me know if that worked.
-
March 17th, 2001, 02:12 AM
#6
Thanks
Will try the registry fix. May not get over there until Tuesday.
Cannot use NetBeui, they use the Internet from a shared connection.
It is not a protocol issue, the registry is corrupt or the system needs reloaded .. will try register fix just suggested.
thanks everyone
------------------
MCSE, MCT, Net +
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|
Bookmarks