cancel
Showing results for 
Search instead for 
Did you mean: 

1x DHCP Server 2019 - multiple VLANs - what am I doing wrong?

1x DHCP Server 2019 - multiple VLANs - what am I doing wrong?

frankygth
New Contributor III

I’m having an Extreme Networks x460 Switch and 2 VLANs. On VLAN 11 there’s a Windows Server 2019 located which has 2 scopes (for the different vlans)

VLAN 11 IP Switch: 192.168.11.253/24
IP
 DHCP Server: 192.168.11.1

VLAN 193 IP Switch: 192.168.193.253/24

I’m able to ping the DCHP Server from the Switch


I did a config bootprelay add 192.168.11.1 vr VR-Default
Also enable bootprelay VLAN VLAN11
and enable bootprelay VLAN VLAN193

and last but not least: enable ipforwarding vlan11
and enable ipforwarding vlan193

When I connect a client to VLAN 193 I’m not getting an IP Adress.

The DHCP Server has a Scope for: 192.168.11.100-110 and a Scope for: 192.168.193.100-110

 

2 ACCEPTED SOLUTIONS

frankygth
New Contributor III

I found the error and it’s working now - thank you!! 
The problem was the getting back to the VLAN . The Problem was more firewall related then switch related. Best Regards, Frank PS: Wireshark did the trick

View solution in original post

systemscsn
Valued Contributor

Silly question, but you have built the VLANS in your router right?

View solution in original post

15 REPLIES 15

frankygth
New Contributor III

Yes, I did that, but I did it within GNS3 (for testing purposes). The Problem was, that the offer didn’t get back in the VLAN. I did see the Request in Wireshark also the offer but there was no Ack. So I had to fix the Firewall / VLAN Issue and everything worked then. I was just confused, if the config on the Switch was ok, which ist was 😉

Thank You very much..

systemscsn
Valued Contributor

Never mind, i see you have resolved the issue.

systemscsn
Valued Contributor

Silly question, but you have built the VLANS in your router right?

frankygth
New Contributor III

I found the error and it’s working now - thank you!! 
The problem was the getting back to the VLAN . The Problem was more firewall related then switch related. Best Regards, Frank PS: Wireshark did the trick

GTM-P2G8KFN