It's 'normal' for the application to kick into 'Not Responding' while opening up.Īll applications are installed directly to attached storage and are accessed via a mapped network drive accessible to all users. There is *some* latency in window dragging and such, but typing and general interaction work as expected. Its almost like Approach on the server knows your laptop is on the LAN and is trying to pull data from it, whereas if its on the WiFi I'm guessing the firewall blocks SMB to the server and Approach quickly gives up trying to pull data and just loads. With respect to the remote desktop server, is Approach installed to directly attached storage or does it load the executable(s) from a file share? What about the data files? I did find the article you referenced awhile back and used it to tweak things like paging file size and turn off unnecessary aesthetic tweaks to regain cpu memory(thinking it was the application/server causing the issue).Ĭan you open notepad and type away with minimal latency whilst waiting for Approach to load? When I ping my gateway on wired vs wireless, the wired is slightly faster as one would expect. There doesn't seem to be a traffic issue. Its a set it and its set for both wire and wireless connection. But this is not a setting that can determine your speed on its own. You can change Experience tab within Remote Desktop Connection, you can choose your connection speed to influence network bandwidth performance. In all the time i have spend setting up RDS/Terminal servers i do not recall anyway to configure different rdp profiles based on wireless or wired connection.

As in what rdp loads or does not load base off the speed of the connection. I could see maybe some kinda of configuration on the rdp connection for slower vs faster connection options. Not sure how it would even be able to determine that seeing that its an encapsulated connection. I do not see this application have some kinda complex performance logic to determine wired vs wireless connection. ****But the key question is do you see a major difference in log Time to RDP session between the two networks? wire vs wireless? Maybe and do a tracert/pathping to look at the rout use by the wired vs wireless. Network latency will cause major issue for RPD. If the path is traversing thru different switch you could have packet loss or collision. Ping from same computer on wire and wireless network same buffer size and see what the results are. Pcwireless-switch02 25% usage- no delay in network traffic. Pcwired-switch01 95% usage- to RDP has to what for the switch. That is true about the only thing traversing the connection is the graphical interface, however if the path to the server is different ie going through one switch that is completely over ran with network traffic compare to another with no traffic on it, could cause a major delay.

Local area connection vs ethernet