Hi all.
Well this time, I have hit upon a different problem, that is REALLY starting
to hack me off.
I have added RAS capability to my NT Service.
It wroks ok if I connect to ONE specific ISP that uses a Script to loging
(generic), BUT if I want to connect to an other ISP that doesn't use a
Script, It wont connect. I have been able to trace with the help of the ISp
and my own error trapping, that it is not Autherizing me.
Now, I have another app. (this is an app. I am converting to an NT Service)
and it uses the same code to produce a RAS connection, and it works
fine.....case i point, I used it to connect and send this email.
I then though, Ok, might be anNT Service thing, so I then created a COM DLL
and via a procedure in it, tried to make a connection to the ISP. IT does
EXACTLY the same thing !
It is almost like the component is nto being FULLY created, or its not being
given the full information.
Its also like if the application th RAS component it added to has no form,
it cant work properly.
Has anyone had this problemin the past ?
How did you get round it ?
Is there another way to connect to the net with RAS that you pass all the
information to ?
I have a unit that is a RAS header converion, but got a wee bit lost in all
the code.
Cheers, Jeremy Coulter
winmail.dat
