davidsurkov
asked on
TCP/IP CP reported error 733: a connection to the remote computer could not be completed
SBS2003 SP2 sudenly stopped receiving remote PPTP connections.
All users report the same error:
TCP/IP CP reported error 733: a connection to the remote computer could not be completed. You might need to adjust the protocols on this computer.
I've spent almost a week already trying to resolve this - nothing found on MS KB or other sites helped as the problem seems to be more complicated rather than just typical misconfiguration.
What's interesting is that there is no
"PPP adapter RAS Server (Dial In) Interface"
found on the server when running "ipconfig /all", which should be present.
During the connection it gets through to the final stage "Registering your computer..." and then it fails with the error above.
I've tried disabling/enabling RRAS, changing RRAS DHCP to static pool - nothing happens. It seems like there is a problem with RAS Network Adapter in the registry, but I am not sure how to repair it.
Has anyone seen this problem before?
All users report the same error:
TCP/IP CP reported error 733: a connection to the remote computer could not be completed. You might need to adjust the protocols on this computer.
I've spent almost a week already trying to resolve this - nothing found on MS KB or other sites helped as the problem seems to be more complicated rather than just typical misconfiguration.
What's interesting is that there is no
"PPP adapter RAS Server (Dial In) Interface"
found on the server when running "ipconfig /all", which should be present.
During the connection it gets through to the final stage "Registering your computer..." and then it fails with the error above.
I've tried disabling/enabling RRAS, changing RRAS DHCP to static pool - nothing happens. It seems like there is a problem with RAS Network Adapter in the registry, but I am not sure how to repair it.
Has anyone seen this problem before?
Brian Pierce
I assume you have read http://support.microsoft.com/kb/168720
ASKER
yes, I've read that article.
The only thing I have not done is reinstalling TCP/IP for which, I suppose, I have to be at the server and not connected remotely to it.
Anyway, if it comes to it, how do I reinstall TCP/IP on the SBS2003 server without damaging everything else?
The only thing I have not done is reinstalling TCP/IP for which, I suppose, I have to be at the server and not connected remotely to it.
Anyway, if it comes to it, how do I reinstall TCP/IP on the SBS2003 server without damaging everything else?
Any chance this occurred after installing SP2 ?
This is known to "break" VPN access in some cases.
If so it seems to me the solution is to remove the existing VPN configuration, and disable RRAS, then re-build the VPN with the "Configure Remote Access" SBS wizard (must use wizard). However, we can assist further with that if SP2 might be the problem.
This is known to "break" VPN access in some cases.
If so it seems to me the solution is to remove the existing VPN configuration, and disable RRAS, then re-build the VPN with the "Configure Remote Access" SBS wizard (must use wizard). However, we can assist further with that if SP2 might be the problem.
ASKER
This occured before installing SP2, I installed it as part of trying to fix the problem.
>If so it seems to me the solution is to remove the existing VPN configuration,
what do you mean exactly by this?
I have tried to Disable and then Configure and Enable RRAS from RRAS MMC, but I have not tried SBS "Configure Remote Access" as I thought it is the same thing. Will try that.
Has anyone found suspecious the fact that
"PPP adapter RAS Server (Dial In) Interface"
is not seen after running "ipconfig /all"?
>If so it seems to me the solution is to remove the existing VPN configuration,
what do you mean exactly by this?
I have tried to Disable and then Configure and Enable RRAS from RRAS MMC, but I have not tried SBS "Configure Remote Access" as I thought it is the same thing. Will try that.
Has anyone found suspecious the fact that
"PPP adapter RAS Server (Dial In) Interface"
is not seen after running "ipconfig /all"?
>>"have not tried SBS "Configure Remote Access" as I thought it is the same thing. Will try that."
I doubt that creating the tunnel manually is you problem, but with SBS it is very important to use the wizards as so many components are interrelated. If you want to do so, disable RRAS in the RRAS console, and then run the wizard by going to Server Management | Internet and E-Mail, and |"Configure remote access". It configures the VPN, routing, firewall, and name resolution, when used in conjunction with the "Create remote connection disk" client end. See:
http://www.lan-2-wan.com/SBS-VPN-instr.htm
>>"anyone found suspecious....is not seen after running "ipconfig /all"?"
Maybe <G>. The PPP adapter will not show up until the first client connects. I am not sure if it remains after they disconnect or not. DHCP leases are like that too. When the first user connects a block of 10 leases is reserved. Until then, nothing.
I doubt that creating the tunnel manually is you problem, but with SBS it is very important to use the wizards as so many components are interrelated. If you want to do so, disable RRAS in the RRAS console, and then run the wizard by going to Server Management | Internet and E-Mail, and |"Configure remote access". It configures the VPN, routing, firewall, and name resolution, when used in conjunction with the "Create remote connection disk" client end. See:
http://www.lan-2-wan.com/SBS-VPN-instr.htm
>>"anyone found suspecious....is not seen after running "ipconfig /all"?"
Maybe <G>. The PPP adapter will not show up until the first client connects. I am not sure if it remains after they disconnect or not. DHCP leases are like that too. When the first user connects a block of 10 leases is reserved. Until then, nothing.
I was just looking into 733 errors. Most often due to the client not receiving a DHCP address. The wizard will also configure DHCP for the clients, so might be worth a shot.
SBS does not recommend using a DHCP relay agent, and SBS must be your DHCP server.
SBS does not recommend using a DHCP relay agent, and SBS must be your DHCP server.
ASKER
1. Disabled RRAS from its console.
2. Restarted the server.
3. Went through SBS Configure Remote Access wizard.
The problem is still the same.
DHCP Server is on the same SBS server and has always been there.
>>"anyone found suspecious....is not seen after running "ipconfig /all"?"
>Maybe <G>. The PPP adapter will not show up until the first client connects. I am not sure if it remains >after they disconnect or not.
According to other SBS2003 servers I have access to, the "PPP adapter" seems to be there all the time even if there are no active connections. Not sure though when exactly it appears...
>DHCP leases are like that too. When the first user connects a block of 10 leases is reserved. Until >then, nothing.
I can see in "DHCP Leases" there are 6 IP addresses allocated to the server.
2. Restarted the server.
3. Went through SBS Configure Remote Access wizard.
The problem is still the same.
DHCP Server is on the same SBS server and has always been there.
>>"anyone found suspecious....is not seen after running "ipconfig /all"?"
>Maybe <G>. The PPP adapter will not show up until the first client connects. I am not sure if it remains >after they disconnect or not.
According to other SBS2003 servers I have access to, the "PPP adapter" seems to be there all the time even if there are no active connections. Not sure though when exactly it appears...
>DHCP leases are like that too. When the first user connects a block of 10 leases is reserved. Until >then, nothing.
I can see in "DHCP Leases" there are 6 IP addresses allocated to the server.
I was able to duplicate your error. Whether the issue is the same, remains to bee seen.
I set up a new VPN on a clean 2003 (non-SBS) server. The PPP adapter was not visible in an ipconfig. I tried connecting and failed with a 733 error. The PPP adapter did then show up, but with a 0.0.0.0 address. In its default DHCP state; under properties of the RRAS server, in the RRAS management console, if you click on the IP tab, DHCP should be checked, and the client should receive an IP, but in this case did not.
I was able to resolve in 2 ways.
1) on the IP tab at the bottom of the page you can choose the adapter to associate with the VPN. "Allow RRAS to select adapter" was chosen, which usually works, but changing to the WAN adapter resolved the issue.
2) most often with RRAS again on the IP page, you set up a static address pool for the VPN clients. With SBS, this is not supposed to be necessary. However, doing so, in my case also resolved the problem.
Seems the RRAS DHCP service doesn't know what scope to pull the IP from without fixing with #1 or #2 above, and results in a 733 error.
Perhaps that will help.
I set up a new VPN on a clean 2003 (non-SBS) server. The PPP adapter was not visible in an ipconfig. I tried connecting and failed with a 733 error. The PPP adapter did then show up, but with a 0.0.0.0 address. In its default DHCP state; under properties of the RRAS server, in the RRAS management console, if you click on the IP tab, DHCP should be checked, and the client should receive an IP, but in this case did not.
I was able to resolve in 2 ways.
1) on the IP tab at the bottom of the page you can choose the adapter to associate with the VPN. "Allow RRAS to select adapter" was chosen, which usually works, but changing to the WAN adapter resolved the issue.
2) most often with RRAS again on the IP page, you set up a static address pool for the VPN clients. With SBS, this is not supposed to be necessary. However, doing so, in my case also resolved the problem.
Seems the RRAS DHCP service doesn't know what scope to pull the IP from without fixing with #1 or #2 above, and results in a 733 error.
Perhaps that will help.
ps- after making changes to RRAS, to be sure they are applied, it is often a good idea to right click on the server name and choose "all tasks", "restart"
ASKER
Thanks, RobWill, for your attempts to investigate the problem.
>1) on the IP tab at the bottom of the page you can choose the adapter to associate with the >VPN. "Allow RRAS to select adapter" was chosen, which usually works, but changing to the WAN >adapter resolved the issue.
I only have one Network Adapter, so this option is not available.
>The PPP adapter was not visible in an ipconfig. I tried connecting and failed with a 733 error. The PPP >adapter did then show up, but with a 0.0.0.0 address.
In your case it is clearly an issue with DHCP and issuing IP addresses, because during the connection PPP adapter pops up with the 0.0.0.0 address. In my case, however, PPP adapter never shows up, so I tend to think the problem is deeper than just with DHCP.
I think, I am going to somehow re-install TCP/IP...
>1) on the IP tab at the bottom of the page you can choose the adapter to associate with the >VPN. "Allow RRAS to select adapter" was chosen, which usually works, but changing to the WAN >adapter resolved the issue.
I only have one Network Adapter, so this option is not available.
>The PPP adapter was not visible in an ipconfig. I tried connecting and failed with a 733 error. The PPP >adapter did then show up, but with a 0.0.0.0 address.
In your case it is clearly an issue with DHCP and issuing IP addresses, because during the connection PPP adapter pops up with the 0.0.0.0 address. In my case, however, PPP adapter never shows up, so I tend to think the problem is deeper than just with DHCP.
I think, I am going to somehow re-install TCP/IP...
ASKER
I will try to reinstall TCP/IP according to these articles:
http://support.microsoft.com/kb/325356
http://support.microsoft.com/kb/317518/
http://support.microsoft.com/kb/325356
http://support.microsoft.com/kb/317518/
Sounds like a reasonable route to go. Let us know how you make out.
--Rob
--Rob
ASKER
The following sequence solved the problem:
1. netsh int ip reset resetlog.txt
2. netsh winsock reset
3. Re-configure IP settings for LAN, as they were reset to Automatic
4. reboot
1. netsh int ip reset resetlog.txt
2. netsh winsock reset
3. Re-configure IP settings for LAN, as they were reset to Automatic
4. reboot
Good to hear you were able to resolve. The need for Winsock would indicate some sort of corruption.
Thanks for the update.
Cheers !
--Rob
Thanks for the update.
Cheers !
--Rob
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.