Networking with Windows XPMode
I have a legacy application that is used to communicate with a robot. The application is 32bit and will not run on Windows 7. I have installed Windows XPmode on my Win7 64bit computer and installed the legacy application. My problem is the application is not communicating with the robot. There are 2 NIC's on the host machine, I have tried them both in every combination I could think ok. The only network that this machine is connecting to is directly to the robot. I have tried setting the IP directly on the host, choosing NAT, and leaving the VM set to grab DHCP...I have set the Host to grab DHCP and tried setting the IP on the VM...setting the IP on both the VM and the Host. What would be the proper way to set the IP?
Erik
Erik
ASKER
compatibility mode does not work, application will not install on win7 64bit. The problem is how/where to set the IP address....host vs vm
The W7 host has to have an IP address if you are communicating via TCP/IP. The VM will need an address as well unless you can bridge the VM to the host adapter in some way. The Robot also needs an IP address. All three should be in the same subnet like 10.0.0.1, 10.0.0.2 and 10.0.0.3 and all should share the same subnet mask of 255.255.255.0. The gateway for the PC host and the VM should be the Robot IP and the Robot gateway address should be the VM.
This would all be simpler if you had all of this connected to a small home type router to give out DHCP...
It has been a while for me and Virtual PC on Windows, I typically do not install it and opt for VirtualBox by Oracle. But you cannot get the free XP license in that way.
This would all be simpler if you had all of this connected to a small home type router to give out DHCP...
It has been a while for me and Virtual PC on Windows, I typically do not install it and opt for VirtualBox by Oracle. But you cannot get the free XP license in that way.
ASKER
I understand TCP/IP. The host is not doing ANY communication to the robot. The Host is simply the Host. So...if I assign the NIC to the VM...do I leave the IP address blank (dhcp) on the host, then set it correctly on the VM? A router would be great if my PLC would grab a DHCP address. It wont. I have tried setting up the NIC to NAT, and setting the address only on the host...doesn't work. I have tried bridging the NIC and setting the IP locally on the VM and the host...doesn't work...
Run the application setup using compatibility mode.
Right click and select trouble shoot, or properties, and there is a compatibility tab set to windows XP and see if that works.
You may have tried it.
The difficulty deals with whether the issue is within the VM, or on the network.
Using wireshark or ms network monitor, you can look at the network traffic within the VM, and on the windows 7 to see whether the traffic leaves and whether the robot responds.
If you still have the old system, use it to build the expected network traffic as a reference.
Right click and select trouble shoot, or properties, and there is a compatibility tab set to windows XP and see if that works.
You may have tried it.
The difficulty deals with whether the issue is within the VM, or on the network.
Using wireshark or ms network monitor, you can look at the network traffic within the VM, and on the windows 7 to see whether the traffic leaves and whether the robot responds.
If you still have the old system, use it to build the expected network traffic as a reference.
Regardless of your software being able to load in Win7 or not, TCP is TCP is TCP. Having said that, can you at least ping the robot from the Win7 box? If no, then you need to overcome that issue first before you can look at the VM. If one IP address cannot ping another IP address on the same network, there is a problem.
I read back through your first post and you said the robot is connected directly to the PC. Are you using a straight through cable or a crossover cable? You must have a crossover cable for direct connections unless one of the NICs auto detects, which may not be 100% fool proof. You can also use a switch between the two devices to get the proper signaling.
I read back through your first post and you said the robot is connected directly to the PC. Are you using a straight through cable or a crossover cable? You must have a crossover cable for direct connections unless one of the NICs auto detects, which may not be 100% fool proof. You can also use a switch between the two devices to get the proper signaling.
Are there two VLANed segments?
Using network monitoring tools, you could troubleshoot the issue to first make sure that there is network traffic originating from your host/guest. Then validating the network .......
Using network monitoring tools, you could troubleshoot the issue to first make sure that there is network traffic originating from your host/guest. Then validating the network .......
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Application was not installed correctly. Once I spoke with the MFR I received the correct steps for install.
A suggestion if I might on whether you ran the application in windows xp compatibility mode within windows 7 rather than within a VM?
Was the robot locked in using MAC address from which it will accept communications?