Outpost Firewall General Discussions, Support, and Troubleshooting ::
Use this forum to ask other users how to do things in Outpost Firewall. Outpost Firewall Pro 1.0.1220.2238 caused BSOD in windows XP? Ceromus. 08-25-2002 01:07 PM
http://outpostfirewall.com/forum/forumdisplay.php?f=55&order=desc&page=406HOME |
I can only assume this is a result of the firewall being on my computer since I have never experienced a blue screen on this machine before. I am using ICS as well.
Here is some information from my system log...
-----------------------------------------------------------------------------
Event Type: Error
Event Source: ipnathlp
Event Category: None
Event ID: 31008
Date: 8/21/2002
Time: 11:23:12 PM
User: N/A
Computer: SYSTEM-XPCKYJ8J
Description:
The DNS proxy agent was unable to read the local list of name-resolution servers from the registry. The data is the error code.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 6f 00 00 00 o...
-----------------------------------------------------------------------------
DRIVER_IRQL_NOT_LESS_OR_EQUAL
STOP: 0x000000d1 (0x75f72faf, 0x00000002, 0x00000000, 0xf3b8f636)
IPNat.sys
thanks for the help in advance.
Ceromus, It would do absolutely no good to work on that version trying to fix BSODs. The programmers are working on THE program to fix the ICS issue and a lot of other issues, including BSODs. I was not aware of any other Blue Screens until Id324 posted.
BSOD on Windows XP - Outpost Users Support Forum::
BSOD on Windows XP Retired Threads Outpost gives me BSOD in Windows XP? Need Outpost Firewall Pro 1.0.1220.2238 caused BSOD in windows XP? Ceromus
http://www.outpostfirewall.com/forum/showthread.php?t=4502HOME |
Outpost Firewall Pro 1.0.1220.2238 caused BSOD in windows XP? - Outpost ::
Outpost Firewall Pro 1.0.1220.2238 caused BSOD in windows XP? Outpost Firewall General Discussions, Support, and Troubleshooting
http://www.outpostfirewall.com/forum/showthread.php?t=4782HOME |
It doesn't make any difference. The programmers are practically rebuilding the program. It will have a new logging system, and will support XP ICS, pass all known leak tests, and several other issues are being dealt with.
I'm sorry if you cannot accept the situation the way it is. Everyone here tries to help people having problems with Outpost, and the programmers are working hard as they can to get version 2 released to beta testing.
There is nothing else we can do.
Never heard of it before. :confused:
Is this a one time event? Is Outpost working ok? Is there some way to repeat the bsod?
As much info as possible, will help get a better idea.
Could be the MS firewall too? Is it disabled?
Ceromus, of course Agnitum supports its product. Danil has a little problem with translating Russian thoughts into English every once in a while and it doesn't come out sounding like what he meant it to say. Look around the board and you will see several thousand posts where people are getting support.
Outpost Firewall General Discussions, Support, and Troubleshooting ::
forum to ask other users how to do things in Outpost Firewall. Outpost Firewall Pro 1.0.1220.2238 caused BSOD in windows XP? Cygwin/XFree86. Install Problem
http://www.outpostfirewall.com/forum/archive/index.php/f-55.htmlHOME |
BSOD: Outpost conflicts with Winternals TCPView Pro - Outpost Users ::
BSOD: Outpost conflicts with Winternals TCPView Pro Retired Threads Outpost Firewall Pro 1.0.1220.2238 caused BSOD in windows XP? Ceromus
http://www.outpostfirewall.com/forum/showthread.php?t=2988HOME |
Next. I'm not sure this was caused by Outpost as it's hard to tell from the message. What Danil was talking about with ICS was that ICS on XP used to work, then in the process of fixing other problems, ICS broke. Trying to use it in XP now could cause some problem, I don't know. ICS in XP is fixed in version 2, which I hope to see soon.
It has been a long time since we knew of a problem with Outpost that caused bsods. If it happens now, its almost always because of leftovers from another firewall like ZA or Sygate, usually registry entries. Did you have another firewall installed previously? If so, when you uninstalled it, did you clean the registry too?
Last, have you had any more bsods since the first one?
Ceromus, we won't discuss here BSODs of very old version. Please await the released of Outpost 2.0, where the problem of ICS+WinXP is fixed.
Well its only happened once so far but I was hoping to track it down before it happened a 2nd time...its not often one gets a blue screen once and never again.
the xp firewall is not on, I dont have any sniffers running, dns cache settings? I dont know anything about that so I can only imagine it wasnt changed.
Danill, did you just tell me you refuse to offer support for a product that your company charges money for? That sure is what it sounded like to me, alot of review sites gave this product a good review are they aware you offer no support for customers experiencing BSOD's?
Im using the version you recommended for customers using Windows XP + ICS, the fact that its very old and you STILL can't make windows xp + ICS doesn't mean you should make customers wait till you finally get it working for support. After all poor programming is not the customers fault. Xp firewall 1 way::
Archive Outpost Firewall Pro 1.0.1220.2238 caused BSOD in windows XP? be able Archive Outpost Firewall Pro 1.0.1220.2238 caused BSOD in windows XP?
http://www.easypcsecurity.info/Internet-Security/xp-firewall-1-way.htmlHOME |
op4 = bsod windows stop error - Outpost Users Support Forum::
op4 = bsod windows stop error Outpost Firewall General Discussions, Support, and Outpost Firewall Pro 1.0.1220.2238 caused BSOD in windows XP? Ceromus
http://outpostfirewall.com/forum/showthread.php?t=18644HOME |
Heaven forbid you should stress yourself to do 2 things at once.
"Others don't have BSODs with ver. 1.0.1220."
So....what do you call Id324's post above yours?
I have also had this problem with this version. Been using it because of the WinXP ICS problem. I did have Zone Alarm, but have followed all the instructions on this board to remove it, using regedit several times to confirm the removal. I have only experienced this on the host machine, not the client. I have had to quit using Outpost because the blue screens where becoming very frequent. I had never had a blue screen up to using it and havn't since I have disabled it. Using WinXP Pro with one client with ICS. Awaiting Outpost 2 but would appreciate any help.
Danill, did you just tell me you refuse to offer support for a product that your company charges money for?I didn't tell that.
That sure is what it sounded like to me, alot of review sites gave this product a good review are they aware you offer no support for customers experiencing BSOD's?Guess, you incorrecly understood me.
We won't investigate the BSOD of old version.
Currently the developers work to fix Win2000sp2/XP+ICS problem with version 1.0.1817.
Do you want them to stop their work and to start investigating your BSOD logs?
They won't do that, as it is a step back.
Im using the version you recommended for customers using Windows XP + ICS, the fact that its very old and you STILL can't make windows xp + ICS doesn't mean you should make customers wait till you finally get it working for support. After all poor programming is not the customers fault.I completely understand your problem - you use old version because of ICS+XP. You had BSOD with this version. Others don't have BSODs with ver. 1.0.1220. Do you want us to stop programming new fixed version and pay all attention to ver. 1.0.1220 and your BSOD reports?
Ceromus, I agree, bsods usually are repeatable, although sporadically.
It has been a while since Outpost was causing any bsods in XP, but that is not to say, there could not still be a problem. If there is a problem, we want to know.
Is the XP firewall disabled? Do you have any other internet aware applications running such as a sniffer?
Did you make any changes to the dns cache settings?
 Red Hat's Rough Recovery From CFO Exit
 Windows Live Finds a New, Pre-installed Home
|
Outpost Firewall Pro 1.0.1220.2238 caused BSOD in windows XP?