Re: Terminal services for administration
- From: "Craig Vogel" <CraigVogel@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 27 Jan 2006 13:19:26 -0800
There is only one default gateway defined and it is on the adapter accessing
the internet, the other adapter has no gateway defined. Setting up the VPN
did that for me. I'll take a look at route.exe and see what I can do.
--
Regards,
Craig Vogel
"Jeff Pitsch [MVP]" wrote:
> What you'll have to do is remove teh default gateway from one of the NIC's,
> then manuallly setup the routing table use route.exe for that NIC. I'll see
> if I can track anything down but I can't promise anything.
>
> Jeff Pitsch
> Microsoft MVP - Terminal Services
> http://www.sbcgatekeeper.com
> Your Terminal Services Security Website
>
> "Craig Vogel" <CraigVogel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:A4150EF3-1A15-422B-8C6E-9F37DA7E5BF9@xxxxxxxxxxxxxxxx
> >I didn't set up any routing when I was using Windows 2000 so I haven't
> > manually setup anything on Windows 2003. Can you suggest any resources
> > where
> > I can find information on setting up the routing?
> > --
> > Regards,
> > Craig Vogel
> >
> >
> > "Jeff Pitsch [MVP]" wrote:
> >
> >> My guess is your config on the server is probalby not correct. Have you
> >> manually set up the internal router table correctly? Windows does not
> >> handle dual homing well at all.
> >>
> >> Jeff Pitsch
> >> Microsoft MVP - Terminal Services
> >> http://www.sbcgatekeeper.com
> >> Your Terminal Services Security Website
> >>
> >> "Craig Vogel" <CraigVogel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:DCF7C3D6-EB10-44A8-A0DB-CED3D8EAD916@xxxxxxxxxxxxxxxx
> >> > After reading a few of the other posting I tried to telnet using port
> >> > 3389.
> >> > The server has 2 LAN adapters. I can telnet to the adapter connected
> >> > to
> >> > the
> >> > local area netwok. I canot telnet to the adapter connected to the
> >> > internet.
> >> > I cannot telnet to the public IP address. As far as I can tell the
> >> > router
> >> > is
> >> > sending port 3389 messages to the server so I can only assume that the
> >> > port
> >> > is disabled for the second adapter. How do I enable port 3389 for both
> >> > adapters?
> >> > --
> >> > Regards,
> >> > Craig Vogel
> >> >
> >> >
> >> > "Craig Vogel" wrote:
> >> >
> >> >> I can connect to my windows 2003 server through the local area network
> >> >> using
> >> >> XP PRO remote desktop but am unable to do so from home. The error I
> >> >> get
> >> >> is
> >> >> as follows.
> >> >>
> >> >> "The client could not connect to the remote computer. Remote
> >> >> connections
> >> >> might not be enabled or the computer might be too busy to accept new
> >> >> connections. It is also possible that network problems are preventing
> >> >> your
> >> >> connection. Please try your connection again later. If the problem
> >> >> continues
> >> >> to occur, contact your administrator."
> >> >>
> >> >> This worked with a Windows 2000 server. I can setup a VPN connection
> >> >> from
> >> >> home to the same server. I assume there is something new in Windows
> >> >> 2003
> >> >> that I probably need to enable or disable but I can't seem to find it.
> >> >> Thanks for any help.
> >>
> >>
> >>
>
>
>
.
- References:
- Re: Terminal services for administration
- From: Jeff Pitsch [MVP]
- Re: Terminal services for administration
- From: Craig Vogel
- Re: Terminal services for administration
- From: Jeff Pitsch [MVP]
- Re: Terminal services for administration
- Prev by Date: Re: which apps can run on ts?
- Next by Date: RE: .Net 2.0 Application Background Color Shows Up as White on TS
- Previous by thread: Re: Terminal services for administration
- Next by thread: Re: Running Outlook on TS 2003
- Index(es):
Relevant Pages
|