General discussion

Locked

Dial in failing to Win2K Pro machine

By TGM ·
I am running a simple network with just two W2K Pro clients in it. One of the clients is connected via cable to a SMC Barricade Wireless router which is acting as a router and providing DHCP services. The other machine is wireless connected to the router using an SMC wireless card. The router is connected via ISDN to the internet. Each client machine is configured to use DHCP automatically. This is all working well.

I want to dial into one of the client machines via a built in modem. I have set up the "incoming connection" as standard ie "no tunelling", "assign IP automatically" etc.

When dialled from another W2k Pro machine not on the network the client answers and then drops the connection.

The event log on the dial machine says; "The user XXX\YYY connected to port COM3 has been disconnected because no network protocols were successfully negotiatated."

The dialling machine says "TCP/IP CP reported error 733. Your computer and the remote computer could not agree on PPP control protocol"

I have unchecked all the PPP options that I can find in the DUN properties and still get the same result.

My suspicion is that it is something to do with the DHCP server but I am getting very lost now.

Help please

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Dial in failing to Win2K Pro machine

by BobHo In reply to Dial in failing to Win2K ...

Have you checked this MS KB article:

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q168720&

Enjoy,

DrBob:&gt

Collapse -

Dial in failing to Win2K Pro machine

by TGM In reply to Dial in failing to Win2K ...

I have chased SMC and after a lot of to-ing and fro-ing it appears that the DHCP server on the Barricade doesn't wuite work like a DHCP server shuod and does support the allocation of IP pools for dial in clients. Back to the drawing board

Collapse -

Dial in failing to Win2K Pro machine

by TGM In reply to Dial in failing to Win2K ...

Thanks, I had seen this article but re-visited it. The problem is that most of the advice seems to assume you are running 2K Server and have access to much more control of RAS than you do under 2Kpro (unless I am missing something?)

I have done some more testing and believe more than ever it is something to do with the dial in not getting an IP lease from the DHCP server.
Why - because if is disable the network adaptor on the dialled machine (no reboot or anything)ie sever the link with theDHCP server and then dial in then everything works fine. It connects and authenticates as you would expect. Doing an "ipconfig" shows that it is connected with a valid IP address but with a subnet mask of 255.255.255.255. Is this normal?

Reconnecting the local network adaptor (still no reboot)and we are still ok. "Ipconfig" shows the local adaptor with a proper IP address and snm of 255.255.255.0 and the dial in as before.

Reboot and retry and we are back to the start with the dial in been rejected. Any ideas

Collapse -

Dial in failing to Win2K Pro machine

by TGM In reply to Dial in failing to Win2K ...

Just done some more testing/elimination.

I removed the wireless lan card from the dialed machine and reaplced it with a normal one. Connected this to the network and rebooted. Network connection all OK, Dialed in and got the same symptoms --- so it isn't the wireless card.

I also set up DUN on the "dialed" machine and "Incoming connections" on the dialing machine ie reversed the connection and tried that. The result... connection works exactly as you would expect, no errors.

There is abig dent in my wall where I keep hitting my head. Any saviours out there?

Collapse -

Dial in failing to Win2K Pro machine

by TGM In reply to Dial in failing to Win2K ...

This question was closed by the author

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums