Re: Attn. Microsoft - BUG REPORT!
From: Jim (anonymous_at_discussions.microsoft.com)
Date: Wed, 18 Feb 2004 01:41:43 -0800
I checked out your web site. Nice work! I've bookmarked it
for future reference.
Since you're an MVP you may be able to pass this
information on to the appropriate people at Microsoft.
As my response to Mr. Garard indicates, the problem with
4DOS is related to upgrading from Win98se, and
NOT "updating" WinXP. Forgive me for not remembering the
details, but it's been over a month since I did the
upgrade, and I spent much time browsing the KB looking for
a solution before I tried swapping out 4DOS for
COMMAND.COM. If this problem had been described I would
have been up and running much faster. It should be easy
enough for MS to reproduce this problem, and write a nice
KB article about it.
The FTP problems are real enough, and I'm not the only
person to have these problems. Just search
the "Networking" newsgroup. The only solution everyone
seems to have is to use PASV mode. Unfortunately, PASV
mode was intended to be used when you're operating behind
a firewall, and the firewall won't accept connections
which are initiated from the server (which is how the
default PORT mode works). As I said, I'm not using any
type of firewall, NAT, ICS, filtering, or anything else
that would explain this problem.
What's REALLY a kicker here is that the WinXP FTP console
client (or any other client using PORT commands) TELLS the
server which port to open, and then allows the server to
open the port, but blocks packets sent to this port, which
leaves the FTP client hanging. Others on the "Networking"
newsgroup have said that the WinXP console FTP client used
to work a few months ago, before some of the more recent
updates. I only recently tried it for the first time,
having already installed all updates. Without support for
PASV mode, the WinXP console FTP client is pretty useless
as long as this problem exists.
Using PASV mode with Cygwin FTP or WS-FTP is a workable
solution for now, but it would be nice if this problem was
fixed as this is NOT how RFC 0959 intended for FTP to work.
The timeout problem is more pressing. I have to forcibly
shutdown the FTP client after each large file transfer.
This means shutting down and restarting Cygwin. This is a
real pain if I have a number of files to transfer (which I
often do). The user command MPUT can't be used because it
requires the FTP client to negotiate each file using port
21. In other words, it sends the first file and then hangs.
Forgive me for being impatient, but I only decided to post
these problems after much searching and reading in both
the KB and newsgroups, and seeing other users having the
same problems being given the same kind of condescending
answers, or just plainly being ignored. I'm only asking
that someone at Microsoft give it a try and confirm
whether the problems exist. I'm also a software developer,
though I don't develop Windows applications. When my
customers report a bug I don't humiliate them, tease them,
or deny that the problem exists. Rather, I do everything I
can to reproduce the problem and fix it. Otherwise, my
customers won't use my software, and I won't have a job!
>No comment, but I agree!
>All the Best,
>Troubleshooting Windows XP
>Utilities for Windows XP
>"Pat Garard" <apgarardATbigpondPERIODnetPERIODau> wrote
>> If you are a Man of Substance, as obviously you are,
>> You MAY change the world!!!!!!!!!!!!
>> You can install ALL updates from
>> Please do NOT feel that you MUST use Windows
>> Update - that's for Nerds!!
>> Please do NOT feel that you MUST install EVRY
>> Update - also for NERDS!!
>> (We NERDS know that to use Windows Update, we
>> need Internet Explorer and the Default Command Line
>> Interpreter - a Problem? What Problem????)
>> Excercise your Freedom, together with a commensurate
>> level of responsibility!!
>> Pat Garard