52 Posts

April 15th, 2007 03:00

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.
Have you done this already?

30 Posts

April 16th, 2007 13:00

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?

30 Posts

April 16th, 2007 13:00

Thanks for the reply. I do have static routes on the firewall for each vlan. Those routes would be:
 
10.1.210.0 - gateway 10.1.210.4
10.244.68.0 - gateway 10.1.210.4
10.244.69.0 - gateway 10.1.210.4
10.244.70.0 - gateway 10.1.210.4
10.244.71 - gateway 10.1.210.4
206.152.208.x - gateway 10.1.210.4
 
 
I am going to set the switch back up in a test enviroment and see what i can figure out oday.

52 Posts

April 17th, 2007 12:00

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.

30 Posts

April 17th, 2007 16:00

I will try that tomorrow night, i need a night off from this one.
 
 
Thanks!
No Events found!

Top