2 servers can't communicate with different subnet, while all other devices can.
I have 3 locations and 3 subnets, 10.0.x.x, 10.1.x.x, 10.2.x.x. Each location has its own subnet.
I had a Cisco 1800 router in place for a point-to-point MPLS network setup to connect all 3 locations together.
I recently removed the MPLS network and replaced it with a site-to-site VPN network.
The gateway for the MPLS on the 10.1.x.x network was 10.1.0.1. I’ve removed that device and added the VPN gateway. The new gateway is also assigned the 10.1.0.1 address. After establishing the VPN tunnel, all servers and PC’s are able to communicate with the 10.0.x.x network except for 10.0.0.3 (DC) and 10.0.0.5 (Time clock server). As well, a ping from 10.0.0.3 to 10.1.0.1 is unreachable (see attached screen shot)
All PC’s and devices on 10.2.x.x can communicate perfectly with 10.0.x.x. The VPN tunnels are configured identically so I don’t believe the problem lies with the VPN configuration.
After removing the Cisco 1800 gateways and activating the VPN gateway 2 servers will not communicate with the 10.1.0.0 subnet. All PC’s in the 10.1.0.0 subnet can see and ping any other PC in the 10.0.0.0 subnet except for my 10.0.0.3 and 10.0.0.5.
It seems the problems lie within the servers themselves. I am not the original network administrator so these servers were initially configured by someone else.
I’ve disable windows firewall on both 10.0.0.3 and 10.0.0.5.
Does anyone have any suggestions as to why the servers can no longer communicate with the 10.1.x.x network after replacing the gateway?
Untitled-1.jpg
I had a Cisco 1800 router in place for a point-to-point MPLS network setup to connect all 3 locations together.
I recently removed the MPLS network and replaced it with a site-to-site VPN network.
The gateway for the MPLS on the 10.1.x.x network was 10.1.0.1. I’ve removed that device and added the VPN gateway. The new gateway is also assigned the 10.1.0.1 address. After establishing the VPN tunnel, all servers and PC’s are able to communicate with the 10.0.x.x network except for 10.0.0.3 (DC) and 10.0.0.5 (Time clock server). As well, a ping from 10.0.0.3 to 10.1.0.1 is unreachable (see attached screen shot)
All PC’s and devices on 10.2.x.x can communicate perfectly with 10.0.x.x. The VPN tunnels are configured identically so I don’t believe the problem lies with the VPN configuration.
After removing the Cisco 1800 gateways and activating the VPN gateway 2 servers will not communicate with the 10.1.0.0 subnet. All PC’s in the 10.1.0.0 subnet can see and ping any other PC in the 10.0.0.0 subnet except for my 10.0.0.3 and 10.0.0.5.
It seems the problems lie within the servers themselves. I am not the original network administrator so these servers were initially configured by someone else.
I’ve disable windows firewall on both 10.0.0.3 and 10.0.0.5.
Does anyone have any suggestions as to why the servers can no longer communicate with the 10.1.x.x network after replacing the gateway?
Untitled-1.jpg
Just a guess: maybe the windows servers defaulted to a /8 netmask, therefore not using the gateway?
Tamas
Tamas
ASKER
Running a tracert command returns nothing but * * * Request timed out.
Yes, from 10.1.x.x I can ping any devices in 10.0.x.x except for 10.0.0.3 and 10.0.0.5.
The netmask has remained 255.255.255.0
I have a support call into Microsoft Server support.. Hopefully they can shed some light on this misscommunication. I would still like to hear other suggestions from EE experts while I wait for the call back.
Yes, from 10.1.x.x I can ping any devices in 10.0.x.x except for 10.0.0.3 and 10.0.0.5.
The netmask has remained 255.255.255.0
I have a support call into Microsoft Server support.. Hopefully they can shed some light on this misscommunication. I would still like to hear other suggestions from EE experts while I wait for the call back.
ASKER
My firewall technition has determinined it is being cause by the DHCP server on my network. I can't see anything setting that looks incorrect. Any ideas?
Are you using a dhcp server to assign IPs in the 10.1.x.x network? In that case, check that the gate way of the scope is set correctly.
What is the gateway used by 10.0.0.3 and 10.0.0.5? Was this gateway also changed?
Where is the firewall situated in the network?
What is the gateway used by 10.0.0.3 and 10.0.0.5? Was this gateway also changed?
Where is the firewall situated in the network?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Microsoft Support fixed this problem for me.
What about communication from other machines in the 10.0.x.x to 10.1.x.x . Does the ping to this network work from machines in 10.0.x.x other than the DC and time server?