|
Does Winsock RSHD/NT work
with Windows XP Service Pack 2?
Yes, it does, based on our testing.
But if you have the new Windows Firewall enabled, you must
configure it to allow Winsock RSHD/NT to receive incoming
connections. By default, the firewall will block the
connections.
You can do this interactively through the
Windows Control Panel. Double-click on the Windows
Firewall icon in the Control Panel, then go to the Exceptions
tab. Click the Add Program button. Click the
Browse button and find the file "wrshdnt.exe", which
will be in the Winsock RSHD/NT installation folder (by
default, "wrshdnt" on the system drive). Click
the Change Scope button if you want to limit connections only
from your network ("subnet") or from a specific list
of IP addresses. (If you do not click the Change Scope
button to do this, it will allow incoming rsh/rcp connections
from any computer, limited only by your RSHD/NT Security
File.) Click OK to save it, then mark the new line
showing "wrshdnt.exe" with a check. This will
allow RSHD/NT to accept connections again.
You can also accomplish this with a command
from a Command Prompt:
netsh firewall add
allowedprogram program="c:\wrshdnt\wrshdnt.exe" name
= "Winsock RSHD/NT" mode=enable scope=subnet
where you replace "c:\wrshdnt"
with the folder where you installed Winsock RSHD/NT. You
can also replace "subnet" at the end with
"all" to allow connections from any computer.
Using "subnet" allows connections only from
computers on your internal network.
Does Winsock REXECD/NT work
with Windows XP Service Pack 2?
Yes, it does, based on our testing.
But if you have the new Windows Firewall enabled, you must
configure it to allow Winsock REXECD/NT to receive incoming
connections. By default, the firewall will block the
connections.
You can do this interactively through the
Windows Control Panel. Double-click on the Windows
Firewall icon in the Control Panel, then go to the Exceptions
tab. Click the Add Program button. Click the
Browse button and find the file "wrexecnt.exe",
which will be in the Winsock REXECD/NT installation folder (by
default, "wrexecnt" on the system drive).
Click the Change Scope button if you want to limit connections
only from your network ("subnet") or from a specific
list of IP addresses. (If you do not click the Change
Scope button to do this, it will allow incoming rexec
connections from any computer, limited only by your REXECD/NT
Security File.) Click OK to save it, then mark the new
line showing "wrexecnt.exe" with a check. This
will allow REXECD/NT to accept connections again.
You can also accomplish this with a command
from a Command Prompt:
netsh firewall add
allowedprogram program="c:\ wrexecnt\wrexecnt.exe"
name = "Winsock
REXECD/NT"
mode=enable scope=subnet
where you replace "c:\wrexecnt"
with the folder where you installed Winsock REXECD/NT.
You can also replace "subnet" at the end with
"all" to allow connections from any computer.
Using "subnet" allows connections only from
computers on your internal network.
Does Winsock RCP/RSH/REXEC
work with Windows XP Service Pack 2?
Yes, it does, based on our
testing.
But please note that the Windows Firewall
will pop up a window asking you if you want to block or
unblock the program the first time you run rsh.exe (or
wrsh.exe) or rexec.exe (or wrexec.exe). This is because
both the rsh and rexec protocols use two network connections
(unless the -c option is used). The first connection is
a simple outbound connection and no firewall configuration is
needed for this. But the second connection is an inbound
connection, connecting from the server back to your PC, and
this is affected by the firewall.
(This does not apply to the rcp command -
rcp only uses one connection.)
When this message appears, you can simply
click the Unblock button and you will no longer see the
message. (If you click the Block button, you will
effectively disable rsh or rexec, so you should not do that.)
This does not apply if you use our rsh or
rexec with the -c option, because the -c option causes rsh and
rexec to use only one connection to the server.
You can also configure the Windows firewall
to allow rsh.exe and rexec.exe through the firewall so the
message does not initially pop up. You can do this
through the Control Panel's Windows Firewall icon. Go to
the Exceptions tab. Click the Add Program button.
Click the Browse button and find the rsh.exe (or rexec.exe)
file in the folder where you installed Winsock RCP/RSH/REXEC.
If you want, then click the Change Scope button if you wish to
restrict all rsh or rexec connections to your local subnet or
specific IP addresses. Normally, you will not want to do
this - you will want to allow all addresses (the default)
because these are connections initiated by you. But you
can choose to restrict them if you like. Click OK to
save, then mark the new line showing rsh.exe (or rexec.exe)
with a check, and Windows will not display the firewall dialog
the first time rsh or rexec is run.
You can also accomplish this with a command
from a Command Prompt:
netsh firewall add
allowedprogram program="c:\rcprsh32\rsh.exe" name =
"Winsock RSH" mode=enable scope=all
netsh firewall add
allowedprogram program="c:\rcprsh32\rexec.exe" name
= "Winsock REXEC" mode=enable scope=all
where you replace "c:\rcprsh32"
with the folder where you installed Winsock RCP/RSH/REXEC.
You can also replace "all" at the end with
"subnet" to restrict outgoing rsh connections to
your local network.
Does Winsock RCMD32.DLL work
with Windows XP Service Pack 2?
Yes, it does, based on our testing. It
is unaffected by the Windows Firewall and requires no
additional settings.
Does Winsock RCP32.DLL work
with Windows XP Service Pack 2?
Yes, it does, based on our testing. It
is unaffected by the Windows Firewall and requires no
additional settings.
|
