NT4 problem

I changed the secondary IP address on the NIC and rebooted, and now DHCP
and RRAS on the primary IP address don't work.

The DHCP server isn't logging any events. However RRAS is logging the
following event:

Event ID: 20050 Source: Router Type: Error
The user <domain\user> connected to port VPN<n> has been disconnected
because the computer could not be projected onto the network.

The error on the client is:
TCP/IP CP reported error 733: Your computer and the remote computer
could not agree on PPP control protocols.

None of the KB references for event 20050 seem to make any sense.

Anyone got any other ideas?

Re-check the RRAS settings based on this troubleshooting page,

ras error code
On the RAS server, check the DHCP settings. Error 733: the PPP control protocol for this network protocol is not available on the server. Resolution: ...
www.chicagotech.net/raserrors.htm

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
"Neil Rashbrook" <(E-Mail Removed)> wrote in message news:%(E-Mail Removed)...
I changed the secondary IP address on the NIC and rebooted, and now DHCP
and RRAS on the primary IP address don't work.

The DHCP server isn't logging any events. However RRAS is logging the
following event:

Event ID: 20050 Source: Router Type: Error
The user <domain\user> connected to port VPN<n> has been disconnected
because the computer could not be projected onto the network.

The error on the client is:
TCP/IP CP reported error 733: Your computer and the remote computer
could not agree on PPP control protocols.

None of the KB references for event 20050 seem to make any sense.

Anyone got any other ideas?

Robert L [MS-MVP] wrote:

> Re-check the RRAS settings based on this troubleshooting page,
>
> *ras* *error* code <http://www.chicagotech.net/raserrors.htm>
> On the *RAS* server, check the DHCP settings. *Error* *733*: the PPP
> control protocol for this network protocol is not available on the
> server. Resolution: *...*
> www.chicagotech.net/*ras**error*s.htm
> <http://www.chicagotech.net/raserrors.htm>

I ended up restoring the registry from before the IP change. This time
the IP change went smoothly. I had to fix up the broken workstation
trust relationships though, perhaps I should have tried to selectively
restore the system hive.