I think I found out what's causing the connection dropping - it's not
really the firewall, it's the dynamic NAT routing. Our admin doesn't
want to set up static NAT routing for the developers though if he can
help it - he says that this should be reserved for servers.
Huh, that sounds dubious.
Dynamic NAT for standard users to access the outer world, that's ok, but why NAT for access of internal resources?
In a local network or VPN there's no need for NAT, because the private address space you're probably using is well known inside the organization.
Seems to be just another example of weird stuff admins are inventing for some not-so-well understood reasons.
Additionally, a NAT gateway may not reshuffle its ports/addresses for an existing connection, which seems to happen here. I'd call that a bug too (the firewall vendor will probably call it a feature, "look, we're scrambling the ports to obfuscate data origins..." - well done!)
However, glad you found a workaround.
Regards, Andreas
---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
