I have been tasked with providing support for two previously configured Cisco routers that connect two buildings Point to point T-1), that is all. Internet services are provided via a completely seperate circuit. The router were previously configured using EIGRP and bridge groups to pass IPX traffic. Unfortunately, I have now implemented a Windows server and cannot ping past either router and I am not sure if these routers are even configured correctly. I have experience configuring internet access routers and ACL however, never a point to point.
The two configs are below. As I said, any help would be greatly appreciated.
I have looked at your configs and while there are a few things that I wonder about and think that perhaps they could be optimized, I believe that fundamentally both router configs should work. I do not see anything in the router configs that should produce the symptoms that you describe.
I suspect that the problem may be in the configuration of the Windows server. You have not told us much about the server. It would help to know in which building the server is located. It would be important to know what IP address is configured on the server. And it would be most important to know what default gateway is configured on the server.
My guess at the problem based on your description is that the default gateway configured on the server is not the router on the local subnet. Or perhaps the address configured in not recognized by the router as local.
Thanks for sending the additional information. It does help clarify some things.
It sounds to me like the configuration of the Windows server is pretty simple: it probably has an interface address, an interface mask, and a default gateway which points to the firewall. It probably has no other routes defined. So it can communicate with anything on the local subnet and anything with a destination not on the local subnet is forwarded to the default gateway (the firewall).
I am not sure why the firewall does not forward packets to the other routers or to addresses in BldgB. Perhaps there is a policy that does not allow this forwarding. Your drawing suggests that there are other workstations in BldgA. Are they able to communicate with BldgB? If so is their default gateway set to be the firewall or to be the router? (I am guessing that if they can communicate with BldgB that their default gateway is the router.)
I believe that one solution would be to configure the Windows server with its default gateway to be the router interface. You may also be able to make some change on the firewall to permit forwarding the packets.
After looking at your network diagram, there are few things that you need to change on your configurations.
1. Firewalls don't forward packets to the same segment after receiving it just as a router does. You need to change the Windows server default gateway to the router's IP address. Since your router has a default route to the firewall for internet access, your server will still be able to access the Internet via the router.
2. You don't need the static routes configured on the Bldg 2 router since you are running EIGRP routing protocol. EIGRP automatically redistributes default routes to its routing table so you should be able to see the route to the Internet in Bldg 2 router via EIGRP.
3. If you're using the Bldg A server as a domain server, you need to add an 'ip helper-address 10.200.1.4' on the FastEthernet of Bldg 2 router to forward WINS request to the server.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...