"Jeff Cochran" <jeff.nospam@zina.com> wrote in message
news:42bfeab4.92441109@msnews.microsoft.com...
> On Sun, 26 Jun 2005 14:47:06 GMT, "John Thomas"
> <Almanaticus@netscape.net> wrote:
>
>>
>>"Jeff Cochran" <jeff.nospam@zina.com> wrote in message
>>news:42beaa1f.75909750@msnews.microsoft.com...
>>> On Sun, 26 Jun 2005 04:22:48 GMT, "John Thomas"
>>> <Almanaticus@netscape.net> wrote:
>>>
>>>>
>>>>"Jeff Cochran" <jeff.nospam@zina.com> wrote in message
>>>>news:42c51e60.40135343@msnews.microsoft.com...
>>>>> On Fri, 24 Jun 2005 00:31:50 -0700, "Fred Exley" <fexley221@cox.com>
>>>>> wrote:
>>>>>>> Oh, I gave up on it several months ago. It wouldnt let me log-in. I
>>>>>>> tried
>>>>>>> for several weeks and gave up. Maybe the other guy can make it work.
>>>>>>>
>>>>>>
>>>>>>I had the same problem, then tried turning off the msft firewall
>>>>>>altogether,
>>>>>>and that fixed it. -Fred
>>>>>
>>>>> Opening the proper ports would also have fixed it, and you'd still be
>>>>> protected by the firewall.
>>>>>
>>>>> Jeff
>>>>
>>>>You are presuming everyone knows how to do that.
>>>
>>> Nope. But if the question had been asked, the answer would have
>>> instructed them in doing this. Instructions for using the Windows
>>> firewall are easily available.
>>>
>>> Disabling securtiy instead of correctly configuring security tools can
>>> lead to other problems. If their system works fine this way, then
>>> congratulations. But for others who read the post in Google, it's
>>> important they realize that disabling the firewall and losing all
>>> protection isn't the only option they have.
>>>
>>> For those that want to know how to use the Windows Firewall and allow
>>> services such as FTP access, a good starting point is here:
>>>
>>>
http://support.microsoft.com/default.aspx?scid=kb;en-us;875357 >>>
>>> Jeff
>>
>>Hey Jeff, the comment was about configuring ports, not disabling
>>firewalls. You
>>are presuming that everyone else has the same technical know-how you do.
>>Simply
>>saying something needs to be done, and using terminology and processes
>>that not
>>everyone understands, only adds to the frustration of something Im sure is
>>simple, if it were only explained in simple terms. Try teaching like a
>>teacher,
>>and others can more easily understand what you are trying to convey.
>
> So what would you like to know? The post I responded to stated simply
> that the solution found by the poster was to disable the firewall
> entirely. I simply stated that opening the correct ports instead of
> disabling the firewall would be a better option. Where did anyone get
> the idea that I should be conducting a lesson on opening firewall
> ports? And did the KB article I listed not help?
>
> Okay, how about this then:
>
> Go to Network Connections in the Control Panel, right click on your
> network connection and choose Properties. Choose the Advanced tab and
> make sure Protect My Computer is checked. That turns on the Windows
> firewall. To allow access for FTP, click on the Settings button,
> check the FTP Server box. If you don't see an FTP Server option, it's
> because you haven't installed FTP yet. Click Okay until you've closed
> all the windows.
>
> Is that sufficient?
>
> If you need more, look at:
>
> How to manually open ports in Internet Connection Firewall in Windows
> XP:
>
http://support.microsoft.com/default.aspx?scid=kb;en-us;308127 >
> How to configure the Windows Firewall feature in Windows XP Service
> Pack 2:
>
http://support.microsoft.com/default.aspx?scid=kb;en-us;875356 >
> There's also a decent explanation in your help files, and Google will
> list dozens of sites with detailed instructions including pictures.
>
> Class dismissed.
>
> Jeff
Hey thanks for the additional pointers. I turned on the firewall and added
an exception for port 21, and it's working fine now. -Fred