A
adeveloper
Hi,
We have an application which is going to be installed on a clients Windows
2000 Server and the interface to the app is accessed from a web site on that
server (ASP + SQL Server). The server lives in a DMZ in the client network.
We need remote access to the server to administer the product but we have
run into problems with the client who do not want to grant us remote access
to the server because of security concerns. The clients policy is to not
provide remote access to any of their servers to anyone outside the
organisation - which of course we can understand but doesn't work for us for
this application because we will need to access the server heavily during
the initial period after it is installed. We only need access to the server
from our own PCs/networks so it only needs to be opened to our ranges of
IPs.
So we want to know what is the most secure configuration is we could access
the client server with using terminal services?
What about VPN? I have heard you can use certifications with VPN - could we
set up a VPN connection on the server that only accepted connections from a
set of IPs and required a certificate on those PCs to be present in addition
to a password?
What I am thinking is that to prevent IP Spoofing that we need to do
something more than just allowing access to a fixed set of IPs in the
firewall.
It seems if we can encrypt the connection, require a certificate and only
allow access from a fix set of IPs then we would have quite a secure set up
for remote access - what do you think?
We could consider using other remote access clients - but would prefer to
stick with terminal services if it is possible to set up really secure
access with it.
Most grateful for any info
Peter Jansen
We have an application which is going to be installed on a clients Windows
2000 Server and the interface to the app is accessed from a web site on that
server (ASP + SQL Server). The server lives in a DMZ in the client network.
We need remote access to the server to administer the product but we have
run into problems with the client who do not want to grant us remote access
to the server because of security concerns. The clients policy is to not
provide remote access to any of their servers to anyone outside the
organisation - which of course we can understand but doesn't work for us for
this application because we will need to access the server heavily during
the initial period after it is installed. We only need access to the server
from our own PCs/networks so it only needs to be opened to our ranges of
IPs.
So we want to know what is the most secure configuration is we could access
the client server with using terminal services?
What about VPN? I have heard you can use certifications with VPN - could we
set up a VPN connection on the server that only accepted connections from a
set of IPs and required a certificate on those PCs to be present in addition
to a password?
What I am thinking is that to prevent IP Spoofing that we need to do
something more than just allowing access to a fixed set of IPs in the
firewall.
It seems if we can encrypt the connection, require a certificate and only
allow access from a fix set of IPs then we would have quite a secure set up
for remote access - what do you think?
We could consider using other remote access clients - but would prefer to
stick with terminal services if it is possible to set up really secure
access with it.
Most grateful for any info
Peter Jansen