NT 4.0 and Ascend Pipeline 50

Thread View: comp.os.ms-windows.nt.pre-release

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Malcolm Hoar Sat, 02 Mar 1996 01:12

Author: Malcolm Hoar
Date: Sat, 02 Mar 1996 01:12

30 lines
1759 bytes

I have a small home LAN running NetBEUI and TCP/IP on Win 95 machines.
The Pipeline 50 ISDN was configured with ROUTE=YES, BRIDGE=NO. There
were no problems with NetBEUI traffic bringing up the ISDN line on
broadcasts etc.

However, when I installed NT 4.0 on one of the machines, the Pipeline
would dial my ISP *everytime* I logged into NT 4.0. The problem *only*
occurred on logins. Not on reboots or any other regular periodic event.

I tried installing filters on the Pipeline without any success.

Finally, I reconfigured NT and set the RAS Autodial Manager Service
to start on Manually (rather than the default of Automatic). This
appears to have solved the problem completely.

I am posting this is the hope that:

(a) It will save someone else the hours of grief I went through.

(b) Someone else with access to similar kit, a packet sniffer and
    sufficient knowledge of TCP/IP and NetBIOS can figure out
    what the RAS Autodial Manager Service is broadcasting that
    triggers the Pipeline to bring up the ISDN line.

--
|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| Malcolm Hoar             These are NOT my views. My views have   |
| malch@malch.com          been censored by the Communications     |
| http://www.malch.com/    Decency Act of 1996. Shpx gur PQN.      |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads