• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

problem with windows authentication to DC on different subnet.

R

rasczak

Lifer
the gist of it is in the title, I've been having an issue with a workstation not being able to log on to the domain.

scenario:

workstation A is on 192.168.5.0 subnet

it's primary DC/DNS server is on subnet 192.168.5.0

secondary is on subnet 192.168.6.0.

both DC's are setup in as primary and secondary dns servers in network properties of NIC.

primary was shutdown due to a move, but now the workstation is unable to log on. Is this a common issue? Shouldn't I be able to log on to the domain using the secondary domain controller even though it's on a different subnet?

as for routing, we have a cisco catalyst 2900 doing the routing between subnets, I can ping workstation A from the secondary DC.

confused.
Joe.
 
RebateMonger, Yes I can. I logon as a local admin and ping everything. It's an unusual issue to say the least.
 
If you're using the Windows firewall on your DC, I believe the default configuration will block traffic originating from an outside subnet.
 
VinylxScratches said:
Do you have Sites and Services setup so that certain a subnet authenticate with certain DCs?
Click to expand...

Yes. Found the issue after I had setup the primary server. After logging in to workstation A, I found that the network properties had an incorrect setting for the secondary DNS. It was pointing to an older server that is no longer in service. Once I changed that to the correct IP of the Secondary DNS/DC, I did a test and took our primary DC offline. I was able to logon just fine with the new settings.

Thanks for your help.
 
rasczak said:
Yes. Found the issue after I had setup the primary server. After logging in to workstation A, I found that the network properties had an incorrect setting for the secondary DNS. It was pointing to an older server that is no longer in service. Once I changed that to the correct IP of the Secondary DNS/DC, I did a test and took our primary DC offline. I was able to logon just fine with the new settings.

Thanks for your help.
Click to expand...

^ Reason why you use DHCP on workstations.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top