Can't connect more than one client at a time to Terminal Server in Win

[eofodile]

My client has 2 remote offices that connect back to a hub site via VPN. Clients are Windows Xp. I setup clients as terminal services clients to run a case managemrnt application stored on the win2k server at the main site. Here's my problem. My first client conmnects fine, but each time I try to connect additional clients to the terminal server, the first one disconnects with an error message indicating that the connection has been broken. I have checked my Terminal services configuration, and it is configured for unlimited connections. I also changed from the remote administration mode, which only allows one connection by an administrator. Can anyone help?

 

[stephenphillips]

Did you check your licensing. Is it possible that Terminal Services thinks you only have one license? Just a thought.

 

[eofodile]

I have been told that Windows Xp clients do not require a CAL as this comes with the client. Not sure what other licensing factors I should be looking at. I did notice that the server had issued temporary licenses to each of the clients that had connected...

 

[butchrecon]

You still need to set up license server on the Windows 2000 machine and register it. If this has been done we need to check settings. Is this a DC? 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.

 

[eofodile]

Win2K server is in fact a DC. These Windows XP terminal clients connect to the network via a pptp connection (VPN)over DSL.

 

[eofodile]

I also attempted to setup the licensing server, though I'm not sure I did it correctly. Can you refer me to a doc that describes setting up the license server? I do know that the Terminal server issued temp licenses to the clients that connected.

 

[dankelt]

Win2000/XP will require a CAL on the server to connect to a Terminal Server. You will not need a "Terminal Services CAL", you will only need that if you have pre 2000 clients. Also, when you are in Remote Administrator Mode, you can have two concurrent connections. Did you say the behavior was the same in either mode. If so, this makes me think it is somethine else besides licensing. I'd try removing T.S. and reinstalling in Remote Admin Mode. If it works in Admin Mode, switch it over to app mode, if it doesn't work, it just might be licensing.

 

[eofodile]

I just realized that this problem only occurs when I try to connect from 2 XP clients at the SAME site. I conducted a test with a colleague, havoing him connect via a VPN connection from his home while I did the same from mine. We were both able to establish Terminal Server connections from our respective homes without issue. The same thing doesn't work when I attempt from 2 Wks at the client site. Please help!!!

 

[eofodile]

I finally broke down and called Microsoft. $245.00 later, they claimed that this is a known problem with Linksys routers where it loses track of GRE packets and sends them to the wrong session, causing the Trem server to disconnect. I replaced the Linksys at the hosting site (The site with the term server) with an SMC router; Same thing happens...The VPN connections stay alive, but once I connect more than 1 client from the same remote subnet to the term server, I disconnect the first client. Now Microsoft wants me to replace the Linksys devices at the source network as well. I am not convinced this will do the trick. Does anyone have any theories about this? I am thinking that maybe it just isn't possible for terminal server to interprete inbound traffic from more than one host communicating through a single public IP address. (The clients use a private IP addres scheme, and are NAT'ed thru a public address.

 

[dankelt]

I am going to have to agree with Microsoft on this one. I beleive your problem lies in the VPN, not terminal services. I'm assuming you are using PPTP for your VPN. Do you have to establish a VPN connection before starting your Terminal Services session? I would try connecting directly to the server from T.S. This would tell you for sure if it is the VPN causing the problem. It sounds logical to me that the linksys could have problems NATing GRE packets. I know I had a heck of a time getting IPCHAINS to do it in the linux 2.2 kernel.