SP2 firewall problem

[Menno Hershberger]

A few days ago I was trying to use WS_FTP to do some work on a website,
and couldn't connect. I figured it was a problem with the server so I
waited a couple of hours and still couldn't connect. Finally, I tried it
again with Windows 98 and got right in. So I went back into XP, no luck.
Experimenting with different things, I finally turned of the XP firewall
and got right in. I checked the firewall settings and WS_FTP was on the
allowed list. I even added a couple of entries for FTP. One was TCP port 21
and the other was UDP port 21. It still won't allow FTP.
I run Sygate Personal Firewall too, so I just keep the XP firewall turned
off now and have no problems. But something went awry with the XP firewall.
Any ideas as to what it might be?

--
-- Puritanism: the haunting fear that someone somewhere may be happy. --

[Charlie Crabb]

I have a similar problem. My IP is trashed by something.
I was running NIS 2004 and SP2 for over a month. Then
I noticed the IP was trashed on startup. I turned *off*
the XP firewall, and things started up successfully after that.
*Howeeevvver*...I just installed NIS 2005. MS Firewall is off.
But I still have the same startup problem. I went into MS
security, toggled the fire wall (end state: off), and am able
to get back on again. So with MS firewall off, NIS 2005 seems
to have some race condition with something. It would seem
that the ISP could patch this. Hey, guess it's a pretty effective
firewall :-)

"Menno Hershberger" wrote:

> A few days ago I was trying to use WS_FTP to do some work on a website,
> and couldn't connect. I figured it was a problem with the server so I
> waited a couple of hours and still couldn't connect. Finally, I tried it
> again with Windows 98 and got right in. So I went back into XP, no luck.
> Experimenting with different things, I finally turned of the XP firewall
> and got right in. I checked the firewall settings and WS_FTP was on the
> allowed list. I even added a couple of entries for FTP. One was TCP port 21
> and the other was UDP port 21. It still won't allow FTP.
> I run Sygate Personal Firewall too, so I just keep the XP firewall turned
> off now and have no problems. But something went awry with the XP firewall.
> Any ideas as to what it might be?
>
> --
> -- Puritanism: the haunting fear that someone somewhere may be happy. --
>

[Torgeir Bakken \(MVP\)]

Menno Hershberger wrote:

> A few days ago I was trying to use WS_FTP to do some work on a website,
> and couldn't connect. I figured it was a problem with the server so I
> waited a couple of hours and still couldn't connect. Finally, I tried it
> again with Windows 98 and got right in. So I went back into XP, no luck.
> Experimenting with different things, I finally turned of the XP firewall
> and got right in. I checked the firewall settings and WS_FTP was on the
> allowed list. I even added a couple of entries for FTP. One was TCP port 21
> and the other was UDP port 21. It still won't allow FTP.
> I run Sygate Personal Firewall too, so I just keep the XP firewall turned
> off now and have no problems. But something went awry with the XP firewall.
> Any ideas as to what it might be?
>
Hi

Troubleshooting Windows Firewall settings in Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=875357

A much more detailed version:
Troubleshooting Windows Firewall in Microsoft Windows XP Service Pack 2
http://www.microsoft.com/downloads/details.aspx?FamilyID=a7628646-131d-4617-bf68-f0532d8db131&DisplayLang=en

The Cable Guy - February 2004
Manually Configuring Windows Firewall in Windows XP Service Pack 2
http://www.microsoft.com/technet/community/columns/cableguy/cg0204.mspx



--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scriptcenter/default.mspx

[Alex Nichol]

Menno Hershberger wrote:

>A few days ago I was trying to use WS_FTP to do some work on a website,
>and couldn't connect. I figured it was a problem with the server so I
>waited a couple of hours and still couldn't connect. Finally, I tried it
>again with Windows 98 and got right in. So I went back into XP, no luck.
>Experimenting with different things, I finally turned of the XP firewall
>and got right in. I checked the firewall settings and WS_FTP was on the
>allowed list. I even added a couple of entries for FTP. One was TCP port 21
>and the other was UDP port 21. It still won't allow FTP.
> I run Sygate Personal Firewall too, so I just keep the XP firewall turned
>off now and have no problems. But something went awry with the XP firewall.
>Any ideas as to what it might be?

