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!