I had a similar experience. What resolved my issue was that I had to create static routes on my firewall that points to the different vlan subnets. I created a route for each network and used the gateway of the vlan that my firewall sat on.
Well just an update. After putting back the orginial switch i found a Printer with a Static IP was plugged into the wrong VLAN port. It was causing our internal network to CRAWL and very sporadic ping responses. Would a PC plugged into a wrong subnet casue this much disruption?
Try adding a route on your firewall pointing 10.1.210.4 to your firewall's external interace ip address. This would be a "host to host" route instead of a network route.
nlspears
52 Posts
0
April 15th, 2007 03:00
Cblair
30 Posts
0
April 16th, 2007 13:00
Cblair
30 Posts
0
April 16th, 2007 13:00
nlspears
52 Posts
0
April 17th, 2007 12:00
Cblair
30 Posts
0
April 17th, 2007 16:00