I have an application that runs on my local PC. It uses web services on 127.0.0.7:88 (yes 88, that is not a typo) . I have SBS 2003 Premium on my network.
My problem is this: When I have the ISA Firewall client installed, the application errors out. If I disable or remove the firewall client it works as designed.
I need to create a rule in ISA that allows this traffic to pass. Any help would be appreciated.
Bob
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Let's try this for a 3rd time. The application uses web serverices on 127.0.0.1:88. I have tried both suggestions. If I remove the proxy settings in IE the application will run, as long as the firewall client is disabled. As soon as I re-enable the firewall client, the proxy settings reappear and the application does not work.
I have also exempted the application from ISA.
Let's try this for a 3rd time. The application uses web serverices on 127.0.0.1:88. I have tried both suggestions. If I remove the proxy settings in IE the application will run, as long as the firewall client is disabled.
I've been doing this for a while. I know what you said,..what you meant,...what it is doing,...and pretty much,..why it is doing it. There are steps to solving these things,..I don't tell people to change things all over the place until I am faily sure about it and what it will do or what it will cause. If you don't follow the steps I say,..and do it the way I say,...you probably won't get the results you want.
As soon as I re-enable the firewall client, the proxy settings reappear and the application does not work.
Of course it does. This was a troubshooting step,..not a final solution.
The final solution is to leave the FWC setup in the ISA MMC just as I said. The reason it did not work with this alone is because you STILL have the proxy settings in the browser. So:....
1. Keep the FWC exemption as I described.
2. Add "127.0.0.1" or "127.0.0.7" (or whatever the thing really uses) to the Intranet Zone in the settings of IE. That is Intranet,...not Internet. You have to click the Advanced button to get to the place to do that. Don't add the port number,..it is not important.
Now with the FWC exempted (but still enabled) and the IP# added the Intranet zone in IE it should work.
Background on IE.
IE does not handle IP# in the URL properly when it also has proxy settings at teh same time. Adding the IP# to the Intranet zone usually corrects thats.
The application in question appears to leverage the Proxy Settings in IE,...so it suffers from the problem caused by IE.
Another solution is to stop using the IP# and use "localhost:88" instead.
It is possible that the FWC was never getting in the way itself but it was the proxy settings in IE causing the problem,..that were being "pushed" there by the FWC when it was enabled.
Unfortunately it is a banking application.. and my experience with them is that they are troublesome. The only other piece of information that I have, is that it connects to a "mini Web site" (the manufacturers words) when you launch the ap. The "mini web site" is on the local host.
According to the manufacturer, the "mini web site" is not provided by any standard web software, but they utilize their own
I will turn the monitoring on and see obtain a log to see if I can see where the ISA server is blocking traffic. And yes... the box is SBS fully patched with ISA SP3
Of course it is blocking it.
The point is not to get the ISA to allow it. The point is that the traffic should never go to the ISA to begin with,...the ISA should never ever even see it.
Business Accounts
Answer for Membership
by: pwindellPosted on 2009-09-25 at 12:19:54ID: 25426297
There is no rule to create.
You just simply exempt it from using the Firewall Client.
You need to know the executable of the Application that the process "happens" under. (like "mywierdapp.exe").
Then on the ISA go into the MMC
1. <isaName>--Configuration---G
2. Go to the Application Settings Tab. Click "New" at the bottom
3. Application = myweirdapp (do not include the ".exe")
Key = Disable
Value = 1
Back on the workstation,...disable, then re-enable the Firewall Client. The change may not take effect immediately. In a worse case it may take 30 minutes,...but disabling-reenabling should spped it up.