I applied that fix prescribed in the article but it didn't seem to help, so I'm guessing that is not the issue either. · actions · 2006-Jan-30 6:04 pm · mjn
Event ID: 1053 Source: Userenv Source: Userenv Type: Error Description:Windows cannot determine the user or computer name. (
eventlog? Anyways I suggest you use below tool to know more about ports and corresponding services. Any other computers / Servers on the same vlan? ¬†(looking for filtering policies on the vlan) Media server... his comment is here Also look for fast retransmission as this would indicate loss as well.
Hopefully someone will read this and point out something that I'm not seeing! · actions · 2006-Jan-29 2:55 am · TrainHead41join:2005-05-08West Chester, PA4 edits TrainHead41 to mjn Member 2006-Jan-29 10:11 pm x 77 Guido Holly In our case, the Firewall blocked the communication from our Terminal Server to the domain controller on port TCP 1026. After trying other solutions, I was able to resolve the issue by removing the ''Client For Microsoft Networks'', rebooting, then adding the client back in, and rebooting again. Possible values for MaxUserPort are from 5000 to 65534 (the default value is 5000 when this key does not exist).
Then stop logon service, flush DNS and register DNS again with ipconfig /registerdns".