- Dec 15, 2002
- 71,410
- 28,089
- 113
Let's say you have an application running with an Apache web server attaching to it and communicating thru a static IP address (let's just say 192.168.1.200) using the WiFi card on a Win8 laptop. You are using iPads/Safari to run the web app. Let's also say that an employee comes along and randomly plugs in a cat5 into the laptop, which is setup via dhcp. The web app is up and running until the router blinks, knocks the WiFi off and it doesn't connect for some reason. Doesn't matter why, but the WiFi doesn't connect back up.
At that point, the laptop is connected to the router via the dhcp connection and is assigned a different IP addy (let's say 192.168.1.51). However, now the iPads will not connect to the web app. You can ping the iPads individually, but when the iPads try to hit 192.168.1.200 it shows as no connection.
You go back to the laptop and ping 192.168.1.200, and the laptop itself can hit that ip address (which is on itself).
Without pointing out how stupid it would be to have two network devices on a single box, tell me why the laptop can ping itself on the ip address associated with that network card that is not connected to the router. Is it resolving the broken line via the hot hardwired connection?
At that point, the laptop is connected to the router via the dhcp connection and is assigned a different IP addy (let's say 192.168.1.51). However, now the iPads will not connect to the web app. You can ping the iPads individually, but when the iPads try to hit 192.168.1.200 it shows as no connection.
You go back to the laptop and ping 192.168.1.200, and the laptop itself can hit that ip address (which is on itself).
Without pointing out how stupid it would be to have two network devices on a single box, tell me why the laptop can ping itself on the ip address associated with that network card that is not connected to the router. Is it resolving the broken line via the hot hardwired connection?
