Re: Can't do Bonding or MultiPPP

Charles Scott (cscott@freeway.net)
Thu, 19 Sep 1996 03:49:42 -0400 (EDT)

All:
I knew this was going to happen. No sooner do I post the message
below, then I get a breakthrough and get stuff working.
It seems that having the ports set to prompt for host (set sxx host
prompt) messes things up. Funny though, I think I rememember reading in
the app notes that everything could be the same with only a few
exceptions. I guess this would be one of those exceptions.
I have a little testing to do and have yet to get hunting working, but
at least I'm on the road, not in the ditch any more.

Thanks for listening.

Chuck

On Thu, 19 Sep 1996, Charles Scott wrote:

>
> All:
> I've banged my head against the wall enough on this one so it's time to
> put my misguided instincts aside and ask for help.
> We have a PM2E with a 5BRI and I have a Bitsurfr Pro on my ISDN line at
> home. I can connect at 56K or 64K on a single B channel but absolutely
> can't get 2 B's up and running, no how, no way!
> I've tried following the application notes on "ISDN-Bitsurfer Pro
> Config" from the Livingston server, to the letter. I've tried every
> possible combination of SPID's, having DN's, not having DN's, and every
> possible combination of dialing with 1 number, 2 numbers the same, 2
> different numbers, ad nauseam. I've tried connecting with terminal
> software and with PPP with Windows 95. I've tried Multilink PPP,
> Bonding, AIMUX, you name it. (argh!)
> It never appears that the second B channel is getting setup. Debug on
> the PortMaster only indicates a connection on a single B1. When I try
> Multilink PPP, one B channel gets connected and it looks like it's
> starting to establish a PPP connection but Windows 95 reports that it
> can't negotiate a network protocol (all I have enabled is TCP/IP).
> Like I said, I can connect on 1 B channel every which way, but not
> 2. Could it be that it's not me, that the line is somehow not right?
> My employees are starting to notice that something is wrong as I've come
> stumbling in at 10 am or so for the last few days. For their sake, anyone
> have a suggestion?
>
>
> Chuck
>