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

Re: (ASCEND) Callback to NT...



On Sun, 24 Aug 1997, Dan Merillat wrote:

> 
> Hey, arn't callback problems a FAQ by now (Yes, I checked...)
> 
> Ok, Local telcos are raping our users by the minute, so they are all
> screaming for ISDN callback...
> 
> So, how do I call back into win NT?  (Or 95)
> 
...
> 
> The exact same thing works for a pipeline.  In fact, the max tries to dial
> to the NT server, but instead of authenticating it just sits there
> transmitting at full 64k (recieve light on his end is on solid, and stats
> is going up about 4k/sec...)
> 
> Eventually the outgoing call fails with "c=40 p=75"
> or "PPP: LCP timeout" during "LCP State request"
> 
> Which makes sense, if it is transmitting garbage down the line.
> 
> Just realised it might be the lack of IP/Netmask... i forgot to put
> in the pool number to draw it from.  Would that cause that kind of error?
> Other ideas?  (I'll try testing with IP assigned... I don't remember what
> the PPP negotiation order is... does LCP handle the IP assignment?
> Somone have a quick breakdown on the order and meanings?)

How do you accept the incoming call-back from the MAX? With RAS server?
Then you have to define the IP Adress for the NT station in RAS server
settings. Define a pool of Ip adresses, in which you exclude all addresses
that are not wanted. 

For example:

MAX has 1.2.3.254, NT workstation should get 1.2.3.80
Define a pool with rang 1.2.3.80 to 1.2.3.254, and exclude 1.2.3.5 to
1.2.3.253. Then the NT station knows both his own IP adress (the first
from the pool) and the one of the MAX (the last pool address).

It's not working fine, but it works. (ou often get errors in the DUN
saying remote end has suddelny hang up etc.)

You can pack alltogether into a DOS batch script that works with the
"rasdial"-command. We use these scripts for home workers that do not know
how the correct order of mouse clicks should be (first DUN, then, after
the error message when the MAX hangs up, close DUN, and wait for the RAS
server to get the call-back).

ALL problems would be gone if MAX would support the MS extensions for
call-back. Then a nice little window would appear on the DUN-screen saying
"waiting for call-back from MAX" and no ugly scriptings would have to be
necessary. Anybody knows if these MS extensions are implemented in an
incremental release?

Elmar

----------------------------------------------------------------------
Elmar Haag             CENTAUR COMMUNICATION           Urbanstrasse 68
haag@centaur.de         Xlink PoP Heilbronn            74074 Heilbronn
http://www.centaur.de   Tel +49 7131 799 258     Fax +49 7131 799 260



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


References: