Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (ASCEND) Win95, Novell & Pipelines

Hi,

>> 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.

True. Rather - when the drivers cannot see any Netware network,
they don't load.

>> 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).

Not true. IPX _is_ loaded - but the Netware client is not, hence no
Netware networks in Network Neighborhood.

>> 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? 

All you have to do is to enable 'Dial Query' in IPX options under the 
connection profile ;-). This is not trick at all, is rather working as
designed.

What happens is the following:

When the Win95 machine boots, it sends out a request called 'Get
nearest server'. All Netware servers receiving this request answers,
and the workstation uses the nearest as the default routing server.
The nearest server is found by measuring the response time.

If the Netware client doesn't receive any responses, it assumes 
there's no Netware network present and doesn't load the client -
saving some memory.

On a large Netware network, there may be dozens of 'Get nearest
server' requests beeing broadcast all the time and you would 
definately not want the Pipeline to dial every time - if you have a
local server present.

So it is configurable - use the 'Dial Query ÿes' option.

If somebody from Ascend reads this:

What IS missing is an option to disable answers to *GNS' at all.
I have loads of problems with Pipelines answering to 'GNS' on
behalf of distant servers even though there's a local server 
present. Typically, the Pipe is faster than the local server, so
clients use a remote server as default router. This is NOT 
practical ;-).

Regards,
Lars

--
Lars Skjærlund, Network Consultant
Bukkeballevej 30, 2960 Rungsted Kyst, Denmark
Tel.: +45 70 25 88 10, Fax: +45 45 16 07 55
Mail: larsskj@inet.uni2.dk
http://inet.uni2.dk/home/skjaerlund
--


++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>