DRRAM
asked on
Change of the LOGONSERVER
I upgraded to a new server (DC) however the old server is still in place. On one of the client workstations the machine keeps logging in to the old server (run --> set--> LOGONSERVER=\\oldservernam e). I tried to change in via command line with set /p logonserver=\\new server
and whenever I retype set it shows that new server is the new logon server but whenever I log off and log back in the old server is the one that is logged into
please do you have an idea why the oldservername still displayed in the LOGONSERVER parameter ?
In fact, I checked the network settings on the client, and I saw the new DNS (new server DC).
Thanks in advance for your eventual answer.
and whenever I retype set it shows that new server is the new logon server but whenever I log off and log back in the old server is the one that is logged into
please do you have an idea why the oldservername still displayed in the LOGONSERVER parameter ?
In fact, I checked the network settings on the client, and I saw the new DNS (new server DC).
Thanks in advance for your eventual answer.
The LOGONSERVER variable does not determine which server is used to authenticate the client - it just records which one did.
You cannot use the SET option to change the server preferences
When authentication takes place, the client simply requests a list of available DCs from DNS by querying the SRV records. Assuming that you have a single site, and the SRV records have equal weight, the client will just use the one that responds first.
You cannot use the SET option to change the server preferences
When authentication takes place, the client simply requests a list of available DCs from DNS by querying the SRV records. Assuming that you have a single site, and the SRV records have equal weight, the client will just use the one that responds first.
ASKER
kcts: please
I agree that the client simply requests a list of available DCs from DNS
but in the DNS I remove the old DC....and in the dhcp server
please i wait your response
I agree that the client simply requests a list of available DCs from DNS
but in the DNS I remove the old DC....and in the dhcp server
please i wait your response
Set up Sites and Services and be sure and add your Network Object for the site in question to the correct Site. This will tell AD where you want the users on that Network to go for authentication.
It seems you are facing the issue with only one client PC.If this is the case check the host file on workstation and remove the entry of old server also remove the same from NIC.
Ran ipconfig /flushdns & ipconfig /registerdns and restart the PC.
If the old server exist in the network the client may authenticate to old server for various reason.
Make sure that on new DC GC is enabled.
I
It seems you are facing the issue with only one client PC.If this is the case check the host file on workstation and remove the entry of old server also remove the same from NIC.
Ran ipconfig /flushdns & ipconfig /registerdns and restart the PC.
If the old server exist in the network the client may authenticate to old server for various reason.
Make sure that on new DC GC is enabled.
I
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
THX
You're welcome :)
Krzysztof
Krzysztof
Thanks
Mike