Re: cant access server via remote desktop
- From: "Frankster" <Frank@xxxxxxxxxxxxxx>
- Date: Fri, 6 May 2005 09:31:29 -0600
Oops.. change all the "@" symbols below to periods ".". FQDN! Had a
momentary greyout I guess:) LOL!
-Frank
"Frankster" <Frank@xxxxxxxxxxxxxx> wrote in message
news:WaidnYP5rdhHFebfRVn-2g@xxxxxxxxxxxxxxx
> Well, it's been awhile since I check this, can't remember if it was under
> W2K/TS or W2K3 Remote Desktop, but...
>
> I found that I needed FQDN resolution to connect. IOW, Doing a TS/RD
> session to IP 1.2.3.4 wouldn't work, or NETBIOS machine name either (11
> char max). It had to be a FQDN like machinename@xxxxxxxxxxxxxxx
>
> So, if that is still true, make sure from the client machine you can
> resolve the TS's machinename@xxxxxxxxxxxxxx, then make sure you put that
> into the Remote Desktop window when attempting to connect.
>
> If you can't resolve it, you could manually edit the local host file to
> achieve it for testing purposes at least.
>
> -Frank
>
> "DG" <nothere@xxxxxxxxxxxxx> wrote in message
> news:eLTXvGAUFHA.2812@xxxxxxxxxxxxxxxxxxxxxxx
>> Sorry about crossing posts but I didn't know which to post in.
>>
>> The error that I get when I try to Remote desktop to my terminal server
>> while on the VPN is "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 connecting again later. If the
>> problem continues to occur, contact your administrator."
>>
>> I know that remote connections are enabled because I connect to the
>> server
>> when I am not on the VPN and am inside the firewall. I also know that
>> the
>> server is not too busy because I am the only one accessing it. My
>> testing
>> was done with a laptop. When inside the firewall, I am hardwired to the
>> network. To test the VPN I unplugged the network cable from the laptop
>> and
>> connected to a wireless router that is outside the firewall and connected
>> a
>> VPN back through the firewall. I also tested hardwired to a router
>> outside
>> the firewall w/ the VPN and still receive the same error. I can remote
>> desktop to all other servers. The servers are all virtual running on the
>> same machine under VM-Ware.
>>
>> Dan
>> "Michael Giorgio - MS MVP" <Michael.Giorgio@xxxxxxxxxxxxxxxxxxx> wrote in
>> message news:%23K7Alt%23TFHA.628@xxxxxxxxxxxxxxxxxxxxxxx
>>> Two things for starters, 1) Please do not cross post. 2) It's
>>> always best to follow-up "can't access server" with at least
>>> the specific error you received.
>>>
>>> "DG" <nothere@xxxxxxxxxxxxx> wrote in message news:
>>> > I have 5 servers running Win2k3 and a cisco router between them and
>>> > the
>>> > internet. Inside the network (behind the router/firewall) I can
>>> > access
>>> all
>>> > 5 servers via remote desktop. However, outside the network I use
>>> > either
>>> > cisco's client vpn or from another site where I have a site to site
>>> > vpn
>> I
>>> > can access all servers but one.
>>> >
>>> > The one that I can't access is running win2k3 and is my terminal
>> services
>>> > server. The fact that I can access the other 4 servers tells me that
>>> > it
>>> is
>>> > not the VPN or firewall but a setting on the terminal services server,
>>> maybe
>>> > MTU???. I am new to terminal services so any help would be
>>> > appreciated.
>>> >
>>> > Dan
>>> >
>>> >
>>>
>>>
>>
>>
>
>
.
- References:
- Re: cant access server via remote desktop
- From: Frankster
- Re: cant access server via remote desktop
- Prev by Date: Re: VPN Server getting confused
- Next by Date: Re: Strange Processes afoot
- Previous by thread: Re: cant access server via remote desktop
- Next by thread: Re: cant access server via remote desktop
- Index(es):
Relevant Pages
|
Loading