Win2003 Standard - Terminal Server Issue!

[TimCHTECH]

Hello, we recently upgraded our Windows 2000 Terminal Server to Window 2003 Standard. After getting the server all set up with its old IP settings and configurations, we set up the Terminal server. Everything was running great for a couple days but now we frequently get some error that prevents users from accessing the Terminal Server remotely. When the error is occuring, a user is unable to connect to the terminal server using its external public IP address but users connecting internally to its 192.168.x.x address are still able to connect perfectly and the Terminal server is still able to browse the network and the Internet.

After checking the Router settings (NetGear Cable/DSL Web Safe) it appears that everything is correct, and when the problem occurs reseting the Terminal server will allow users to connect Externally again. Anyone have any ideas?

 

[tianzhen99]

I had a similar problem. It finally turned out to be the switch that remembers another ethernet card for the IP number in its internal cache. The ISP helped resolving the problem. You may try "arp" to broadcast your new ethernet to the switch --- if it is the case.

 

[WillShakespeare]

This is from the white-paper, and may be of use:

Terminal Server Licensing Mode:
Terminal server in Windows Server 2003 supports the following licensing modes:
• Per Device License tokens are assigned to each device that connects to a particular terminal server
• Per User License tokens are assigned to each user that connects to a particular terminal server
In order to use a combination of User, Device, and External Connector licenses on single terminal server, you should configure your server in Per User mode.

By default, a terminal server running Windows 2000 that is upgraded to Windows Server 2003 is placed in Per Device mode. However, if the terminal server running Windows 2000 is in Internet Connector mode, the server is placed in Per User mode.

 

[WillShakespeare]

And the icing on the cake!:

Client License Distribution Per User
When a terminal server is configured in Per User mode, the terminal server must be able to locate a license server after the grace period has expired. While it is possible to install TS Per User CAL tokens on a license server, there is currently no method of assigning a TS Per User CAL token to a particular user account.

Client License Distribution for External Connector
There is currently no support in Terminal Server Licensing or the Microsoft Clearinghouse for the External Connector. In order to use an External Connector license, you will need to configure your terminal server in Per User mode.

 

[WillShakespeare]

Incidentally, the reason I posted the above quotes is because you may have your TS in Per Device mode which is default in most cases, and in that case your external users may not be able to obtain licenses given the restrictions above. So you might consider changing to Per User mode, which apparently from above, also uses Per Device CALs.

 

[TimCHTECH]

Sorry for the late reply to this thread, but I wanted to post a followup.

We are still having this problem. We have changed out the NIC to ensure that the terminal server wasn't losing connectivity through a faulty NIC.

As it stands right now, the Terminal Server will periodically start rejecting all external clients that are attempting to access it through it's public IP address that is being forwarded to it from the router, local clients connecting directly to it through it's 192.168.x.x address are still able to connect fine. While it's rejecting external clients the Terminal server is able to browse both the network and the Internet perfectly, along with no error messages being generated in the Event Log.

Resetting the Terminal server will again allow external users to connect to it, but within 12-24 hours usually it will again begin rejecting remote users. The server is currently set in per user mode, with more than enough licenses to spare.

Any help would be greatly appreciated, thanks!

 

[TimCHTECH]

When a terminal server is configured in Per User mode, the terminal server must be able to locate a license server after the grace period has expired"

This may be the issue, when we open up the Terminal Server Licensing, it says that "No licensing server is available in the current domain." Clicking Action >> Connect and typing in the Terminal Server name will allow it to connect to it, but upon closing the Licensing Window and reopening it, it again says the no licensing server is availble. And yes, The server has been activated.

 

[WillShakespeare]

Have you added the magic registry entry? If not, have a look at my FAQ in this conference: faq931-4850

hth,

Will
[Morning]

 

[TimCHTECH]

Late response, but we're still having this issue. I ran through your FAQ, Will and verified that everything was correct. I added the registry entry and the Terminal Server now sees itself under the Terminal Licensing, but it still starts rejecting clients after a while until it is rebooted. Any one have more ideas?