Wednesday, July 11, 2012 8:35 PM
I'm having a networking problem with an application that I've installed in Windows XP mode and am using as a published app in Windows 7 Professional.
The application is the IBM Client Access Emulator for connecting to an IBM AS400 or iSeries server. It won't install on 64-bit systems due to driver issues apparently (I've tried). Therefore I'm forced to install it in XP mode on 64-bit systems.
When starting the program I am able to connect to the server and then around 10-30 seconds later the session is disconnected. I then reconnect the session and everything is fine for the rest of the day. I've found this only happens when the virtual machine comes out of hibernation, but not when the virtual machine is already running or has been shut down previously. I'm not sure what is going on, but it appears something may be resetting the network connection when the virtual machine comes out of hibernation. Since the virtual machine hibernates when shutting down or restarting the Windows 7 computer, this problem happens at the beginning of each day or after a restart.
This problems is occurring in multiple systems with multiple hardware configurations. I have 2 network cards in each system. One connects to an internal network the AS400 and other internal systems are on, and the other connects to a network that has internet access. Both are setup as bridged connections in XP mode. I'm unsure if the problem lies in the virtual machine or in the Client Access program itself.
Needless to say this problem is mostly a nuisance, but I'm about to be forced to install this setup on several more machines with users who may not understand and accept the problem.
Any ideas for a fix?
Friday, July 13, 2012 9:05 AM
Do you mean that the windows 7 computer is a virtual machine? If you do, you can try to install the application on a physical machine to see if the issue also occurs. Also, you can test to access a shared folder. Make it come out of hibernation to see if the session will be disconnected. From the test, we can find out if the problem lies on the Client Access program itself.
Friday, July 20, 2012 12:58 PM
The program is run in Windows XP Mode on Windows 7 64 bit Professional computers. This error does not occur on regular Windows XP machines. I had one system in the past with Client Access installed directly in Windows 7 32 bit and I don't recall it having this problem. The problem only shows up when the Client Access software runs as a virtualized and published app from Windows XP inside Windows 7 64bit (and only when XP mode comes out of hibernation).
I'm not sure how I setup accessing a shared folder as a published app? Might need to find another app I can make published into Windows 7 that requires a network connection.
Friday, July 20, 2012 1:59 PM
Ok, I took your suggestion and figured out how to setup opening a shared network drive in xp's explorer as a published app accessing a share over the same network connection and the same disconnect occurs.
- I created a mapped network drive inside XP mode.
- I copied a shortcut to it into the start menu where it could be auto-published into Windows 7.
- With XP mode hibernated, I opened the shortcut in Windows 7 and the XP explorer window opens and then disappears after 10 seconds or so.
- After waiting for XP mode to hibernate again, I then opened the same shortcut in Windows 7 and initiated a file transfer. A file starts to transfer and after 10 or so seconds, an error pops up stating the specified network name is no longer available. I can then get it to reconnect to the share and work as normal immediately after that.
- With XP mode "powered off", I opened the shortcut in Windows 7 and the share and file transfer act normally with no disconnection.
This leads me to believe it is a problem with XP mode un-hibernating, not Client Access.
This would not be a problem if I could get XP mode to "power off" instead of hibernating when shutting down Windows 7 or after published apps are closed. But despite the settings changed in XP mode, it still chooses to hibernate instead of "shut down" or "turn off".