There are currently no logon servers available to service the logon request
Updated: 21 May 2010 | 11 comments
I'm sure the is a basic explination awaiting me, and I'm a bit new to this whole scene.
after loading an image on a machine, somewhere in the middle of the installation when the client needs to communicate with the server for instructions, alrtiris reports the "There are currently no logon servers available to service the logon request" error.
big problem or simple solution?
thanks in advance for your feedback.
discussion Filed Under:
Comments
i am getting this error on pushing out packages. I am starting testing Vista machines and have the Dagent installed and when i go to push a package to the vista machine i get this error (the package works fine on windows xp machines). Any thoughts?
Can you provide a little more information about your environment? Are these machines in a domain? On the machines in question, if they are not, is simple file sharing enabled? If it is, you will need to ensure that it is unchecked, or disabled.
Also, if you specify a username and password that do not exist, this can cause a problem, especially if the computer name has changed due to imaging.
Brian Hawver
Systems Engineer
Yaskawa America, Inc.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.
The machines are joined to the domain and the service account that i use to push the packages has Administrator rights to the machine. The service account pushes fine to the other machines joined to the domain that are windows xp. So that account is active and working
Is the service account a domain account or local to each computer? When you specified that service account in the task, did you use the old netbios naming convention for the username or the UPN convention? What I mean is each account in AD has two names. An example is YOUR_DOMAIN\username or username@yourdomain. Try using the opposite way of what you are using currently (i.e. if you are using YOUR_DOMAIN\username, try using the UPN, username@yourdomain).
We don't use Vista here yet, so these are pretty much just suggestions, I can't really say what does or doesn't work with Vista and DS 6.9.
Brian Hawver
Systems Engineer
Yaskawa America, Inc.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.
hi...i am new to network
hi...i am new to network administration..please help me over these...how to change domain\username to username@domain?
Not sure what your questions is...
I guess I am not sure what your question really is. Are you asking how to change the Domain Account in the DS console? Or are you asking how to set the UPN in AD?
To change it in DS, click on Tools ---> Options. Then click on the Domain Accounts tab. This is where you will set it.
Your AD administrator would be the one that would set or change the UPN in AD.
Brian Hawver
Systems Engineer
Yaskawa America, Inc.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.
Vista machines are added to the domain after rdeploy has layed the image down already right? Is this through a modify settings job? Sounds like possible LANMan settings. Do you have GPO's on the domain that change those settings?
in the package i was using DOMAIN/username so i tried Username@domain.com and that worked. I guess Vista no longer like DOMAIN/username thanks for your help
Glad I could help!
Brian Hawver
Systems Engineer
Yaskawa America, Inc.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.
Windows has never accepted DOMAIN/user for authentication. You use DOMAIN\user.
yeah sorry you are right i miskeyed in my message here
Would you like to reply?
Login or Register to post your comment.