Procurve 1800 24g VPN

[sockpuppet]

I have routing and remote access running on a windows 2003 server.
I replaced an unmanaged 3com 10/100 switch with a procurve 1800 24g switch and the VPN no longer works.
The firewall NAT's an external address to the internal address on one of the VPN servers network cards.
From the VPN server both the network cards work fine, I can ping the router from both cards.
If I move the network cable to another switch (Not procurve) the VPN works fine.

I'm guessing that the procurve won't forward the VPN traffic by default.

Anyone got any ideas on this?

[Jonathan Axford]

Hi,

Do you have any config on the 1800 that could be preventing the communication?

I.e ports in different VLANs etc?

If the 3Com was previously an unmanaged device, the Procurve should just slot straight in with its factory default settings.

It should not be stopping specific traffic as far as i know...

Let us know how the switch is configured...

[sockpuppet]

I have 2 of these 1800 24g switches, they are new out of the box, so they should have factory default settings. I haven't done any configuration on them yet.

I initially thought it could be a NAT problem as our firewall NAT's real world addresses to internal addresses, but if this was the case then our web server, citrix server and FTP servers would also fail.

[Joel Belizario]

Have you tested both switches or tested the suspect switch in another setup?

Maybe possible you have a faulty switch out of the box?

[sockpuppet]

I tried it with both switches, its unlikely they are both faulty.