Switches, Hubs, and Modems
cancel
Showing results for 
Search instead for 
Did you mean: 

HP2524 switch,Devices on same switch,same VLAN,with IPs on same network not able to Ping each other

gurumagic9
Occasional Visitor

HP2524 switch,Devices on same switch,same VLAN,with IPs on same network not able to Ping each other

I have an HP 2524 switch.  I have 7 devices, all of which have IP's that are on the same network.  They are all plugged into this 2524 switch.  My VLAN config is as such

 

; J4813A Configuration Editor; Created on release #F.05.55

hostname "DMZ_HP-2524"
cdp run
ip default-gateway 74.xxx.xxx.192
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
untagged 25-26
no ip address
tagged 12
no untagged 1-11,13-24
exit
vlan 2
name "WEB_SERVERS"
untagged 1-11,13-22
ip address 74.xxx.xxx.197 255.255.255.224
tagged 12
exit
vlan 61
name "WLAN-PUBLIC"
untagged 24
no ip address
tagged 12
exit
vlan 101
name "Internl_link"
untagged 23
tagged 12
exit
primary-vlan 2
no aaa port-access authenticator active

 

My devices are using IP's that are in the network range:

74.xxx.xxx.193 - 74.xxx.xxx.222

255.255.255.224

 

so they should be able to see each other.  When I try to ping 74.xxx.xxx.193 from 74.xxx.xxx.196 or any other computers on the network, it doesn't work.  If I try to ping directly from a telnet session on this same switch, it cannot ping the devices plugged into either.  All of these devices are plugged into ports 1-11.  If I ping google from one of these devices, it works just fine.  None of these machines have firewall enabled during this testing.  I have another switch that uses just a default VLAN and devices connected to it, can ping the devices on the former switch.  Any ideas?  I've been googling to my hearts content and cannot find any resolution.  I can provide more information if needed.  Any help is greatly appreciated.

 

T

1 REPLY
gurumagic9
Occasional Visitor

Re: HP2524 switch,Devices on same switch,same VLAN,with IPs on same network not able to Ping each ot

Solved.  This was actually failing because of a NAT rule.