Closed
Bug 73346
Opened 24 years ago
Closed 24 years ago
Browser and mail go deaf when you connect to VPN
Categories
(Core :: Networking, defect)
Tracking
()
mozilla1.0
People
(Reporter: benc, Assigned: neeti)
Details
lchiang said there was bug on this, but I could not find it. Although it
releates to my experience while using NS6 as an AOL employee, I believe the
problem is sufficiently general to put here.
Using Netscape 6.0 from home, over a DSL connection.
My workplace network is available via a VPN that supposedly uses IPSec. I think
the relevant part here is that when I connect to the corporate network, my
routing tables get completely re-written, and basically everything points to the
VPN gateway.
In general, I've observed Communicator seems to survive this without problems,
but Netscape 6 seems to just go deaf after the VPN connection is made.
For example:
STEPS:
1- Start Netscape 6.
2- Wait for home page (http://www.news.com) to load. Normal browsing of the
public network works fine.
3- Connect to VPN.
4- Observe that all new browser attempts fail (new window, link clicks, etc.)
Also opening mail (and attempting to connect to the corporate mail server) fails
as well.
My feeling is that this is NOT a DNS caching problem (even if we cached IP's,
the target IP's have not changed).
I would do a packet trace to see if there is some aberant transmissions or
half-open connections, but the IPSEC connection encrypts everything on my home
network (argh).
|
||
Comment 2•24 years ago
|
||
this on windows, right? hmmm... i'm not sure what could be going on here.
perhaps this is related to the socket pair used by the socket transport service?
perhaps it needs to be recreated after IPSec comes online?
benc: what happens with localhost sockets... are they encrypted as well?
No, that bug is about a VPN package that filters mail. This is a problem with
the network config changing.
*** This bug has been marked as a duplicate of 26718 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
VERIFIED:
After studying the other reports, I have found that my system seems to fixate on
the old DNS server list.
So after switching networks, IP addresses work fine (for example, I can access
servers not visible to external DNS by using their IP address, but not by
hostname.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•