danw
Lifetime Supporting Member
A production dept desktop and validation dept's laptop both communicate (using the HMI app) to the HMI through a couple local CAT cables and unmanaged switch on a private network using static IPs with no gateway settings, proving the HMI and associated hardware outside the new laptop works OK.
The new Win 7 Pro laptop will not ping/communicate to the HMI via the laptop's wired Ethernet port with the laptop on a static IP.
To check the Ethernet port, I
- disabled the WiFi wireless adapter (so the only way to communicate is through the wired port)
- set the wired adapter to DHCP
- connected a CAT cable to the corporate network and found that Internet Explorer connected to the internet just fine using the wired port.
But when the port is re-configured with a 192.168.X.XXX static IP address (subnet mask 255.255.255.0), and the laptop substituted for the production desktop that communciates with the HMI, the laptop will not communicate with the HMI using the HMI app program. An attempt to ping the HMI times out.
I checked the Windows Firewall and the HMI app program is enabled for both private and public networks.
In my experience, failure to ping a point-to-point connection (through a working unmanaged switch) has either been a hardware issue
- CAT cable not plugged in
- switch power disabled/disconnected
- bad connector on a CAT cable
or an IP address issue
- a wrong subnet IP address
- DHCP is enabled rather than a static IP
I'm guessing the Windows firewall could stop a ping or a app program, but what would I look for?
Any other ideas?
Dan
The new Win 7 Pro laptop will not ping/communicate to the HMI via the laptop's wired Ethernet port with the laptop on a static IP.
To check the Ethernet port, I
- disabled the WiFi wireless adapter (so the only way to communicate is through the wired port)
- set the wired adapter to DHCP
- connected a CAT cable to the corporate network and found that Internet Explorer connected to the internet just fine using the wired port.
But when the port is re-configured with a 192.168.X.XXX static IP address (subnet mask 255.255.255.0), and the laptop substituted for the production desktop that communciates with the HMI, the laptop will not communicate with the HMI using the HMI app program. An attempt to ping the HMI times out.
I checked the Windows Firewall and the HMI app program is enabled for both private and public networks.
In my experience, failure to ping a point-to-point connection (through a working unmanaged switch) has either been a hardware issue
- CAT cable not plugged in
- switch power disabled/disconnected
- bad connector on a CAT cable
or an IP address issue
- a wrong subnet IP address
- DHCP is enabled rather than a static IP
I'm guessing the Windows firewall could stop a ping or a app program, but what would I look for?
Any other ideas?
Dan