Permission and compatibility.

You can right click on the program, and select properties, then select Compatibility, select Change settings for all users. This way, you are setting it for all users. Set the XP SP3 if that’s what works on your PC XP with Office 2007. And checked, run as administrator only if necessary.

Next part is Windows 7 have a great revamp on firewall. There are two parts to it. First part is internal firewall called work firewall, and another call Public firewall. You just need to tinker the work firewall. Go to Windows(Start), at search type Firewall, select result to run Firewall, go to Properties, and you will see Domain, Private, Public, I would try to turn them all off momentarily, to test out the software issue you are dealing with. Once proven, then you know your buddy-firewall has been the culprit

Sorry for the late post, my real IT job is quite demanding at times.

Based on my last project, which expand to using Windows 7 and Windows XP, I would convert the programs to run compatibility with winXP sp3 in the windows 7 and turn off UAC. I hope this help.
:/

In the trace we see Windows sending a request to the iSeries for srvsvc. The iSeries responds with Function not supported.
Windows keeps sending the srvsvc request to the iSeries. We are not sure if it is expecting to get a different response from the iSeries, or what.
Then Windows decides to go out to http port 80 and see if something on port 80 will respond, which it does not because NetServer does not use this port.
Windows makes a bunch of requests trying to contact port 80, which is all eating up time and delaying what you are trying to do.
In the past when we have seen Windows try to access port 80, it has been when the Web Client service was running. If it was not running on the PC you traced, we have no way of telling why Windows was trying to access port 80. This would be a question for Windows Support.

Work around is to save the file to the pc and then copy to ifs folder.