ivicker
asked on
Windows 2000 Peer to Peer
I have a Windows 2000 peer to peer network. A compaq PC is the "server" running Windows 2000 PRO sp3. Users access the network using thier laptops registered to other domains.
When they try to access the server they get this error message "there are currently no logon servers available to service the logon request"
If they conect to thier domain via RAS the error message stops until the next reboot.
Thanks in advance
When they try to access the server they get this error message "there are currently no logon servers available to service the logon request"
If they conect to thier domain via RAS the error message stops until the next reboot.
Thanks in advance
How many laptops are being used? Win2k pro has a lmit of 10 concurrent connections
ASKER
It's only 3 or 4 laptops.
Anything showing up in the "servers" event logs?
ASKER
There is nothing showing under servers in the event log. You can access the workstations from the Server.
ASKER
If it is easier use MSN Messenger ianvicker@hotmail.com
So the laptops are configured to login to other domains?
ASKER
Yes they are. If the laptops log on locally they can access the server. But this is not acceptable to this particular customer.
I would add an entry to his lmhosts file then.
xxx.xxx.xxx.xxx yourservername #PRE
ASKER
This has already been done. We have also tried \\computername\share /user:
Can he ping the ip address of the server?
ASKER
Yes, and the name
ASKER
Yes by IP and by Name
Hmm can you give me a little more info about the network. Are you using a router or firewall to the internet?
Error Message:
There are currently no logon servers available to service the logon request.
Explanation:
This may be due to a network failure, or because the computer is physically removed from the network (such as with laptop computers).
User Action:
If you are using a network, make sure the domain controller you are trying to log on to is accessible. If necessary, obtain administrative assistance to do this. As an alternative, and in the case of laptops, log on to the machine locally as the primary user of the system.
From the microsoft website
There are currently no logon servers available to service the logon request.
Explanation:
This may be due to a network failure, or because the computer is physically removed from the network (such as with laptop computers).
User Action:
If you are using a network, make sure the domain controller you are trying to log on to is accessible. If necessary, obtain administrative assistance to do this. As an alternative, and in the case of laptops, log on to the machine locally as the primary user of the system.
From the microsoft website
ASKER
All I will say is that it used to work and no passwords have been changed!
No passwords have been changed on your server but the domain he logs into should have a domain password policy that requires you to change your password every so often.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
FOOTNOTE: "then the only solution is to have them log-on to a local account." logon to their local machine account on the laptop....again, the Admins in their domain, can and may prevent that. Depends on how security savvy they are. But it doen't sound too good if they are sill running mixed mode.
-Eric
If you have any other '?'s? about this...please ask, I am following the thread.
-Eric
If you have any other '?'s? about this...please ask, I am following the thread.
DISCLAIMER:
1 more thing...if you (or anyone else) do test it out, just stop the net logon service and segment the net so just the host and the DC are on the wire. I reccomend doing it with a LAB or "break me" machine. Do not forget ot turn it back on yor you will have some PISSED domain controllers. Make sure you logon the old skool way LM-style.
I absolve myself from ANY responsibilities for you taking my advice to turn net logon off on your DC. This included but is not limited to, loss of productivity, angry spuse/angry boss, network down time, broken SLA's, loss of limbs and/or organs and other sort of injury including but limited to loss of life. This shall extend into the afterlife as well, IF it is dertimined that ones existing, I am released from all spiritual responsibility for this act....I reserve the right to make changes to this disclaimer at any time, without notification.
-Eric
OK thats it...
/endtrans
1 more thing...if you (or anyone else) do test it out, just stop the net logon service and segment the net so just the host and the DC are on the wire. I reccomend doing it with a LAB or "break me" machine. Do not forget ot turn it back on yor you will have some PISSED domain controllers. Make sure you logon the old skool way LM-style.
I absolve myself from ANY responsibilities for you taking my advice to turn net logon off on your DC. This included but is not limited to, loss of productivity, angry spuse/angry boss, network down time, broken SLA's, loss of limbs and/or organs and other sort of injury including but limited to loss of life. This shall extend into the afterlife as well, IF it is dertimined that ones existing, I am released from all spiritual responsibility for this act....I reserve the right to make changes to this disclaimer at any time, without notification.
-Eric
OK thats it...
/endtrans
I lied....since I read about "acceptable solution"
Why? They do not want to lose their profile? if that is all it is, make a user account with the same name and PW (or whatever), you will have to give them either PU or Admin on the local machine or very specific permissions and rights (PITA!!!). Then logon with the new user and log off, log into local admin change the reg key:
HKEY_LOCAL_MACHINE\SOFTWAR
change the string so that it matches their orther profile. The profile will be "shared", this may really upset their admins in the other domain if they find out, however.
Then they have the same username and PW and profile.
There really isn't much you can do with the derver (cept give "network" and "Anonymous" atleast user level access. BAD BAD BAD....and it may not work....cause the problem isn't the stand alone server. They are getting NAK'd by their clients local/quasi domain security authority. So any change you make is going to have to clients side no matter what.
the real solution is what I stated above,or put a DC/DS there and Trust the other domain.
if they can try Kerberos, but that depends on the conditions set by the net admin if.when the ticket expires, still worth a shot.
-Eric
Why? They do not want to lose their profile? if that is all it is, make a user account with the same name and PW (or whatever), you will have to give them either PU or Admin on the local machine or very specific permissions and rights (PITA!!!). Then logon with the new user and log off, log into local admin change the reg key:
HKEY_LOCAL_MACHINE\SOFTWAR
change the string so that it matches their orther profile. The profile will be "shared", this may really upset their admins in the other domain if they find out, however.
Then they have the same username and PW and profile.
There really isn't much you can do with the derver (cept give "network" and "Anonymous" atleast user level access. BAD BAD BAD....and it may not work....cause the problem isn't the stand alone server. They are getting NAK'd by their clients local/quasi domain security authority. So any change you make is going to have to clients side no matter what.
the real solution is what I stated above,or put a DC/DS there and Trust the other domain.
if they can try Kerberos, but that depends on the conditions set by the net admin if.when the ticket expires, still worth a shot.
-Eric
You may refer to this site from Microsoft Help and Support :
http://support.microsoft.com/default.aspx?scid=kb;en-us;139410
Goodluck!
eNTRANCE2002 :)
http://support.microsoft.com/default.aspx?scid=kb;en-us;139410
Goodluck!
eNTRANCE2002 :)