G
Guest
Network with about 80 pc'
2 subnets: 10.0.0.x,10.0.4.
1 AD\Domain Controller\AD Integrated DNS Server Running the Network (DNS=10.0.0.14
The Network Is connected to the Internet through a Third Party Router as our IS
This Company (Router) has a lot of Ports and services closed (10.0.0.7)
When DC has a Gateway of 10.0.0.7 to the router...Clients in the 10.0.4.x subnet cannot Ping the DC and therefore cannot Find a Domain Controller when they log in
If I change the DC's Gateway to another old (but still active) Gateway through another ISP (10.0.0.8
The Clients on 10.0.4.x can now Ping 10.0.0.14(The DC), and therefore find the Domain Controller to log in to the Domain
My question is Of what Importance is the Domain Controllers Gateway to Clients on the 10.0.4.x subnet, and for that matter the entire network
BTW..DNS settings are fine for all Clients
2 subnets: 10.0.0.x,10.0.4.
1 AD\Domain Controller\AD Integrated DNS Server Running the Network (DNS=10.0.0.14
The Network Is connected to the Internet through a Third Party Router as our IS
This Company (Router) has a lot of Ports and services closed (10.0.0.7)
When DC has a Gateway of 10.0.0.7 to the router...Clients in the 10.0.4.x subnet cannot Ping the DC and therefore cannot Find a Domain Controller when they log in
If I change the DC's Gateway to another old (but still active) Gateway through another ISP (10.0.0.8
The Clients on 10.0.4.x can now Ping 10.0.0.14(The DC), and therefore find the Domain Controller to log in to the Domain
My question is Of what Importance is the Domain Controllers Gateway to Clients on the 10.0.4.x subnet, and for that matter the entire network
BTW..DNS settings are fine for all Clients