Conditional forwarding in Windows server with 2 different gateways
We currently have a Cisco firewall/router (x.x.x.1) handling routing for a dedicated private circuit that securely connects our business with our vendor.
We also have a Fortinet firewall/router(x.x.x.4) for our internet service through our local ISP.
Each local PC is configured with the .1 Cisco as the default gateway. From my understanding (don't have access to the Cisco but this is what I'm being told) the Cisco has a default route using the .4 Fortinet device.
From my understanding, all traffic not meant for our vendor is routed back to the .4 Fortinet router via that default route in the Cisco router.
There are 2 conditional forwarders configured in the local DNS server that point to IPs on the vendor's network. I'm assuming DNS servers at their location. I'm guessing since the PCs have the .1 router as default gateway and along with the conditional forwarders is what is routing traffic to the correct circuit. I should ask, am I correct in assuming the conditional fwders are pointing all vendor traffic to the next hop over the .1 gateway and if the traffic isn't asking for that specific next hop the conditional fwder is providing it is routed back through the default gateway of .4?
What I'm trying to figure out is how to correctly re-configure all PCs to use the .4 as their default gateway. I want to do that because right now, using .1 as the gateway is causing the internet speeds to be very slow. When I test a PC by changing the gateway to .4 internet speeds are what I would expect. But then access to the vendor software doesn't work.
In order for the vendor software to work with .4 as the default gateway on the PC, do I need to have the Fortinet configured with static routes to the vendor's DNS servers or just back to the Cisco at .1?
We also have a Fortinet firewall/router(x.x.x.4) for our internet service through our local ISP.
Each local PC is configured with the .1 Cisco as the default gateway. From my understanding (don't have access to the Cisco but this is what I'm being told) the Cisco has a default route using the .4 Fortinet device.
From my understanding, all traffic not meant for our vendor is routed back to the .4 Fortinet router via that default route in the Cisco router.
There are 2 conditional forwarders configured in the local DNS server that point to IPs on the vendor's network. I'm assuming DNS servers at their location. I'm guessing since the PCs have the .1 router as default gateway and along with the conditional forwarders is what is routing traffic to the correct circuit. I should ask, am I correct in assuming the conditional fwders are pointing all vendor traffic to the next hop over the .1 gateway and if the traffic isn't asking for that specific next hop the conditional fwder is providing it is routed back through the default gateway of .4?
What I'm trying to figure out is how to correctly re-configure all PCs to use the .4 as their default gateway. I want to do that because right now, using .1 as the gateway is causing the internet speeds to be very slow. When I test a PC by changing the gateway to .4 internet speeds are what I would expect. But then access to the vendor software doesn't work.
In order for the vendor software to work with .4 as the default gateway on the PC, do I need to have the Fortinet configured with static routes to the vendor's DNS servers or just back to the Cisco at .1?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Ehm that is exactly what i was suggesting... so what would be the difference?...
ASKER
Sorry, I wasn't clear on if you were talking about adding routes to the PCs. Waiting for a list of IPs from the vendor before I can test.
ASKER
The static routes work like a charm.
ASKER