Win2003 Server running Terminal Services -WinXPclients can't conne

  • Thread starter Thread starter NET_ADMIN_IT_GURU
  • Start date Start date
N

NET_ADMIN_IT_GURU

Guest
We have clients who have connected via dial up from offsite fine to a Win2K
server running Terminal Services, then thru VPN to our network.

We now have installed a Win2003 Server running Terminal Services with 4 CALs
for clients to connect, set up as per Session - not per Device.

When the client dials into the Win2003 server it connects dial up fine. When
it tries to connect then thru VPN, it recieves "Network Protocol Connections
Error 736 TCP/IP CP error".

The clients were able to connect fine before on the Win2K Server, and now
they are having problems connecting on Win2003 Server. I have checked every
settting that I know and am stumped!

ANy suggestions????

THANKS!
--
MCSE
NET ADMIN.
 
Re: Win2003 Server running Terminal Services -WinXPclients can't conne

As I understand you're dialing from terminal services VPN connection to
other network?

This is probably not terminal services problem, something is not configured
OK with VPN, try changing to PPTP VPN



--
____________________________________
Frane Borozan
Terminal Services and Citrix Presentation Server user logging
http://www.terminalserviceslog.com
 
Re: Win2003 Server running Terminal Services -WinXPclients can't c

Re: Win2003 Server running Terminal Services -WinXPclients can't c

On each client I should do this? We have users that have laptops. They dial
in from offsite locations through modem, then connect through VPN, then they
use Remote Desktop to get to a computer on our internal network to access
their files.

Is there a better way to do this??

"Frane" wrote:

> As I understand you're dialing from terminal services VPN connection to
> other network?
>
> This is probably not terminal services problem, something is not configured
> OK with VPN, try changing to PPTP VPN
>
>
>
> --
> ____________________________________
> Frane Borozan
> Terminal Services and Citrix Presentation Server user logging
> http://www.terminalserviceslog.com
>
 
Re: Win2003 Server running Terminal Services -WinXPclients can't c

Re: Win2003 Server running Terminal Services -WinXPclients can't c

First is this solving your problem? try changing on single client.
I am not VPN specialist I just suggest from my practice




--
____________________________________
Frane Borozan
Terminal Services and Citrix Presentation Server user logging
http://www.terminalserviceslog.com
 
Re: Win2003 Server running Terminal Services -WinXPclients can't c

Re: Win2003 Server running Terminal Services -WinXPclients can't c

Yes I am able to connect now. But when I connect thru VPN a message box comes
up on the server that says:

"Could not initialize communication profile: TCP/IP. Could not open a TCP/IP
socket. Already in use. The combination of IP address and recieve port is in
use by another program. Please edit the communication profile, click adnavced
and change either."

What/where is this referring to???

THX


"Frane" wrote:

> First is this solving your problem? try changing on single client.
> I am not VPN specialist I just suggest from my practice
>
>
>
>
> --
> ____________________________________
> Frane Borozan
> Terminal Services and Citrix Presentation Server user logging
> http://www.terminalserviceslog.com
>
 
Re: Win2003 Server running Terminal Services -WinXPclients can't c

Re: Win2003 Server running Terminal Services -WinXPclients can't c

I am really not familiar with that error, try other groups.




--
____________________________________
Frane Borozan
Terminal Services and Citrix Presentation Server user logging
http://www.terminalserviceslog.com
 
Back
Top