Quantcast
Channel: ฟอรัม Remote Desktop Services (Terminal Services)
Viewing all articles
Browse latest Browse all 25135

2003 Terminal Server Roaming Profiles randomly fail to load

$
0
0

I have 2 2003 terminal servers both on the same ESX host. They are identical (4gb ram). I just recently spun up a new 2008 R2 file share and moved their roaming profiles over from a server 2000 NAS. Now when users log in they are getting 1509 and 1511 errors in the event log. Not everyone is getting them however, and if the log off and log back on, it typically brings them in fine the second time without any errors.

The file share and the terminal servers are all on the same esx host, and those are pretty much the only servers on there. I am assuming it has to be something with the file share, as it didnt start occurring until the profiles were moved over (all the same rights were brought over).

I am not sure why this is happening or what the cause is, as I havent been able to find anyone else with the same issue. The 1509 errors all have "The specified network name is no longer available." in the DETAIL portion, whereas most other problems I have seen had Access Denied. The failure is also not happening on the same file.

The ESX host has 32 GB of Ram, 8 2.7 ghz processor and is connected to a SAN using iSCSI. The terminal servers do not handle more than 8 users totals between the two of them so I cant see resources being an issue. The only thing I havent tried is setting up a second NIC and doing NIC teaming, however the network traffic for this shouldnt be leaving the hosts virtual switch as everything is on the same host.

I have followed most of the recommended settings for setting up the profiles (although they range from 20-60 mb each) and running UPH Clean on one of the servers, but the issue is still happening.

Thoughts?


Viewing all articles
Browse latest Browse all 25135

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>