RDP issues : inter-VLAN routing ?

RDP issues : inter-VLAN routing ?

RDP issues : inter-VLAN routing ?
RDP issues : inter-VLAN routing ?
a week ago - last edited a week ago
Model: SG6654X  
Hardware Version:
Firmware Version:

Hello,

 

I've been troubleshooting a strange behavior in my network for a few weeks.

 

Setup :

- OC400 as a controller

- ER8411 as main router

- SG6654X (L3) as main switch (connected to ER8411)

- SG3452XP (L2) all connected to the SG6654X

- 1 FS switch connected to the SG6654X

 

Issue :

On the 1st floor, connected to the FS switch, I have RDP issues connecting 2 devices even on the same floor. I can start the RDP session, but after something like 20 or 30 sec, it's lagging hard (not cutting the stream, but really unusable).

When I connect to it by Wi-Fi (different subnet) or by a NAT rule directly, it works perfectly fine. With VPN on (same subnet), same trouble as locally.

 

Ideas :

I've tried many many things but nothing worked.

I'm thinking that it might be caused by inter-VLAN routing.

I have no specific config on my FS switch, but it's uplink to my Omada has a specific port configuration that tag my network with a VLAN (172). I'm thinking that's why the FS can't switch the two devices and has to pass by the router, somehow making it hard lagging.

I've done no specific config to my L3 main switch, so I don't know if he can do any inter-VLAN routing or if it's all on the ER8411 to do so.

 

Observation :

Today I've observed in "Insights > Routing Table" that L2 switches all have my subnets configured, example :

NAME        

DESTINATION IP/SUBNETS NEXT HOP DISTANCE
000_SWITCH-12 0.0.0.0 / 0 10.0.0.1 254
000_SWITCH-12 10.0.0.0 / 16 10.0.10.112 0
000_SWITCH-12 AAA.BBB.0.0 / 16 AAA.BBB.0.112 0

 

But my L3 switch has none of the subnets routed, only this :

NAME        

DESTINATION IP/SUBNETS NEXT HOP DISTANCE
000_SWITCH-01 10.0.0.1 10.0.0.1 254
000_SWITCH-01 10.0.10.101 10.0.10.101 0
000_SWITCH-01 AAA.BBB.0.101 AAA.BBB.0.101 0

 

Theory of the day :

Is this normal ? I'm wondering if :

- 1st floor with the FS switch is directly connected to the L3 switch, so only the routing table of 000_SWITCH-01.

- Other floors have Omada switches with routing tables like the 000_SWITCH-12 has.

That seems odd to me, but I'm no expert so I'd like your opinion on this. Could it be the problem ?

 

Conclusion :

I know that the easy answer is probably just to replace these FS switches with Omada switches, but I'd like to understand the technical source of the problem and be able to explain it.

 

If anyone can help me see clear in this, I'd really appreciate as this has been a real issue for us.

 

Thanks ahead.

 

PS : I don't think it's the cause, but I'll mention it, historically we have this "AAA.BBB.0.0" subnet that is outside the private networks standards (neither 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16).
PS² : I know it's really ugly.

  0      
  0      
#1
Options
3 Reply
Re:RDP issues : inter-VLAN routing ?
a week ago - last edited a week ago

Hi @Dipsy 

Thanks for posting in our business forum.

It would be better with a diagram to understand your full topology.

 

RDP lags, I don't think that means the VLAN is causing the issues.

Routing should not cause problems as well.

My first impression is that the problem is not with the network environment.

 

Edit:
Not sure if you were affected:

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
  2  
  2  
#2
Options
Re:RDP issues : inter-VLAN routing ?
a week ago - last edited a week ago

Hello @Clive_A,

 

Thank you for your answer.

 

Why I thought it could be network based :

- The user complaning the most had a brand new computer, and we replaced it with another one since then too.

- It works when we connect from NAT or Wi-Fi.

- It worked when we physically moved the computer to another floor.

- We have 3 floors and total of ~80 users ; it's the only floor we are observing issues.

- Problems appeared around the same time we deployed our whole new infrastructure (all Omada).

 

Definitely a tricky and unclear issue, as we don't observe it with most of the computers on the floor.

 

I'm definitely gonna look into this Microsoft post !

 

Thanks,

Jérémy

 

PS : on a sidenote, if anyone could confirm that the difference in the routing table of the L3 switch vs the routing tables of the L2 switches is normal, I'd be at peace.

  0  
  0  
#3
Options
Re:RDP issues : inter-VLAN routing ?
a week ago

  @Dipsy 

 

I have switch based inter - vlan routing here (lthough all TP link L2+ TP-Link switces here, not any of the fancy new L3 ones).  I dont have any issues with RDP to a couple of our servers form any vlan that is permitted to get to the management vlan through switch ACLs.  Even via VPN works normally from both site-to-site IPsec that just bridges into the vlans, or L2TP/IPsec that terminated on a seperate IP pool, which is then bridged into the vlan - all RDP works fine here! ?

  0  
  0  
#4
Options