Matt_Brfc Posted January 30, 2013 Author Posted January 30, 2013 Some servers have 2 nics but the majority only have a single interface, still having issues with this although I have not had much time to investigate any further recently.
Matt_Brfc Posted February 7, 2013 Author Posted February 7, 2013 Head Bashing! tried a whole range of things ranging from RDP config through to repairing the OS without much luck, cleared cached credentials and still no joy!! Arghh!
Matt_Brfc Posted February 25, 2013 Author Posted February 25, 2013 RDP is used on both servers and workstations, regardless of the platform or architecture this is apparent on al hosts.
rkeberdle Posted June 5, 2013 Posted June 5, 2013 Matt, Were you ever able to resolve this bizzare issue? I have the same issue with a Win 7 Ent PC on our domain that appears to be setup in an identical manner to other PCs just like that do not exhibit the behavior. I have read a lot of articles and experimented with a lot of settings but at this point am not any closer to resolving outside of replacing it. Rob
mac_shinobi Posted June 5, 2013 Posted June 5, 2013 Just wondering if you tried the below ( as per my above post ) Here is what you need to do if you have the same issue: - Run a command prompt (cmd.exe) as an Administrator - Type: netsh interface tcp set global autotuninglevel=disabled Disable the autotunning feature in Vista completely, and fit and lock the RWIN receive window to default value 65536 bytes.
rkeberdle Posted June 6, 2013 Posted June 6, 2013 Thank you for the suggestion mac_shinobi but unfortunately this did not have any impact on my issue.
MattRVBC Posted July 22, 2013 Posted July 22, 2013 Hi Guys, Sorry for the long period of time in getting back to you. Since I last posted I have a new machine which did work fine for sometime however I'm now back with the annoying "Initiating Remote Connection" issues again on Windows 7 Professional SP1. Tried various things and still no Joy! on the plus side it works on mac! Matt
chazzy2501 Posted July 22, 2013 Posted July 22, 2013 have you tried disabling the client and host firewalls? I have only port 3389 enabled on my host and client and it can get really slow sometimes but on others I have a manually set firewall its blazing?
MattRVBC Posted July 29, 2013 Posted July 29, 2013 Im still having problems with this, the issue seems to be PC related as the same issue applies to various profiles.
azinnc Posted September 11, 2013 Posted September 11, 2013 I am having the same issue. It takes forever to initiate the connection, then takes a while to authenticate. However, once I am connected, the speed is just fine. I have tried all of the suggestions in this thread, but am still having the issue. Other Windows 7 machines do not have the same issue, even when connecting to the same server. I have also verified that I have the latest NIC driver (Intel 82579LM Gigabit). Has anyone figured out how to fix this?
SYNACK Posted September 11, 2013 Posted September 11, 2013 Sounds like a nps / Nla issue to me, it may be hanging up trying to make sure everyone is who they say they are. 1
azinnc Posted September 13, 2013 Posted September 13, 2013 My computer is the only one having the issue. Other clients can connect very quickly. Remote Desktop is the only thing that has a slow initial connection. I have also noticed that while the connection is waiting to be initiated, the rest of my internet traffic becomes extremely slow, including basic web browsing. Once the connection is established, everything is nice and speedy. Any ideas?
azinnc Posted September 16, 2013 Posted September 16, 2013 Solved! I found that it was RDP protocol 8.0 that was installed in a Microsoft update found at Description of the Remote Desktop Protocol 8.0 update for Windows 7 SP1 and Windows Server 2008 R2 SP1. I simply uninstalled that update and it is working great now.
SYNACK Posted September 16, 2013 Posted September 16, 2013 Solved! I found that it was RDP protocol 8.0 that was installed in a Microsoft update found at Description of the Remote Desktop Protocol 8.0 update for Windows 7 SP1 and Windows Server 2008 R2 SP1. I simply uninstalled that update and it is working great now. Still sounds like an Nla/nps fault to me but you've got it going again so all good.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now