The XP one needs to be set to Passive mode FTP. But if you have another
good one, like Sygate, you do not need it


--
Alex Nichol MS MVP (Windows Technologies)
Bournemouth, U.K. (remove the D8 bit)

[GateKeeper]

I have read numerous posts advising users not to run the Windows XP firewall
and another one at the same time. I do have both a hardware firewall (my
router) and the WinXP firewall on my laptop, but this has never caused a
problem for me. But then again, I don't use FTP software on the laptop.


"Menno Hershberger" > wrote in message
...
> A few days ago I was trying to use WS_FTP to do some work on a website,
> and couldn't connect. I figured it was a problem with the server so I
> waited a couple of hours and still couldn't connect. Finally, I tried it
> again with Windows 98 and got right in. So I went back into XP, no luck.
> Experimenting with different things, I finally turned of the XP firewall
> and got right in. I checked the firewall settings and WS_FTP was on the
> allowed list. I even added a couple of entries for FTP. One was TCP port
> 21
> and the other was UDP port 21. It still won't allow FTP.
> I run Sygate Personal Firewall too, so I just keep the XP firewall turned
> off now and have no problems. But something went awry with the XP
> firewall.
> Any ideas as to what it might be?
>
> --
> -- Puritanism: the haunting fear that someone somewhere may be happy. --

[Roger Courtney]

The firewall is designed for people DIRECTLY connected to the Internet. If
you have a firewall between you and the Internet the recommendation is to
NOT use WinXP Firewall.

Happy Holidays, Roger

"GateKeeper" > wrote in message
...
>I have read numerous posts advising users not to run the Windows XP
>firewall and another one at the same time. I do have both a hardware
>firewall (my router) and the WinXP firewall on my laptop, but this has
>never caused a problem for me. But then again, I don't use FTP software on
>the laptop.
>
>
> "Menno Hershberger" > wrote in message
> ...
>> A few days ago I was trying to use WS_FTP to do some work on a website,
>> and couldn't connect. I figured it was a problem with the server so I
>> waited a couple of hours and still couldn't connect. Finally, I tried it
>> again with Windows 98 and got right in. So I went back into XP, no luck.
>> Experimenting with different things, I finally turned of the XP firewall
>> and got right in. I checked the firewall settings and WS_FTP was on the
>> allowed list. I even added a couple of entries for FTP. One was TCP port
>> 21
>> and the other was UDP port 21. It still won't allow FTP.
>> I run Sygate Personal Firewall too, so I just keep the XP firewall
>> turned
>> off now and have no problems. But something went awry with the XP
>> firewall.
>> Any ideas as to what it might be?
>>
>> --
>> -- Puritanism: the haunting fear that someone somewhere may be happy. --
>
>

[Malke]

GateKeeper wrote:

> I have read numerous posts advising users not to run the Windows XP
> firewall
> and another one at the same time. I do have both a hardware firewall
> (my router) and the WinXP firewall on my laptop, but this has never
> caused a
> problem for me. But then again, I don't use FTP software on the
> laptop.

This advice has nothing to do with FTP software or running a router and
a firewall. It refers to running two software firewall programs, like
XP's built-in one and Sygate, for instance. Having a router and one
software firewall is A Good Thing.

Malke
--
MS MVP - Windows Shell/User
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"

[Ken Blake]

In ,
GateKeeper > typed:

>I have read numerous posts advising users not to run the Windows
>XP
> firewall and another one at the same time. I do have both a
> hardware
> firewall (my router) and the WinXP firewall on my laptop, but
> this
> has never caused a problem for me.


There is never a problem running both a hardware firewall and a
software firewall--I do the same. The advice, which I and many
others give, is not to run two *software* firewalls at once.

You might want to consider, however, that your Windows XP
firewall pretty much duplicates what the hardware firewall does,
and provides little, if any, extra benfit. Both protect you
agiant sincoming attacks only. If you're going to run a software
firewall, I would recommend you run almost any of the third-party
ones, which would add outgoing protection.

--
Ken Blake - Microsoft MVP Windows: Shell/User
Please reply to the newsgroup