Remote Desktop Connection ( Lan Issue )

[oXiDe]

Hi Guys!

Not sure if this is the appropriate section to put this but I'm running into a few issues.

With a lot of our clients, the servers are set up in such a way, each user connects to them via Remote Desktop Connection. (Windows 7 Ultimate), the issue we are having is sluggish sound and video problems over LAN only.

For e.g
A client may watch a youtube video locally using remote desktop connection which is quite sluggish and sound cuts in and out... However, If I or the client connects into the server from home and watches a youtube video, it works perfectly fine!

Now, upon further testing, we have discovered that is seems to be solemnly a Windows 7 thing.. Windows 8 does not have this issue what so ever... There is no difference between the systems other then the operating system itself..

Any ideas?

 

[SAG]

Hi Guys!

Not sure if this is the appropriate section to put this but I'm running into a few issues.

With a lot of our clients, the servers are set up in such a way, each user connects to them via Remote Desktop Connection.[/b] (Windows 7 Ultimate), the issue we are having is sluggish sound and video problems over LAN only.

For e.g
A client may watch a youtube video locally using remote desktop connection which is quite sluggish and sound cuts in and out... However, If I or the client connects into the server from home and watches a youtube video, it works perfectly fine!

Now, upon further testing, we have discovered that is seems to be solemnly a Windows 7 thing.. Windows 8 does not have this issue what so ever... There is no difference between the systems other then the operating system itself..

Any ideas?

What OS is the Terminal Server running?

 

[YeOldeStonecat]

How are they connecting to it while on the LAN...via public IP or LAN/private IP? If public IP may be some issue with the router not handling loopback well.

 

[oXiDe]

Sag.
Sorry I did not explain that clearly, when i mention that the issue only happens on windows 7, windows 7 is the terminal server. When I mentioned that it does not happen on windows 8.. windows 8 was also the terminal server.

 

[oXiDe]

How are they connecting to it while on the LAN...via public IP or LAN/private IP? If public IP may be some issue with the router not handling loopback well.

As mentioned in my post, the issue only seems to occur on devices connected within the same network (LAN), the issue does not occur on a connection outside the network infact, it works perfectly fine.

 

[SAG]

So...
There is no Terminal Server, these people are connecting to Windows 7 and Windows 8 desktop computers?
What client computers are they using to connect internally, and what client computers are they using externally?

Also, are we talking 10, 100, or gigabit LAN?

Are the .rdp settings the exact same for internal vs external traffic as far as quality settings?

 

[SAG]

As mentioned in my post, the issue only seems to occur on devices connected within the same network (LAN), the issue does not occur on a connection outside the network infact, it works perfectly fine.

What is was getting at, is some routers have trouble sending traffic out and then back in. I see this alot on hacked up linux computers acting as routers.
Internally, are the client computers connecting to the serving computers using private IP addressing, or are you forcing them out of the internal network and back in, relying on port forwarding to send them to where they need to go?

 

[oXiDe]

What is was getting at, is some routers have trouble sending traffic out and then back in. I see this alot on hacked up linux computers acting as routers.
Internally, are the client computers connecting to the serving computers using private IP addressing, or are you forcing them out of the internal network and back in, relying on port forwarding to send them to where they need to go?

Internal connections use a private ip address. External use the public...

As for the network it's all on gigabit lan... and all using windows 7 operating systems.

 

[YeOldeStonecat]

As mentioned in my post, the issue only seems to occur on devices connected within the same network (LAN), the issue does not occur on a connection outside the network infact, it works perfectly fine.

I understood that without any problems.....do you know what loopback is? You CAN BE inside on your network...(LAN)...but connect using a public IP. I've seen profiles setup for terminal server where the RDP shortcut just has the public IP on it, not the private IP like 192.168.1.25.

 

[oXiDe]

I understood that without any problems.....do you know what loopback is? You CAN BE inside on your network...(LAN)...but connect using a public IP. I've seen profiles setup for terminal server where the RDP shortcut just has the public IP on it, not the private IP like 192.168.1.25.

Local Network uses the private IP.