Conference gyro::internet_toolss

> I just installed a network card (3c590b-combo) in my gateway system 
> running W95.  I added it using the control panel add device which went 
> ok but now I cannot use netscape or any other application with dialup 
> ppp connection.

	I had a problem when my system was configured for both
	Ethernet and Dial-Up.  Some of the processes over Ethernet
	were using the TCP/IP address I had configured for Dial-Up.

	A work-around was to create separate "Hardware Configurations"
	(Control Panel->System) where one contained the Ethernet
	card and the other contained the "Dial-Up" adapter.  On
	startup you have to choose a hardware configuration from
	a list (unless Windows 95 Plug-and-Play can figure it out).

    
    
    				Did you add the device 2 times in the
    device tables with separate configurations ? Will I have to reboot 
    to use each configuration ? 
    
    				Thanks , Frank 

Re. 0

I (and many others) experienced this problem when using Altavista Tunnel
Personal Edition, and at that time the dual hardware configuration was the
only workaround. Yes, you must reboot to switch from one config. to other.

I would recommend that you take a look to the Tunnel support Forum (you can find
it in the Tunnel Home Page). There a few topics covering this issue and may be
in the last months somebody has found a less akward workaround. 

Luis

    This is a well documented problem with Windows95 which is fixed by
    applying the ISDN 1.1 Accelerator Pack from Microsoft.  You can find it
    at 
    
    http://www.microsoft.com/windows/common/aa2725.htm
    
    This fix is applicable even if you are not using ISDN, so don't let the
    name fool you.  I have been running with the Accelerator pack using a
    modem/PPP connection, a Ethernet IP connection and the Tunnel.  It
    works great!
    
    As an alternative, you could purchase a new system that is loaded with
    Windows 95 OEM SR2.  This includes the bits in the ISDN update.  
    
    Gary

    Well documented bug?  The "bug" is only if you have 3 or more network
    interfaces.  A situation you get into when you use the Tunnel software
    and a local Ethernet card.  ("PPP" + "Tunnel" + "Ethernet").  I don't
    think this is the situation the original noter is in.
    
    If you want to have a local private TCP/IP on your Ethernet *and*
    dial-in, the key is to configure your TCP/IP routes correctly.  With
    or without the Tunnel or the ISDN patch.
    
    --Ron

    The following Microsoft KB article is the problem I was refering to 
    in .-2 that the ISDN update fixed, at least in my case.  The PPP
    adapater never receives an address when IP is bound to a NIC as well as
    to the Dial up adapter.
    
    -----------------
      
    PSS ID Number: Q140460
    Article last modified on 10-04-1996
    PSS database name: WIN95X
     
    95
     
    WINDOWS
     
    
    ---------------------------------------------------------------------
    The information in this article applies to:
     
     - Microsoft Windows 95
    ---------------------------------------------------------------------
     
    SYMPTOMS
    ========
     
    If you have two or more network adapters in your computer and you are
    using Dial-Up Networking to connect to a network using the TCP/IP
    protocol, you may not be assigned an IP address and may not be able to
    use a static IP address. When this occurs, running Winipcfg.exe shows
    an
    IP address and subnet mask of 0.0.0.0, even though you are connected
    with
    the TCP/IP protocol.
     
    CAUSE
    =====
     
    This problem can occur when you have two or more network adapters
    installed with TCP/IP bound to each, and you have TCP/IP bound to the
    Dial-Up Networking adapter.
     
    RESOLUTION
    ==========
     
    Use the following steps to work around the problem:
     
    1. In Control Panel, double-click the Network icon.
     
    2. Click one of the network adapters. (NOTE: Do not click the Dial-Up
       Networking adapter.)
     
    3. Click Properties.
     
    4. On the Bindings tab, click the TCP/IP check box to clear it, and
       then click OK.
     
    5. If you have more than two network adapters, repeat steps 2-4 until
       TCP/IP is bound to only one network adapter and the Dial-Up
    Networking
       adapter.
     
    6. Click OK until you return to Control Panel. When you are prompted to
       restart your computer, do so.
     
    STATUS
    ======
     
    Microsoft has confirmed this to be a problem in Microsoft Windows 95.
    We
    are researching this problem and will post new information here in the
    Microsoft Knowledge Base as it becomes available.
     
    KBCategory: kbnetwork kbenv kbpolicy
    KBSubcategory: win95 dun
    Additional reference words: 95
    =============================================================================
    Copyright Microsoft Corporation 1996.
    
    
     
    
    

    
    			I will load the patch and see how it goes ,thanks 
    	for the replies . I will let you know the results . 
    
    			Thanks again , Frank 
    

Frank, I'm sure the ISDN accelerator pack will help.  This is definitely a 
problem for ANY system with 2 network adapters or more who try to connect
to a dial-up.  Basically, the stack is corrupt before you dial up and you 
aren't assigned a network address (do a route print and you won't see
any information for your dial-up).

Microsoft basically never tested multihomed configurations for Windows 95.
When we first reported this bug to them, their answer was "Windows 95 was
never inteded as a multi-homed operating system".  Not sure they ever would
have fixed it if they weren't bit by it themselves with ISDN.

As far as the advice to check the tunnel home page, I'm afraid that is
on a system which is no longer on Digital's network.

Jeff

    
    			Thanks for all of the support , I don't think my
    	system or me could have taken 1 more reboot from changing
    configurations . The ISDN patch did fix the problems . I was on the
    verge of taking the network card back to the store . 
    
    			Thanks , Frank