Link to home
Start Free TrialLog in
Avatar of ClintonK
ClintonKFlag for United Kingdom of Great Britain and Northern Ireland

asked on

How to configure VLAN without tagging on Draytek 2960

I have a Draytek 2960 router and two servers; one SBS2011 (192.168.10.5) and one Windows 2016 Essentials (192.168.5.5).
I'm in the process of migrating from SBS2011 to Windows 2016 after which the SBS2011 server will be retired.
During the migration I would like both servers online. The SBS2011 is running DNS and DHCP and the Windows 2016 is just running DNS (DHCP is not installed yet).

I am attempting to configure VLANS on the Draytek, and although all seems sort of OK I'm getting dropouts and poor response when the Windows 2016 server is connected and ports 2,3 and 4 are enabled so I conclude there must be some traffic conflict going on.
My Draytek settings are:
User generated image
User generated image
My intention is that I'm using port 1 for the SBS2011 server and ports 2,3 and 4 for the Windows 2016 (iDRAC, Windows NIC and a single PC on the new domain) so I'm not intending to use VLAN Tagging - I want it all to be physical port based config.
I've achieved a similar configuration on another site but that was using a Draytek 2862N and that worked fine.

Not sure what's going on with this.
Avatar of Soulja
Soulja
Flag of United States of America image

Are you trying to communicate between the two vlans? Is the idrac ip'd on the same subnet as the primary nic on the 2016 server?
Do you get slow response and dropouts when you just connect the primary nic of the 2016 server and not the idrac interface?
What does the traffic rules look like between your VLANS?
Avatar of ClintonK

ASKER

Ideally I want two isolated LANS and I'll move data between the two using FTP or similar. I'm not worried about shifting data but more about have a separate server and PC that I can work on to install apps etc.
The iDRAC card has address 192.168.5.3
I've just enabled only draytek port 3 (the primary nic of the server) and done a quick test and when I connect to SB2011 (using Logmein) and then to Windows 2016 (also using Logmein) I get dropouts/freezes.
If you ping the switch (192.168.5.2) from the 2016 server do you get dropped frames?
Is there any traffic reporting on the 2960 that shows dropped frames?
Is there any errors in the 2960 logs?
No dropped frames when I ping 192.168.5.2
Traffic stats don't report any transmit or receive errors for LAN1 or LAN2
Nothing to report from the 2960 logs
ASKER CERTIFIED SOLUTION
Avatar of Soulja
Soulja
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I've just connected to both servers using RDP and for a while they looked solid but the SBS2011 server froze and then reconnected. I'm beginning to suspect the SBS2011 server is causing trouble and perhaps Logmein is being affected by that (dunno, just guessing).
Thanks for verifying that the Draytek config is good which means I think I will direct my attention to the SBS2011 and work faster to get it replaced by the Windows 2016 server.
So, just to confirm. The Draytek VLAN config I've got should prevent all traffic crossing between 192.168.10.0 and 192.168.5.0 ?
No not necessarily. The config looks like they will route between each other, based on the LAN 1 and Lan 2 ip addressing. I assume those are the routed interfaces you are using as the default gateways for each vlan.
Actually if you look under your general settings. There should be an inter-lan route tab. If it's unchecked the two subnets will not talk to one another.
Just been poking around a bit more and noticed this on the port interface screen. Port 1 is plugged into the switch so will auto negotiate but ports 2,3 and 4 are plugged directly into the devices, i.e. iDRAC, Server and PC.
I've now set the interface speed accordingly and so far (so far....) it hasn't dropped out or frozen. Whether this is a red herring or not remains to be seen so I'll monitor it over the next day or so.
User generated image
So much for that idea. Still getting dropouts.
Again, I'd recommend ping plotter to help you trace your dropouts. I have had instances of bad ports on switches that caused intermittent issues, but until you get some visibility on the problem, your just guessing in the dark.
Now running PingPlotter
Closed due to inactivity