Setting up XP as PPP Server
Datawiz
I am developing an embedded system which utilises a commercial TCP/IP
stack & PPP (CMX Micronet). This is a DCE device. It will (eventually)
drive a GPRS modem. DCE issues 'CLIENT' & awaits 'CLIENTSERVER' before
beginning PPP negotiation.
With Win 98 'Dial up Server' using a 'NT type' 'null modem' driver,
the embedded device (the Client) successfully establishes the PPP
connection, and subsequent TCP/IP communication works fine.
Despite a lot of time & effort, I can't get to first base with a Win
XP Professional box (ie. PPP negotiation doesn't even get started).
I am using 'Incoming Connections' and the same 'NT type' 'null modem'
driver (on COM1) as I used with Win 98 for the XP/DCE device
connection.
So, I would very much appreciate some help with the following (and
anything else relevant)
1) I should be using 'Incoming Connections' shouldn't I ?
2) Do I need a 'null modem' driver for XP..if so, where can I get one?
3) How should I set up the XP (and maybe DCE) to start the PPP
negotiation?
4) How do I set up a 'ppp log file' in XP?
any help will be greatly appreciated.
PS: I can thoroughly recommend James Carlsons' 'PPP Design,
Implementation, and Debugging'...
regards to all
Allan Coyne
Datawiz
answering my own questions here....
> So, I would very much appreciate some help with the following (and
> anything else relevant)
> 1) I should be using 'Incoming Connections' shouldn't I ?
Yes, that's right.
> 2) Do I need a 'null modem' driver for XP..if so, where can I get one?
Yes you do - the one you used for Win98 works OK
> 3) How should I set up the XP (and maybe DCE) to start the PPP
> negotiation?
Standard 'Incoming connections' setup
> 4) How do I set up a 'ppp log file' in XP?
Still don't know the answer to this one.....
My problem was that I was using Frontlines' SerialTest Async + Spy to
sniff COM1 (on which I set up my incoming connection).
SerialTest Async + Spy cannot operate with the Microsoft serial.sys
driver, so it must be replaced with an alternative supplied by
Frontline.
Predictably (well, at least Murphys' law says so), 'Incoming
Connections' won't start PPP using Frontlines' serial.sys...sigh
Alan J. McFarlane
> Hello All,
>
> I am developing an embedded system which utilises a commercial TCP/IP
> stack & PPP (CMX Micronet). This is a DCE device. It will (eventually)
> drive a GPRS modem. DCE issues 'CLIENT' & awaits 'CLIENTSERVER' before
> beginning PPP negotiation.
>
Well I take it from your follow-up posting that you've fixed this. I was
going to say that you need to send "CLIENT" twice and RRAS answers after two
"rings", see e.g.
"145879 - How to Set the Number of Rings for RAS Auto-Answer in Windows NT
4.0/Windows 2000"
http://support.microsoft.com/default.aspx?scid=kb;en-us;145879
and
http://homepage.ntlworld.com/alanjmcf/comms/infrared/IrDA%20FAQ.html#_Toc40792045
Was that not necessary?
As to logging, I'm not near an XP machine at the moment but does the
following apply "234014 - HOW TO: Enable PPP Logging in Windows"
http://support.microsoft.com/default.aspx?scid=kb;en-us;234014 it recommends
e.g. "netsh -c ras set tracing PPP enable".
--
Alan J. McFarlane
http://homepage.ntlworld.com/alanjmcf/
Please follow-up in the newsgroup for the benefit of all.
Datawiz
"Alan J. McFarlane" <alan...@yahoo.com> wrote in message news:<2cpya.8928$Mu3.1...@newsfep4-glfd.server.ntli.net>...
> Datawiz <dat...@pipeline.com.au> wrote:
> Well I take it from your follow-up posting that you've fixed this. I was
> going to say that you need to send "CLIENT" twice and RRAS answers after two
> "rings", see e.g.
> "145879 - How to Set the Number of Rings for RAS Auto-Answer in Windows NT
> 4.0/Windows 2000"
> http://support.microsoft.com/default.aspx?scid=kb;en-us;145879
> and
> http://homepage.ntlworld.com/alanjmcf/comms/infrared/IrDA%20FAQ.html#_Toc40792045
> Was that not necessary?
The embedded target issues up to 6 'CLIENT' strings approx 4 secs
apart, so RRAS gets its two rings.
I didn't even know XP expected two rings ...glad the target sent out
more than one. If it hadn't, I probably would have had more questions
here.. :)
>
> As to logging, I'm not near an XP machine at the moment but does the
> following apply "234014 - HOW TO: Enable PPP Logging in Windows"
> http://support.microsoft.com/default.aspx?scid=kb;en-us;234014 it recommends
> e.g. "netsh -c ras set tracing PPP enable".
Yes, you're right. I had found that, but hadn't yet got to posting the
answer.
All I need to do now is sort out why the target is not handling PAP
correctly...but that's a target, not an XP problem.
thanks again for you help
Allan Coyne