dhcp and windows 2019 no reply and relay

HeHeEh

New Member
Joined
May 7, 2023
Messages
1
Reaction score
0
Credits
10
Hey, can you tell me where the mistake is?

LAN Segment NET1 and NET2

Debian 10 (DHCP SERVER)
With 1 Interface ens33, IP 10.199.99.254/28 and Virtual IP with IP 10.99.99.252/24, all connected to LAN segment NET1.

With the DHCP server settings:

subnet 10.199.99.240 netmask 255.255.255.240 {
range 10.199.99.240 10.199.99.254:
option router 10.199.99.254;
}
subnet 10.99.99.0 netmask 255.255.255.0 {
}

and a fixed IP for client 10.99.99.1.

Windows 2019 (As DHCP Relay)
With 2 Ethernet
Eth0 IP 10.199.99.253/28 connected to LAN segment NET1, Eth1 IP 10.99.99.254 connected to LAN segment NET2.

Ubuntu (As Client)
Connected to LAN segment NET2.

The question is why can't Ubuntu get a DHCP IP address?

Why did monitoring using Wireshark show that Ubuntu requested DHCP and Windows 2019 forwarded it to Debian but Debian did not respond? And why, even if Debian does respond, Windows 2019 doesn't forward it to the client?

That's my question.
 

Members online


Latest posts

Top