From: fmarshallx@remove_the_x.acm.org   
      
   I should add that the behavior on the "broken" system is identical to   
   behavior I see on a computer that doesn't have the VPN installed / running /   
   connected.   
      
   I can access all the same pages from another, unrelated computer *and* I   
   cannot access the *same* pages on the computer with the VPN client   
   installed.  This suggests there's something broken with the VPN   
   configuration on the target client computer.   
      
   Fred   
      
      
   "Fred Marshall"  wrote in message   
   news:Cbmdnc-WH_BjlHzfRVn-3w@centurytel.net...   
   > I'm trying to get one XP system to access web pages using a Cisco VPN   
   > client.   
   > The system had been working fine.  Details are below.   
   >   
   > One question I have is:   
   > Given that we see the Ethernet NIC interface and given that we see the VPN   
   > client as a network interface:   
   > How does the sytem decide which of these "interfaces" to use in supporting   
   > things like Internet Explorer?   
   > It *appears* that all the interfaces are working but those pages that   
   > require the VPN aren't coming up.  Thus my (probably dumb) question.   
   >   
   > Presently we can see normal web pages both http and https.  But we cannot   
   > access an https page that probably requires connection via the VPN.   
   >   
   > So, my other question is:   
   > How might this be fixed?   
   > I'm tempted to reinstall the VPN client, repair the TCP/IP stack, ....   
   >   
   > Any suggestions regarding both questions would be greatly appreciated.   
   >   
   > Thanks,   
   >   
   > Fred   
   >   
   > *****Background:   
   > We're working on a customer's system with *no* technical reference   
   > information or support.   
   > It's rather strange indeed but I'm sure we'll figure it out.   
   > I could use some advice / help:   
   >   
   > The system has the following:   
   >   
   > A Westell DSL Modem - working fine.   
   > (Initially, the modem was set up to be dialed by PPPOE software in the PC.   
   > I changed this so that the modem will dial and stay connected by itself.   
   > Maybe this was a mistake but I don't see how.)   
   >   
   > Ethernet NIC: as normal, an ethernet NIC shows up as a network interface.   
   >   
   > PPPOE interface: IF the PPPOE software is started, then it shows up as an   
   > interface.  But now that the modem is automatic, this software doesn't do   
   > anything.  So, I just don't start it up at all.  I've seen lots of systems   
   > transitioned from using "dialing" software to simply letting the modem do   
   > the connection work - so I'm very used to this part.   
   >   
   > There is a Cisco VPN client installed on the computer.  I'm not so used to   
   > this.....   
   > When the VPN client is started, it connects.  So far this seems good.   
   >   
   > So, the current network interfaces showing are:   
   > Ethernet NIC - connected with IP address DHCP from the modem.   
   > VPN "interface" - connected with IP address that must be coming from the   
   > other end of the VPN...   
   > PPPOE interface - not connected / used.   
   > Dialup connection - not connected / used.   
   >   
   > For the critical purpose of the sytem, Internet Explorer 6 is being used   
   > for all interfacing - to interactive web pages.   
   > The customer reports that the distant servers recently switched from http   
   > to https pages.   
   > After this was done, they report that one of the client computers stopped   
   > connnecting to the pages.   
   > So, our task is to get it working again.   
   > (Because all other clients in this system are working, we might assume   
   > that the switch to https has *nothing to do* with the problem).   
   >   
   >   
   >   
   >   
   >   
   >   
   >   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)