IIS used to use the FTP-Data port (TCP-20) for communication rather than
picking a random high port. This was to assist with Firewall behavior. Might
see if forwarding port 20 will fix your issue.
-K
--- Original Message ---
From: "Pearson, Andrew" <[EMAIL PROTECTED]>
To: "'[EMAIL PROTECTED]
Javier,
There is also a product by Greyware Automation that does pretty much the
same thing called XO and uses a web browser for control:
http://www.greyware.com/products/xo/index.asp
If you're wanting to use something like a Desktop remote control, they're
things like port redirectors,
I would suggest you run their FPort utility on the server itself. That will
tell you what application is using which port. I would venture to guess
that those are random ports allocated by RPC services to provide server
functionality.
This is merely a guess, I but I would venture that this is a
You might want to check out Microsoft's TechNet-Security section. There's a
Tools & Checklist area there. In there, there is a document called "Windows
2000 Server Baseline Security Checklist":
http://www.microsoft.com/technet/security/tools/chklist/w2ksvrcl.asp
You might want to go thr
>-Original Message-
>From: Stefan Osterlitz [mailto:[EMAIL PROTECTED]]
>To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
>
>>Platform is not important, can be a UNIX or NT based FTP server. This
>>request has obvious security issues but if you knew the client you'd
>>agree this is the least of th
Unfortunately, the answer is server dependant. In both Unix and NT/2000 you
can script actions that can be triggered via a web interface.
With NT, you could simple use IIS, NT's integrated accounts, WMI, and ASP.
However, this would require you to take security precautions to make sure
the right
