Anonymous_User Absent Member.
Absent Member.
1783 views

Client 4.91 and DUN: error 720

I am having a problem with DUN on a notebook PC running WinXP SP2. I am
also using the Novell Client 4.91 (I am pretty sure it is 4.91 SP2).
When I try to use DUN, I get anerror 720 (PPP Protocol error, DUN could
not negotiate a compatible set
of network protocols. Check all settings make sure connection is only
TCP/IP and that network only has 1 adapt.)

Is there a way to fix this issue with DUN networking on the client
4.91? I have tried to uncheck usage of the Novell Client and IPX/SPX
for the device which is connecting via DUN.

Thanks
Mike McWhinney
elja, Inc.

Labels (1)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Client 4.91 and DUN: error 720

Mike,

The Novell Client may not be directly related with the PPP error, but
its possible there are invalid entries or other corruption already present.
I've seen a couple Windows 2000 boxes in the past producing 720 errors
with VPN clients. In these cases it revolved around users
adding/removing firewalls, VPN clients or other network interfaces...

Newsgroups: novell.support.os.client.winnt-2k-xp
Date: Wed, 04 Sep 2002 20:42:33 GMT
Subject: RAS error message
http://tinyurl.com/4a3nb

I've read it can sometimes be addressed with resetting TCP/IP or Winsock...

Repair/Reset Winsock settings
http://windowsxp.mvps.org/winsock.htm

RAS Errors 611 and 720 With PPP or SLIP
http://support.microsoft.com/kb/123298

You may find a few suggestions by searching Forums.ModemHelp.Net...
http://forums.modemhelp.net/search.php

--
Tony Pedretti
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Client 4.91 and DUN: error 720

Tony,

Thank you for the reply.

We do not use any VPN components on this network, so the VPN issue is
irrelevant (I think). I tried the netsh fix to reset network settings
using the following:

netsh int ip reset resetlog.txt

This didn't fix the problem. It actually screwed up some of my network
properties for one network adapter. I had to use system restore to
bring back the system to the way it was before. I don't know if netsh
winsock reset catalog would mess up the adapter. I guess it can't hurt
to try it.

I found something that might be worth trying. From Microsoft's KB:

http://support.microsoft.com/default.aspx?scid=kb;en-us;810979



Mike

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.