Can't authenticate properly on domain when connected to 2 physical wired networks
Posted on 2011-03-07
I have a domain workstation that is connected to a Windows Active Directory network (172.x.x.x) and another local network (192.x.x.x).
In order to successfully authenticate on the domain, I'm always forced to disable/disconnect the 192 network connection before I am able to.
I tried the following measures, but met with no success.
1. Using Network Connection properties, I manually set the metric values of the 172 network to 1 and the 192 network to 2.
2. I tried setting up a static route for the possible subnets where domain controllers are located to go through the 172 network.
3. I tried deleting the default route for 192 network.
How can I configure the networks so that they both stay active and I'm able to use the domain services normally?
One example of malfunction is that when trying to add a domain user using the "control userpasswords2" applet, I get an error that a trust relationship with the domain failed. It seems that any non-cached domain credentials cannot be verified.
Thanks in advance!