Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VPN error.

Status
Not open for further replies.
butchrecon

butchrecon

MIS
Jan 10, 2001
2,873
US
I get this message when users attempt to VPN in via the internet. Any ideas?

TCP/IP CP reported error 733: your computer and the remote computer
could not agree on PPP control protocols.
James Collins
Field Service Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.
 
Sort by date Sort by votes
Are you trying to connect using PPTP or L2TP? If PPTP, make sure that your firewall/router has PPTP pass-through enabled. More specifically, it has to be able to allow traffic on port 1723 using IP protocol 47 (also known as GRE - Generic Routing Encapsulation).

Are you able to get into the VPN server from a machine on your LAN? Marc Creviere
 
Upvote 0 Downvote
VNC is so simple to use, I've never had any problems with it except you need a good screen resolution for it to work. Can you un-install, then re-install and leave the default settings. Also, can you connect to a pc locally or another pc via the internet? If that doesn't work, do a search on google for VNC & Protocols. That's how I found out about the screen resolution problem. I loaded it on a new server and it just would not work. When I found the awnser, I changed the resolution and everythings fine. Good luck. Glen A. Johnson
Microsoft Certified Professional

"Curiosity is one of the most permanent
and certain characteristics of a vigorous intellect."
Samuel Johnson (1709-84); English author.

 
Upvote 0 Downvote
The server is an ISA 2000 Server. I dont know about trying from our LAN. I will look at that. James Collins
Field Service Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.
 
Upvote 0 Downvote
FilthPig,

That did not work. Any other Ideas. James Collins
Field Service Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.
 
Upvote 0 Downvote
Does this happen to all your users, or just some of your users?

I've seen a similar message when the VPN server or client uses more than just the TCP/IP protocol (NetBeui, IPX/SPX). If any protocol other than TCP/IP is used in the VPN negotiation, and the client calling in does not have that particular protocol installed on their computer (or vice versa), then an error message similar to yours would pop up.

If this is the case, you should go into your VPN/RRAS settings and uncheck all non-TCP/IP protocols.

On the client end, you may have to do something similar (remove all non-TCP/IP protocols) so that they only use TCP/IP when they VPN in.

Oh yeah, the funny thing is, even though I get that message, I still get connected through the VPN. However, it is very confusing and threw me off at first until I fully read the error message. In my case, it at the end of "could not agree on PPP protocols" I think it told me what the offending protocol was that could not agree to the PPP connection.

Hope that this is helpful.
 
Upvote 0 Downvote
It happens when TCP/IP is the only protocol used. James Collins
Field Service Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.
 
Upvote 0 Downvote
Yes. James Collins
Field Service Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.
 
Upvote 0 Downvote
are you connecting with a netbios name or tcp/ip address? Glen A. Johnson
Microsoft Certified Professional

"You cannot create experience. You must undergo it."
Albert Camus (1913-1960); French writer and philosopher
 
Upvote 0 Downvote
Actually via "mail.companyname.com" for the VPN connection. Does that make a difference? James Collins
Field Service Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.
 
Upvote 0 Downvote
try "mail.companyname.com:0" This is what I need to connect over the internet. I usauall connect to computername.domanename.com:0. Good luck. Glen A. Johnson
Microsoft Certified Professional

"You cannot create experience. You must undergo it."
Albert Camus (1913-1960); French writer and philosopher
 
Upvote 0 Downvote
Sorry that did not work. It would not even connect. The error 733 comes after connection as it is registering system on the network. Users get authenticated fine. James Collins
Field Service Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.
 
Upvote 0 Downvote

Just out of curiosity when the client does hook up through the VPN does he use the APIPA addressing scheme or is he given an IP address from the DHCP relay agent?
If he is getting an APIPA address, then this would give an error.
We had the same type of thing happen, the client could hook up every time, but we would get an error in event viewer, cant remember what number error it was.
The eventual fix was that the settings in RRAS was to automatically select the right interface, and it was always grabbing the wrong one. We set it to grab the right interface instead of doing it automatically. It then received an IP address from the relay agent and no more warnings.
I cant remember where I found the article, and I was doing my practicum there, and no longer work there. The boss had me find the problem as part of the practicum and it took almost a week of digging to come up with that fix.
I dont know if this has any bearing on your problem or not but I thought it might be a possibility.
 
Upvote 0 Downvote
Apparently that link wont work. It was not the one that discussed the change I mentioned.
 
Upvote 0 Downvote
silly question?

do you have your clients remote access rights enabled?

and also do you have their computer name included on AD?

and also check for the right ip address and subnet that shoudl be related on domain...

 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

DeepuM
  • Locked
  • Question
Web Response returned Web Exception : The underlying connection was closed error | Simphony & QS
Replies
0
Views
167
DeepuM
DeepuM
StevenFromSouth
  • Locked
  • Question
VPN Connects but cannot access remote network computers or folders
Replies
1
Views
116
StevenFromSouth
StevenFromSouth
bechna
  • Locked
  • Question
Windows Server and VPN Setup
Replies
1
Views
105
DrB0b
DrB0b
bechna
  • Locked
  • Question
Unable to connect to VPN windows server 2019
Replies
0
Views
85
bechna
bechna
FreeSoldier
  • Locked
  • Question
Server 2012 R2 VPN Encryption
Replies
1
Views
101
tacohunter
tacohunter

Part and Inventory Search

Sponsor

Back
Top