Re: Remote View/Control
From: Terry (it_at_REMOVETHISfloydautomatic.co.uk)
Date: 08/19/04
- Next message: Bill Grant: "Re: Problem with Server2k3 dropping network configuration"
- Previous message: Daljit Singh: "Denying Network Access"
- In reply to: Miha Pihler: "Re: Remote View/Control"
- Next in thread: anonymous_at_discussions.microsoft.com: "Re: Remote View/Control"
- Reply: anonymous_at_discussions.microsoft.com: "Re: Remote View/Control"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 19 Aug 2004 09:25:27 +0100
Hello Mike,
RDP works just fine. I'm noting the VPN requirements as that is the next
thing for me to do. As I'm running Zonealarm Pro firewall I note that I will
have to enable some ports. Not too sure about NAT getting in the way but
seem to recall an update to one of the protocols to allow the handling of
NAT.
To really make things a little tricky, my ISP dishes out a dynamic IP for my
ADSL connection which is leased for a period of time before being changed.
Regards
"Miha Pihler" <mihap-news@atlantis.si> wrote in message
news:eXIqo8bhEHA.2784@TK2MSFTNGP09.phx.gbl...
> Hi,
>
> On your firewall you need to open TCP port 3389 and I would open it only
> from your home IP if you have static IP, so that other internet users
can't
> connect to server using TS.
>
> 192.168.1.x is a private IP address and you can only use it inside your
LAN
> or WAN or over VPN. If you will connect to your server from home over
> Internet (not VPN) you will need to enter server's _public_ IP address.
> Check your firewall since it is doing NAT (Network Address Translation)
for
> you.
>
> In MSTSC client you don't have to specify TCP port if you will use 3389
port
> (it is default port). Here are some examples how this would look.
>
> Using IP:
> http://freeweb.siol.net/mpihler/ip.jpg
>
> Using name:
> http://freeweb.siol.net/mpihler/name.jpg
>
> After you connect it would look something like this:
> http://freeweb.siol.net/mpihler/session.jpg
>
> I hope this helps,
>
> Mike
>
> "Mario" <anonymous@discussions.microsoft.com> wrote in message
> news:8ca601c485a7$1a569110$a401280a@phx.gbl...
> > Hi Mike,
> > thank you for your response.
> >
> > This is my scenario. I have a windows server 2003 server
> > sitting behind a SMC broadband router. I want to be able
> > to connect to the server from home using TS. What
> > exactly do I need to do in the router configuration page
> > to allow my connection through the sever?
> > You mentioned port 3389 to be open for TCP/IP is that
> > correct?
> > Also, you said to enter the name or IP address of the
> > server, does that mean the PRIMARY DNS IP address?
> > because my server is getting an ip address from my router
> > (i.e. 192.168.1.x)
> >
> > Let me see if I have the correct: After setting up
> > remote desktop on both, the server and the home pc with
> > th especific user account, forwarding the 3389 port to
> > TCP/IP and specifying the server's IP addres I open up
> > the remote desktop connection window at home and the as
> > an example: 192.168.1.x:3389 (where the IP address is the
> > PRIMARY DNS IP ADDRESS) and click connect?
> >
> > I woud really appreciate it if you can confirm my theory
> > or if you can correct my procedures.
> >
> > Mario Hernandez
> >
> > >-----Original Message-----
> > >Hi Mario,
> > >
> > >Windows 2003 by default installs RDP which you can use
> > to administer
> > >servers. You can have up to two concurrent connections
> > to one server (two
> > >administrators can work on server at a time using TS).
> > >Even with TS installed, they are disabled by default. To
> > enable it right
> > >click My Computer on server and click Remote tab. Select
> > the option where is
> > >says "Allow users to connect remotely to this computer".
> > Here you can also
> > >add any non administrator users that will use TS to
> > access it. Apply the
> > >settings and close all the windows.
> > >
> > >On your windows XP click on Start > Run > mstsc and
> > click OK. Enter name of
> > >IP of server and click OK. Well from here there should
> > be no problems.
> > >
> > >If you need to access remote server or other network
> > make sure that TCP port
> > >3389 is not blocked.
> > >
> > >Mike
> > >
> > >"Mario" <anonymous@discussions.microsoft.com> wrote in
> > message
> > >news:174d01c48567$5af0e940$a301280a@phx.gbl...
> > >> I am looking for a way to manage my Windows Server 2003
> > >> remotely. Do you have detailed instructions on how to
> > >> configure TS to allow me to do that from my XP pro
> > system?
> > >>
> > >> I would really appreciate your information.
> > >>
> > >> Thank you,
> > >>
> > >> Mario Hernandez
> > >> info@marioh.com
> > >>
> > >>
> > >> >-----Original Message-----
> > >> >Hello Mike,
> > >> >I have spotted an old webcast I could watch to give me
> > >> an overview, I
> > >> >suppose what I need to know is some basic setup
> > >> requirements for the server
> > >> >and XP client. Any HOWTO docs on this please?
> > >> >Regards
> > >> >
> > >> >"Miha Pihler" <mihap-news@atlantis.si> wrote in
> > message
> > >> >news:e1DA6N7gEHA.2952@TK2MSFTNGP09.phx.gbl...
> > >> >> I use terminal service daily to access and manage
> > >> servers at remote sites.
> > >> >I
> > >> >> do it all from my Windows XP. In Windows 2003 TS is
> > >> installed by default
> > >> >it
> > >> >> is just not enabled. In Windows 2000 you have to
> > >> select it when installing
> > >> >> server.
> > >> >>
> > >> >> TS Client that comes with Windows XP is better
> > >> (faster) then the one that
> > >> >> comes with Windows 2000. You can even install it on
> > >> Windows 98 and manage
> > >> >> server from there.
> > >> >>
> > >> >> TS is also much faster then VNC.
> > >> >>
> > >> >> Anything special that you would like to know? Any
> > >> special requirements?
> > >> >>
> > >> >> Mike
> > >> >>
> > >> >> "Terry" <it@REMOVETHISfloydautomatic.co.uk> wrote in
> > >> message
> > >> >> news:O2WARr6gEHA.1972@TK2MSFTNGP09.phx.gbl...
> > >> >> > Thanks Mike,
> > >> >> > I need to manage the server from an XP client.
> > >> Anyspecial considerations
> > >> >> to
> > >> >> > use Terminal Services? I have used VNC before,
> > works
> > >> quite well on
> > >> >Win98.
> > >> >> > Regards
> > >> >> >
> > >> >> > "Miha Pihler" <mihap-news@atlantis.si> wrote in
> > >> message
> > >> >> > news:OyDvuU6gEHA.1644@tk2msftngp13.phx.gbl...
> > >> >> > > Depending on operating system and other
> > >> requirements, you could
> > >> >probably
> > >> >> > use
> > >> >> > > Terminal Service. Terminal Services work on
> > >> Windows 2000 Server or
> > >> >newer
> > >> >> > > operating system (Windows XP, Windows 2003). In
> > >> Windows 2003 Microsoft
> > >> >> > added
> > >> >> > > support for console logon.
> > >> >> > >
> > >> >> > > If you are looking for 3rd party tools that will
> > >> also work on older
> > >> >> > > operating systems, look at VNC.
> > >> http://www.realvnc.com/
> > >> >> > >
> > >> >> > > I hope this helps,
> > >> >> > >
> > >> >> > > Mike
> > >> >> > >
> > >> >> > > "Terry" <it@REMOVETHISfloydautomatic.co.uk>
> > wrote
> > >> in message
> > >> >> > > news:Obn8RM6gEHA.632@TK2MSFTNGP12.phx.gbl...
> > >> >> > > > What are the best ways to be able to manage
> > the
> > >> server from another
> > >> >> > > desktop?
> > >> >> > > > Do I need a KVM over Cat5 for instance? or is
> > >> there another way?
> > >> >> > > > Regards
> > >> >> > > >
> > >> >> > > >
> > >> >> > >
> > >> >> > >
> > >> >> >
> > >> >> >
> > >> >>
> > >> >>
> > >> >
> > >> >
> > >> >.
> > >> >
> > >
> > >
> > >.
> > >
>
>
- Next message: Bill Grant: "Re: Problem with Server2k3 dropping network configuration"
- Previous message: Daljit Singh: "Denying Network Access"
- In reply to: Miha Pihler: "Re: Remote View/Control"
- Next in thread: anonymous_at_discussions.microsoft.com: "Re: Remote View/Control"
- Reply: anonymous_at_discussions.microsoft.com: "Re: Remote View/Control"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
