Before I get into the details let me give the details of my modest little network:
I have 1 Cisco 3750 (SMI) serving as my core switch/router. This switch has InterVLAN Routing setup including the SVI's for 4 subnets (10.1.10.1 - .40.1). My access layer switches at Cisco 2960 L2 switches each assigned a specific VLAN and 2 trunk lines (dot1q) with etherchannel back to the core switch. My management VLAN is simply VLAN 1 with IP's of 10.1.1.1 - .1.4.
My WAN connection is currently a single L3 port with an IP of 192.168.119.2 connecting to the LAN port of a Linksys RV042 with Firewall & VPN services. The Linksys also has a route sending all 10.0.0.0 traffic to it's 192.168.119.1 LAN port or back to the core switch. I also have a default route set for 0.0.0.0 0.0.0.0 192.168.119.1 which effectively sends all non-LAN traffic out the the Linksys device and this is where it gets weird (*I do not have RIP turned on my core switch.):
I can ping both FQDN's and IP addresses from my core switch console and everything works fine. However, as soon as I try to do the same thing from a VLAN connection (or a PC connected to the VLAN) all I can get is DNS services (www.yahoo.com gets translated to an IP address) but after it hits the DNS I get timeout errors.
I ran a traceroute on the switch (and a tracert on the XP machine I'm testing from) and I go from the VLAN to the Linksys Device out to the ISP DNS Server and then nothing but timeouts after that.
From what I can tell the inbound IP traffic is not being properly delivered from the Linksys device back to the Core or from the core to the VLAN's.
To muddy the water even more I can ping a computer or resource on my Intranet on another VLAN/Subnet and my servers resolve the request without any problems!
I did go through and reset my switches and re-programmed them with just enough information to active IntraVLAN Routing and the default route to the Linksys.
After doing that all my computers on the VLAN's can access the internet. However, they work for about 5 minutes or so and then it's back to the timeout error. If I go into the command line on the host and ping the router and then the public IP address they magically start working again for about 5 minutes.
This could be the weirdest problem I have ever come across.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...