ip communication problems

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We have two sites connected via a T1 connection. Until recently, our main
site had an ip range of 192.168.0.x, mask 255.255.255.0 and our secondary
site had an ip range of 192.168.1.x, mask 255.255.255.0. Routers on either
side of the T1 shuttled traffic between 192.168.0.2 and 192.168.1.2, and
everything worked just fine. Unfortunately, our main site grew at a faster
than expected rate and we needed additional addresses, so we reconfigured our
main sites range to 192.168.8.x, mask 255.255.252.0. Our routers were
reconfigured to shuttle traffic between 192.168.10.2 and 192.168.1.2. When
configured in this way everything works for about 15 minutes and then dies.
Only machines in the same subnet will continue to communicate with one
another. Our servers in the 192.168.10.x range can see each other, but not
the computers with dynamicly assigned ips in the 192.168.8.x range, even
though the subnet mask is set properly. For 15 minutes it works and then it
dies. If we reset the switches and servers it works again for another 15
minutes and then dies again. We got around the problem at the main site by
assigning all the servers ip addresses in each of the class C subnets (i.e.
192.168.8.x, 192.168.9.x, etc.), but the link between sites is failing after
15 minutes in the same fashion and we are uncertain as to how to fix it. Any
thoughts?
 
From the server at the main site:
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 172.20.0.1 172.20.0.10 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
172.20.0.0 255.255.0.0 172.20.0.10 172.20.0.10 1
172.20.0.10 255.255.255.255 127.0.0.1 127.0.0.1 1
172.20.255.255 255.255.255.255 172.20.0.10 172.20.0.10 1
192.168.1.0 255.255.255.0 192.168.10.2 192.168.10.1 1
192.168.8.0 255.255.252.0 192.168.10.1 192.168.10.1 1
192.168.8.1 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.8.255 255.255.255.255 192.168.10.1 192.168.10.1 1
192.168.9.1 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.9.255 255.255.255.255 192.168.10.1 192.168.10.1 1
192.168.10.1 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.10.255 255.255.255.255 192.168.10.1 192.168.10.1 1
192.168.11.1 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.11.255 255.255.255.255 192.168.10.1 192.168.10.1 1
224.0.0.0 224.0.0.0 172.20.0.10 172.20.0.10 1
224.0.0.0 224.0.0.0 192.168.10.1 192.168.10.1 1
255.255.255.255 255.255.255.255 172.20.0.10 172.20.0.10 1
Default Gateway: 172.20.0.1
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
192.168.1.0 255.255.255.0 192.168.10.2 1

From the server at the secondary site:

Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 172.20.0.1 172.20.0.2 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
172.20.0.0 255.255.0.0 172.20.0.2 172.20.0.2 20
172.20.0.2 255.255.255.255 127.0.0.1 127.0.0.1 20
172.20.255.255 255.255.255.255 172.20.0.2 172.20.0.2 20
192.168.1.0 255.255.255.0 192.168.1.55 192.168.1.55 20
192.168.1.55 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.55 192.168.1.55 20
192.168.8.0 255.255.252.0 192.168.1.2 192.168.1.55 1
224.0.0.0 240.0.0.0 172.20.0.2 172.20.0.2 20
224.0.0.0 240.0.0.0 192.168.1.55 192.168.1.55 20
255.255.255.255 255.255.255.255 172.20.0.2 172.20.0.2 1
255.255.255.255 255.255.255.255 192.168.1.55 192.168.1.55 1
Default Gateway: 172.20.0.1
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
192.168.8.0 255.255.252.0 192.168.1.2 1
 
If the computers lose connection may be DNS problem. The local DNS must
go to the local names resolutor, and this solve outside of the lan.
 
Back
Top