I like "Why? Because M$ can!". It has a nice ring to it.
Cheers
Jams
> -----Original Message-----
> From: owner-portmaster-users@livingston.com
> [mailto:owner-portmaster-users@livingston.com]On Behalf Of John Vozza
> Sent: Thursday, March 18, 1999 09:01
> To: Rick Davidson
> Cc: portmaster-users@livingston.com
> Subject: Re: (PM) nt quick disconnects
>
>
> Rick
>
> I have seen this when NT has lost its tcp/ip protocol. (And yes this can
> happen after working properly then wham its gone. Why? Because M$ can!)
>
> John
> -------------------------------------------------------------------------
> NetRom Internet Services 973-208-1339 voice
> john@netrom.com 973-208-0942 fax
> http://www.netrom.com
> -------------------------------------------------------------------------
>
>
> On Thu, 18 Mar 1999, Rick Davidson wrote:
>
> > PM3 2T
> > ComOS 3.8
> > Ameriwrech PRI
> > st. patty's day hangover
> >
> > got a customer who is dialing in with an NT server, it connects
> momentarily
> > and disconnects. the PPP trace shows it doing everything correctly
> > (username, password, ipcp config), as you see below we receive
> a terminate
> > request immediately after the succeeded connection. the machines MLPPP
> > dialup was working fine this morning using 2 generic 33.6
> modems. any ideas
> > on what is generating this termination request? line noise?
> >
> > **** S2: IPCP Open
> > **** LCP IPCP Open
> > **** Connection Succeeded
> >
> > Received IPCP_TERMINATE_REQUEST on port S2 of 4 bytes containing:
> > 05 06 00 08 00 00 00 02
> > Packet Info: Code: 0x05, ID: 0x06, 8 bytes.
> > [0x00], length: (0 bytes), [0x]
> > [0x00], length: (0 bytes), [0x]
> > [0x00], length: (0 bytes), [0x]
> > [0x00], length: (0 bytes), [0x]
> > [0x00], length: (0 bytes), [0x]
> > [0x00], length: (0 bytes), [0x]
> > [0x00], length: (0 bytes), [0x]
> > [0x0], length: (0 bytes), [0x]
> >
> > Sending IPCP_TERMINATE_ACK to port S2 of 4 bytes containing:
> > 06 02 00 04
> > Packet Info: Code: 0x06, ID: 0x02, 4 bytes.
> >
> ------------------------------------------------------------------
> ----------
> > ------------------------------------------------------
> >
> > these also came across in the debug, what might these mean?
> >
> >
> > Received UNKNOWN on port S2 of 14 bytes containing:
> > 0C 02 00 12 00 00 7F 2E 4D 53 52 [NP] [STX] [NULL]
> [DC2] [NULL] [NULL]
> > [DEL] . M S R
> > 41 53 56 34 2E 30 30 A S V 4 . 0 0
> >
> > Received UNKNOWN on port S2 of 15 bytes containing:
> > 0C 03 00 13 00 00 7F 2E 4D 53 52 [NP] [ETX] [NULL]
> [DC3] [NULL] [NULL]
> > [DEL] . M S R
> > 41 53 2D 31 2D 4C 41 57 A S - 1 - L A W
> >
> > Received UNKNOWN on port S2 of 10 bytes containing:
> > 00 0A 12 06 00 00 00 01 C3 2F [NULL] [NL] [DC2]
> [ACK] [NULL] [NULL]
> > [NULL] [SOH] [?]/
> >
> > TIA
> > Rick Davidson
> > Systems Administrator
> > Buckeye Internet Services, Ltd. www.buckeyeweb.com
> > 37841 Euclid Ave. Suite 7 Willoughby, Ohio 44094 USA
> > Make SPAM illegal - Join CAUCE at http://www.cauce.org
> >
> > -
> > To unsubscribe, email 'majordomo@livingston.com' with
> > 'unsubscribe portmaster-users' in the body of the message.
> > Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>
> >
>
> -
> To unsubscribe, email 'majordomo@livingston.com' with
> 'unsubscribe portmaster-users' in the body of the message.
> Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>
>
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>