HP2626 Intervlan Routing

[LTowndrow]

Hi,

Looking for some help.

I have a HP 2626 switch, whichI have created two vlans on. In vlan2 I have a DHCP server with two scopes. One scope for Vlan 2 (192.168.1.30 - 192.168.1.40) and one scope for vlan 3 (172.25.3.1 - 172.25.3.10) Clients in both vlans need to talk to each other.

 If I put a client in vlan 2 the client receives a DHCP address.

However if I put a client in vlan 3 it can't receive a DHCP address from the server in vlan 2.

Please can you help with what I need to do to resolve this issue.

hostname "Edge_1"
sntp server 192.168.1.18
ip routing
timesync sntp
sntp unicast
logging 192.168.1.18
snmp-server community "public" Unrestricted
vlan 1
   name "DEFAULT_VLAN"
   untagged 9-26
   no ip address
   no untagged 1-8
   exit
vlan 2
   name "VLAN2"
   untagged 1-4
   ip address 192.168.1.2 255.255.255.0
   ip helper-address 192.168.1.18
   exit
vlan 3
   name "VLAN3"
   untagged 5-8
   ip address 172.25.3.1 255.255.255.0
   ip helper-address 192.168.1.18
   tagged 3
   exit

 Destination        Gateway         VLAN Type      Sub-Type   Metric     Dist.
  ------------------ --------------- ---- --------- ---------- ---------- -----
  127.0.0.0/8        reject               static               0          250
  127.0.0.1/32       lo0                  connected            0          0
  172.25.3.0/24      VLAN3           3    connected            0          0
  192.168.1.0/24     VLAN2           2    connected            0          0

Many Thanks

[ISoliman]

How the server is connected ? On Which port of the switch? Does it recognize VLAN tagging ?

The easier way is to untag the port connected to the DHCP server in VLAN 2 only, and configure the gateway of the server to point to the IP address of the switch in it's VLAN or configure a static route from the DHCP server pointing to the other subnet so that it will know where to send the DHCP traffic back to that subnet.

[LTowndrow]

After spending a little time trying out different configurations, it turned out to be the Firewall on the server.