Page 2 - CMD functions

(Oo;?(It would have been solved at least as to WSH, apart from the result?)

(Oo;?(What about moving either one of the two? The former thread came from IIS forum as it is helpless, if I remember right.)

maybe it is better to be moved.
because this subject is releated to IIS than Windows.

people who needs help on the same subject look IIS forum first, I think..

thank you

Thread moved.

you remember right
accessing to the server is related to Windows security
but
creating an user who can access to the server via wscript.shell is related to IIS

Wrong

WSH is not an IIS function, it's part of the Microsoft scripting engine. IIS is only one envrionment that can use wsh but it can be used from VB, C, SQL Server, and any other COM-capable environment. So by moving your post to a low-traffic forum like IIS you're limiting the possible assistance.

You need to fully understand windows file permissions to secure your server. Correct permission settings will prevent use from IIS, VB, C, or any other program.

IIS is unable to use WSH on it's own. Your web programmers are the only way any WSH hacks get on your server through IIS. Why do you allow your web code to use WSH anyway, just block it from the IIS user account.

Get a firewall. Your earlier statement that you can't use a firewall if you use remote control is completely incorrect. You need a firewall and you need to securely connect your remote control. I use SSH and tunnel the remote control ports through the SSH connection myself. Better for you is probably a good VPN router/firewall, juniperr is very knowledgeable on these.

So welcome back to the IIS forum anyway.