Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Win95, Novell & Pipelines
Why not just leave the connection permanently up (nailed, perm/switched,
whatever)?
Unless you have to pay usage charges (In Kansas City it's about $100 a
month for ISDN which is expensive but you get unlimited access) per
minute, per hour, etc. for the ISDN line there's no reason not to just
leave the connection up at all tiems...
> From: msheehan@sctcorp.com
> Date: Tue, 18 Aug 1998 11:22:10 -0400
> Subject: (ASCEND) Win95, Novell & Pipelines
>
> I am configuring a Pipeline 85 (v5.1Ap9, load b2a.p75) to hook to
> an Ascend Max. I've set it up for bridging IP, IPX and Appletalk
> using DHCP. Everything works fine using a Windows NT PC. I can
> bring up the ISDN line (IP Arp request) and access everything
> including Microsoft and Novell servers. The problem that I am
> having is that when using a Win95 PC and it boots up, the
> Pipeline's ISDN line is not up therefore there is no "true"
> connection to the network yet. Apparently, Win95 doesn't load
> any of the Novell drivers when there is not a network connection.
> Then, when the user activates the ISDN line (IP ARP request
> brings up the line) IP works fine, but they cannot get to any
> Novell servers. It appears that IPX isn't even loaded (only
> Microsoft stuff shows up in Network Neighborhood). While the
> ISDN line is up, if the user then reboots their Win95 PC they can
> then login to both Microsoft and Novell servers through the
> Pipeline.
>
> Is this a known issue using the Pipelines with Windows 95 PC's.
> Is there a way to have the Pipeline "trick" the 95 PC into
> thinking there is a connected Novell network even when the line
> is down?
>
> Thanks for your help!
>
> Maryann Sheehan
> SCT Corp.
> msheehan@sctcorp.com
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>