Link to home
Start Free TrialLog in
Avatar of iamuser
iamuser

asked on

2 device phsycially on same switch cannot reach each other

I have a non PC device that came prconfigured with a default IP ( no DHCP option). The device is also POE powered with no other power options available.
in order to change the IP i have to get to the device's web management page. I have plugged the device into a port of a POE CISCO switch and then a laptop into the next port on the same switch, The Device had an IP of 192.16.0.1 and I gave the laptop 192.168.0.2. The ports themselves are on the same VLAN.

The switch shows both devices on the switch. However, from the laptop I am unable to reach the web management page of the device. Doing an Arp -a on the laptop shows an entry for 192.168.0.1. I also cannot ping the device from the laptop.

The switch has a trunk that goes to a router and the network assigned to the VLAN is different from the network that the 2 devices are on. But from what I understand. that should not matter as both devices are local to the switch. The shouldn't be a need for the switch to forward the traffic to the router. It should know that one device is on port 5 and the other port 6. Or am I wrong here?

On managed switches this was never an issue,
Avatar of Darrell Porter
Darrell Porter
Flag of United States of America image

Make sure your subnet masks match. Likely they should both be 255.255.255.0.
Do either have a gateway set?
I am presuming the address you provided above for the non-PC device is a typographical error on your part and should be 192.168.0.1.
Does the Windows PC have its firewall enabled?  If so, disable it using the Control Panel Windows Firewall applet and do not simply stop the Windows Firewall Service.
On the Windows PC, ensure any wireless interface is disabled for the duration of this exercise.
I dont think that you can give your device an ip of 192.168.0.1 that would normally be reserved for the default gateway and should not have been used for your device.
You get an ARP response, so local broadcasts for the 192.168.0.0/24 network work, and there is a device answering.
Either the device is a different one than the intended, which you might be able to check by comparing the MAC addresses of ARP and device (if known),
or the device runs a firewall - very unlikely
or the device does not work correctly, and refuses to offer the required services.

I assume you checked the Cisco switch for access rules? There shouldn't be any applied intra-VLAN (only if crossing VLANs), but maybe there is a misconfiguration. In which case another laptop or similar connected instead of the non-PC device with IP 192.168.0.1.
Check the switch port configurations they are connected to and make sure they are on the same vlan. If not, that is the reason. Also as someone else stated, make sure the subnet masks are the same.
Avatar of iamuser
iamuser

ASKER

  • Both devices were on the same VLAN but network for that VLAN is 192.168.5.x /24 where as the devices themselves had IP of 192.168.0.1 and 192.168.0.2.
  • Both devices were plugged physically to the same switch on port 1 and port 2.
  • The subnet mask is /24
  • There is no gateway on the PC as the gateway goes to 192.16.0.3 (yea I know, that is the gateway IP) since the laptop is using 192.168.0.2. The device also has no gateway either
  • Being that both items were plugged into the switch and next to each other I assumed that there would be no need for routing. Both of them should be able to talk to each other
  • no firewall on the laptop, it was off and even if it wasn't there were 2 active rules (created) to allow all traffic in and out.
  • I also added a static entry into the arp table on the laptop that points 192.168.0.1 to the mac address of the device. That did nothing.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.