cannot access 2003 server remotely

  • Thread starter Thread starter KevinK
  • Start date Start date
K

KevinK

Greetings,

I am in the process of installing 4 servers with Windows 2003 Server
as the OS. I am learning as I go, was certified in NT but this is a
whole new world now and I am a bit lost...

I wish to be able to allow a user to connect over the Internet and log
on to one of the servers. I have set up a rule in the DSL hub/firewall
to allow all incoming from all on all ports and specified to direct it
to the internal IP address of the server. When I type in the IP
address of the DSL router, I can log into the router itself over the
Internet. When I specify a port, for instance port 1723, I get a "this
page cannot be displayed" error page. Down the bottom of the screen it
states "Cannot find server or DNS error". I have done, I think, all of
the steps listed in the book I am using but I keep getting this
problem.

I know I have done or am doing something incorrect and I am hoping
that someone will be able to help me get this working...

Thanks!
 
There are many ways to connect to a Win 2003 server over the Internet.
However, these 'ways' are determined by the services the server is
configured to provide and the client used to access them. The most common
are:

1. Web services - You are able to connect to your router with Internet
Explorer because it has a built-in web server which provides a page for
remote administration. You can configure Windows Server 2003 as a web
server as well. Use the Configure My Server wizard to install IIS. This
will give the client access to whatever resources you care to provide
through the web site.

2. VPN - You refer to port 1723, and this is used to provide VPN access
using PPTP protocol. You can configure a Windows Server 2003 machine as a
VPN server. Use Administrative Tools/Routing and Remote Access. You will
probably want to disable the Basic Firewall after you do this. In Windows,
you do not use Internet Explorer to connect to a VPN server. On the client,
use the Make New Connection wizard to configure a VPN connection to the
server. See:

http://www.microsoft.com/resources/...enterprise/proddocs/en-us/vpn_server_role.asp

VPN essentially lets the remote client behave as if it were connected to the
local LAN.

3. Remote Desktop/terminal Services - On the Windows Server 2003 machine,
right click My Computer and select Properties. Click 'Allow users to
connect remotely to this server remotely'. On the client, download and
install the RDP client - you can get it here:

http://www.microsoft.com/windowsxp/downloads/tools/rdclientdl.mspx

RDP essentially allows you to control the server remotely. You can also
establish an RDP connection using Internet Explorer, but the server must be
running IIS and be configured with the tsweb site.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
 
"I have set up a rule in the DSL hub/firewall
to allow all incoming from all on all ports and specified to direct it
to the internal IP address of the server."
Click to expand...

Sounds like you've got your whole network open?? Might want to think about locking down that firewall.

Everything Doug has said is right on the money.

Ian Bagnald
MCSE:Security Windows 2000
MCSA:Security Windows 2000
COMPTIA A+
 
InBan said:
Sounds like you've got your whole network open?? Might want to think about
locking down that firewall.
Click to expand...

I just opened it up to test if I could get through. I figured if I
opened all ports I would at least see if I could access the server
without making a stupid error by trying the wrong port or something.
Once I figure that out, then I can try and access it on a specific
port. I did lock it down right after my unsuccessful test... It does
appear that VPN is what I am after, will be giving it another go
tomorrow and see how I make out. Thanks for the responses, appreciate
the help!

Kevin
 
Back
Top