I have a 2003 Server running Virtual Server 2005 with all updates.

I have only one Virtual Machine running. The VM is a server 2003 machine.
The VM 2003 Server can access the network and Internet. I can ping it from
desktops on the LAN and other servers. Everything seems to be working as
expected except one thing. I cannot Remote Desktop (Terminal Service) into
the VM from any PCs.

When I am at my desk I Remote Desktop into all my other servers to do Admin
stuff. When I try to get into this VM I get "This computer can not connect
to the remote computer". I can ping the VM and from Windows Explorer I can
view the VMs files. (\\util2\c$) I have tried it from 3 or 4 different
machines.

So I guess the first thing to ask is, Can you Terminal Service into a VM or
do you HAVE to use the VMRC?

I do have Remote Desktop enabled in the VM. The firewall is NOT running. I
have been trying to get this going for a week now and I am running out of
ideas.

Any thoughts?

Thanks,

Yes, you definitely can use RDP (Terminal Services) into a VM running
on Virtual Server, there is no requirement to only use VMRC.

>I do have Remote Desktop enabled in the VM. The firewall is NOT running. I
>have been trying to get this going for a week now and I am running out of
>ideas.

I would suspect a firewall somewhere is getting you, but it's real
hard to tell.

First thing I'd try is a NETSTAT -a in the VM to see if it's even
listening on the normal RDP port 3389.

--
Bob Comer


On Tue, 1 Apr 2008 10:55:01 -0700, JohnnyF
<JohnnyF@discussions.microsoft.com> wrote:

>I have a 2003 Server running Virtual Server 2005 with all updates.
>
>I have only one Virtual Machine running. The VM is a server 2003 machine.
>The VM 2003 Server can access the network and Internet. I can ping it from
>desktops on the LAN and other servers. Everything seems to be working as
>expected except one thing. I cannot Remote Desktop (Terminal Service) into
>the VM from any PCs.
>
>When I am at my desk I Remote Desktop into all my other servers to do Admin
>stuff. When I try to get into this VM I get "This computer can not connect
>to the remote computer". I can ping the VM and from Windows Explorer I can
>view the VMs files. (\\util2\c$) I have tried it from 3 or 4 different
>machines.
>
>So I guess the first thing to ask is, Can you Terminal Service into a VM or
>do you HAVE to use the VMRC?
>
>I do have Remote Desktop enabled in the VM. The firewall is NOT running. I
>have been trying to get this going for a week now and I am running out of
>ideas.
>
>Any thoughts?
>
>Thanks,

On Tue, 1 Apr 2008 10:55:01 -0700, JohnnyF
<JohnnyF@discussions.microsoft.com> wrote:

>So I guess the first thing to ask is, Can you Terminal Service into a VM or
>do you HAVE to use the VMRC?

Yes you can, I have a Win2003 Enterprise Server running under
VirtualServer 2005 on my XP-Pro host and whenever I want to do admin
stuff on it I use RDP. I think that I have never even used the VMRC+
console for this.

There is something else getting you.
Maybe the guest does not recognize you as a valid user?


Bo Berglund

Thanks for the quick response Bob.

I know it is not a firewall. I have other servers on the same switch and
they can interact with the VM server in every way but RDP. However, when I
did the Netstat -a it does not show that it is listening on port 3389 (see
below). I did verify in the registry it was set to the default 3389. I also
checked the Services and it shows Terminal Services is Started. One funny
thing though is that when you highlight Terminal Services it will not let you
stop or restart the service. Those buttons are grayed out.

So not Listening on 3389 my be the issue but since it says it is started and
since I can not Stop or restart the service, I am not sure what is next.

Bo, I did try and RDP in using the VMs local admin account but I still get
the same response.

I appreciate both of you taking the time to respond. if you have any other
ideas, I would be glad to hear them. Thanks. John

Proto Local Address Foreign Address State
TCP util2:http util2.hhhhh.local:0 LISTENING
TCP util2:epmap util2.hhhhh.local:0 LISTENING
TCP util2:microsoft-ds util2.hhhhh.local:0 LISTENING
TCP util2:1025 util2.hhhhh.local:0 LISTENING
TCP util2:1037 util2.hhhhh.local:0 LISTENING
TCP util2:1240 util2.hhhhh.local:0 LISTENING
TCP util2:netbios-ssn util2.hhhhh.local:0 LISTENING
TCP util2:netbios-ssn util2.hhhhh.local:0 LISTENING
TCP util2:2314 exchange1.hhhhh.local:epmap ESTABLISHED
TCP util2:2315 exchange1.hhhhh.local:1026 ESTABLISHED
TCP util2:ms-wbt-server util2.hhhhh.local:0 LISTENING
UDP util2:microsoft-ds *:*
UDP util2:isakmp *:*
UDP util2:1026 *:*
UDP util2:1027 *:*
UDP util2:2320 *:*
UDP util2:ipsec-msft *:*
UDP util2:ntp *:*
UDP util2:1028 *:*
UDP util2:1067 *:*
UDP util2:1092 *:*
UDP util2:ntp *:*
UDP util2:netbios-ns *:*
UDP util2:netbios-dgm *:*
UDP util2:ntp *:*
UDP util2:netbios-ns *:*
UDP util2:netbios-dgm *:*

"Robert Comer" wrote:

> Yes, you definitely can use RDP (Terminal Services) into a VM running
> on Virtual Server, there is no requirement to only use VMRC.
>
> >I do have Remote Desktop enabled in the VM. The firewall is NOT running. I
> >have been trying to get this going for a week now and I am running out of
> >ideas.
>
> I would suspect a firewall somewhere is getting you, but it's real
> hard to tell.
>
> First thing I'd try is a NETSTAT -a in the VM to see if it's even
> listening on the normal RDP port 3389.
>
> --
> Bob Comer
>
>
> On Tue, 1 Apr 2008 10:55:01 -0700, JohnnyF
> <JohnnyF@discussions.microsoft.com> wrote:
>
> >I have a 2003 Server running Virtual Server 2005 with all updates.
> >
> >I have only one Virtual Machine running. The VM is a server 2003 machine.
> >The VM 2003 Server can access the network and Internet. I can ping it from
> >desktops on the LAN and other servers. Everything seems to be working as
> >expected except one thing. I cannot Remote Desktop (Terminal Service) into
> >the VM from any PCs.
> >
> >When I am at my desk I Remote Desktop into all my other servers to do Admin
> >stuff. When I try to get into this VM I get "This computer can not connect
> >to the remote computer". I can ping the VM and from Windows Explorer I can
> >view the VMs files. (\\util2\c$) I have tried it from 3 or 4 different
> >machines.
> >
> >So I guess the first thing to ask is, Can you Terminal Service into a VM or
> >do you HAVE to use the VMRC?
> >
> >I do have Remote Desktop enabled in the VM. The firewall is NOT running. I
> >have been trying to get this going for a week now and I am running out of
> >ideas.
> >
> >Any thoughts?
> >
> >Thanks,
>

I just did some testing on my own W2K3 R2 server and the netstat
command output looks a little funny, but there is one sure way to see
if it's listening --

netstat -an|find "3389"

I wasn't able to see 3389 in the netstat -a command either.

Actually, now that I look harder, I think this line describe RDP:

TCP x3500cwu:ms-wbt-server x3500cwu.cwusa.local:0 LISTENING


--
Bob Comer




On Tue, 1 Apr 2008 11:53:01 -0700, JohnnyF
<JohnnyF@discussions.microsoft.com> wrote:

>Thanks for the quick response Bob.
>
>I know it is not a firewall. I have other servers on the same switch and
>they can interact with the VM server in every way but RDP. However, when I
>did the Netstat -a it does not show that it is listening on port 3389 (see
>below). I did verify in the registry it was set to the default 3389. I also
>checked the Services and it shows Terminal Services is Started. One funny
>thing though is that when you highlight Terminal Services it will not let you
>stop or restart the service. Those buttons are grayed out.
>
>So not Listening on 3389 my be the issue but since it says it is started and
>since I can not Stop or restart the service, I am not sure what is next.
>
>Bo, I did try and RDP in using the VMs local admin account but I still get
>the same response.
>
>I appreciate both of you taking the time to respond. if you have any other
>ideas, I would be glad to hear them. Thanks. John
>
> Proto Local Address Foreign Address State
> TCP util2:http util2.hhhhh.local:0 LISTENING
> TCP util2:epmap util2.hhhhh.local:0 LISTENING
> TCP util2:microsoft-ds util2.hhhhh.local:0 LISTENING
> TCP util2:1025 util2.hhhhh.local:0 LISTENING
> TCP util2:1037 util2.hhhhh.local:0 LISTENING
> TCP util2:1240 util2.hhhhh.local:0 LISTENING
> TCP util2:netbios-ssn util2.hhhhh.local:0 LISTENING
> TCP util2:netbios-ssn util2.hhhhh.local:0 LISTENING
> TCP util2:2314 exchange1.hhhhh.local:epmap ESTABLISHED
> TCP util2:2315 exchange1.hhhhh.local:1026 ESTABLISHED
> TCP util2:ms-wbt-server util2.hhhhh.local:0 LISTENING
> UDP util2:microsoft-ds *:*
> UDP util2:isakmp *:*
> UDP util2:1026 *:*
> UDP util2:1027 *:*
> UDP util2:2320 *:*
> UDP util2:ipsec-msft *:*
> UDP util2:ntp *:*
> UDP util2:1028 *:*
> UDP util2:1067 *:*
> UDP util2:1092 *:*
> UDP util2:ntp *:*
> UDP util2:netbios-ns *:*
> UDP util2:netbios-dgm *:*
> UDP util2:ntp *:*
> UDP util2:netbios-ns *:*
> UDP util2:netbios-dgm *:*
>
>"Robert Comer" wrote:
>
>> Yes, you definitely can use RDP (Terminal Services) into a VM running
>> on Virtual Server, there is no requirement to only use VMRC.
>>
>> >I do have Remote Desktop enabled in the VM. The firewall is NOT running. I
>> >have been trying to get this going for a week now and I am running out of
>> >ideas.
>>
>> I would suspect a firewall somewhere is getting you, but it's real
>> hard to tell.
>>
>> First thing I'd try is a NETSTAT -a in the VM to see if it's even
>> listening on the normal RDP port 3389.
>>
>> --
>> Bob Comer
>>
>>
>> On Tue, 1 Apr 2008 10:55:01 -0700, JohnnyF
>> <JohnnyF@discussions.microsoft.com> wrote:
>>
>> >I have a 2003 Server running Virtual Server 2005 with all updates.
>> >
>> >I have only one Virtual Machine running. The VM is a server 2003 machine.
>> >The VM 2003 Server can access the network and Internet. I can ping it from
>> >desktops on the LAN and other servers. Everything seems to be working as
>> >expected except one thing. I cannot Remote Desktop (Terminal Service) into
>> >the VM from any PCs.
>> >
>> >When I am at my desk I Remote Desktop into all my other servers to do Admin
>> >stuff. When I try to get into this VM I get "This computer can not connect
>> >to the remote computer". I can ping the VM and from Windows Explorer I can
>> >view the VMs files. (\\util2\c$) I have tried it from 3 or 4 different
>> >machines.
>> >
>> >So I guess the first thing to ask is, Can you Terminal Service into a VM or
>> >do you HAVE to use the VMRC?
>> >
>> >I do have Remote Desktop enabled in the VM. The firewall is NOT running. I
>> >have been trying to get this going for a week now and I am running out of
>> >ideas.
>> >
>> >Any thoughts?
>> >
>> >Thanks,
>>

Yep, that shoots that idea. This is what I get:

C:\Documents and Settings\hhhhadmin>netstat -an|find "3389"
TCP 172.16.10.11:3389 0.0.0.0:0 LISTENING

So it appears to be Listening. I assume the 0.0.0.0:0 indicates it is not
connected to anyone at the moment.

So now that we know it is listening, I need to figure out why it won't
Answer! Maybe I have Voice Mail turned on?

Thanks for the input, I'll keep searching.

John.

"Robert Comer" wrote:

> I just did some testing on my own W2K3 R2 server and the netstat
> command output looks a little funny, but there is one sure way to see
> if it's listening --
>
> netstat -an|find "3389"
>
> I wasn't able to see 3389 in the netstat -a command either.
>
> Actually, now that I look harder, I think this line describe RDP:
>
> TCP x3500cwu:ms-wbt-server x3500cwu.cwusa.local:0 LISTENING
>
>
> --
> Bob Comer
>
>
>
>
> On Tue, 1 Apr 2008 11:53:01 -0700, JohnnyF
> <JohnnyF@discussions.microsoft.com> wrote:
>
> >Thanks for the quick response Bob.
> >
> >I know it is not a firewall. I have other servers on the same switch and
> >they can interact with the VM server in every way but RDP. However, when I
> >did the Netstat -a it does not show that it is listening on port 3389 (see
> >below). I did verify in the registry it was set to the default 3389. I also
> >checked the Services and it shows Terminal Services is Started. One funny
> >thing though is that when you highlight Terminal Services it will not let you
> >stop or restart the service. Those buttons are grayed out.
> >
> >So not Listening on 3389 my be the issue but since it says it is started and
> >since I can not Stop or restart the service, I am not sure what is next.
> >
> >Bo, I did try and RDP in using the VMs local admin account but I still get
> >the same response.
> >
> >I appreciate both of you taking the time to respond. if you have any other
> >ideas, I would be glad to hear them. Thanks. John
> >
> > Proto Local Address Foreign Address State
> > TCP util2:http util2.hhhhh.local:0 LISTENING
> > TCP util2:epmap util2.hhhhh.local:0 LISTENING
> > TCP util2:microsoft-ds util2.hhhhh.local:0 LISTENING
> > TCP util2:1025 util2.hhhhh.local:0 LISTENING
> > TCP util2:1037 util2.hhhhh.local:0 LISTENING
> > TCP util2:1240 util2.hhhhh.local:0 LISTENING
> > TCP util2:netbios-ssn util2.hhhhh.local:0 LISTENING
> > TCP util2:netbios-ssn util2.hhhhh.local:0 LISTENING
> > TCP util2:2314 exchange1.hhhhh.local:epmap ESTABLISHED
> > TCP util2:2315 exchange1.hhhhh.local:1026 ESTABLISHED
> > TCP util2:ms-wbt-server util2.hhhhh.local:0 LISTENING
> > UDP util2:microsoft-ds *:*
> > UDP util2:isakmp *:*
> > UDP util2:1026 *:*
> > UDP util2:1027 *:*
> > UDP util2:2320 *:*
> > UDP util2:ipsec-msft *:*
> > UDP util2:ntp *:*
> > UDP util2:1028 *:*
> > UDP util2:1067 *:*
> > UDP util2:1092 *:*
> > UDP util2:ntp *:*
> > UDP util2:netbios-ns *:*
> > UDP util2:netbios-dgm *:*
> > UDP util2:ntp *:*
> > UDP util2:netbios-ns *:*
> > UDP util2:netbios-dgm *:*
> >
> >"Robert Comer" wrote:
> >
> >> Yes, you definitely can use RDP (Terminal Services) into a VM running
> >> on Virtual Server, there is no requirement to only use VMRC.
> >>
> >> >I do have Remote Desktop enabled in the VM. The firewall is NOT running. I
> >> >have been trying to get this going for a week now and I am running out of
> >> >ideas.
> >>
> >> I would suspect a firewall somewhere is getting you, but it's real
> >> hard to tell.
> >>
> >> First thing I'd try is a NETSTAT -a in the VM to see if it's even
> >> listening on the normal RDP port 3389.
> >>
> >> --
> >> Bob Comer
> >>
> >>
> >> On Tue, 1 Apr 2008 10:55:01 -0700, JohnnyF
> >> <JohnnyF@discussions.microsoft.com> wrote:
> >>
> >> >I have a 2003 Server running Virtual Server 2005 with all updates.
> >> >
> >> >I have only one Virtual Machine running. The VM is a server 2003 machine.
> >> >The VM 2003 Server can access the network and Internet. I can ping it from
> >> >desktops on the LAN and other servers. Everything seems to be working as
> >> >expected except one thing. I cannot Remote Desktop (Terminal Service) into
> >> >the VM from any PCs.
> >> >
> >> >When I am at my desk I Remote Desktop into all my other servers to do Admin
> >> >stuff. When I try to get into this VM I get "This computer can not connect
> >> >to the remote computer". I can ping the VM and from Windows Explorer I can
> >> >view the VMs files. (\\util2\c$) I have tried it from 3 or 4 different
> >> >machines.
> >> >
> >> >So I guess the first thing to ask is, Can you Terminal Service into a VM or
> >> >do you HAVE to use the VMRC?
> >> >
> >> >I do have Remote Desktop enabled in the VM. The firewall is NOT running. I
> >> >have been trying to get this going for a week now and I am running out of
> >> >ideas.
> >> >
> >> >Any thoughts?
> >> >
> >> >Thanks,
> >>
>

Finally got it running.

It turned out to be something in the Terminal Services Configuration setup
under Administrative Tools. I had been in there before but didn't see
anything the first time. This time I went to connections and then the
properties of the RDP-tcp connection. I changed the settings for the network
adaptor and I also added the Domain Admin group in the permissions. Not sure
which one fixed the issue but it is working.

Thanks for your input Bob and Bo.

Now to actually do something productive with this thing!

John

"JohnnyF" wrote:

> I have a 2003 Server running Virtual Server 2005 with all updates.
>
> I have only one Virtual Machine running. The VM is a server 2003 machine.
> The VM 2003 Server can access the network and Internet. I can ping it from
> desktops on the LAN and other servers. Everything seems to be working as
> expected except one thing. I cannot Remote Desktop (Terminal Service) into
> the VM from any PCs.
>
> When I am at my desk I Remote Desktop into all my other servers to do Admin
> stuff. When I try to get into this VM I get "This computer can not connect
> to the remote computer". I can ping the VM and from Windows Explorer I can
> view the VMs files. (\\util2\c$) I have tried it from 3 or 4 different
> machines.
>
> So I guess the first thing to ask is, Can you Terminal Service into a VM or
> do you HAVE to use the VMRC?
>
> I do have Remote Desktop enabled in the VM. The firewall is NOT running. I
> have been trying to get this going for a week now and I am running out of
> ideas.
>
> Any thoughts?
>
> Thanks,

>So it appears to be Listening. I assume the 0.0.0.0:0 indicates it is not
>connected to anyone at the moment.

It just means it's listening for no specific foreign IP address. When
you actually make an RDP connection the listener task stays there
looking the same, and another lines shows up for an actual connection.

>So now that we know it is listening, I need to figure out why it won't
>Answer! Maybe I have Voice Mail turned on?

Maybe. <g>

One thing about Win2003R2 that I've run in to is the firewall doesn't
always work the way that I expected, especially if you have RRAS
active too. If you have RRAS going, try disabling that and then
making sure the firewall is off and then check for a connection.

--
Bob Comer





On Tue, 1 Apr 2008 12:26:00 -0700, JohnnyF
<JohnnyF@discussions.microsoft.com> wrote:

>Yep, that shoots that idea. This is what I get:
>
>C:\Documents and Settings\hhhhadmin>netstat -an|find "3389"
> TCP 172.16.10.11:3389 0.0.0.0:0 LISTENING
>
>So it appears to be Listening. I assume the 0.0.0.0:0 indicates it is not
>connected to anyone at the moment.
>
>So now that we know it is listening, I need to figure out why it won't
>Answer! Maybe I have Voice Mail turned on?
>
>Thanks for the input, I'll keep searching.
>
>John.
>
>"Robert Comer" wrote:
>
>> I just did some testing on my own W2K3 R2 server and the netstat
>> command output looks a little funny, but there is one sure way to see
>> if it's listening --
>>
>> netstat -an|find "3389"
>>
>> I wasn't able to see 3389 in the netstat -a command either.
>>
>> Actually, now that I look harder, I think this line describe RDP:
>>
>> TCP x3500cwu:ms-wbt-server x3500cwu.cwusa.local:0 LISTENING
>>
>>
>> --
>> Bob Comer
>>
>>
>>
>>
>> On Tue, 1 Apr 2008 11:53:01 -0700, JohnnyF
>> <JohnnyF@discussions.microsoft.com> wrote:
>>
>> >Thanks for the quick response Bob.
>> >
>> >I know it is not a firewall. I have other servers on the same switch and
>> >they can interact with the VM server in every way but RDP. However, when I
>> >did the Netstat -a it does not show that it is listening on port 3389 (see
>> >below). I did verify in the registry it was set to the default 3389. I also
>> >checked the Services and it shows Terminal Services is Started. One funny
>> >thing though is that when you highlight Terminal Services it will not let you
>> >stop or restart the service. Those buttons are grayed out.
>> >
>> >So not Listening on 3389 my be the issue but since it says it is started and
>> >since I can not Stop or restart the service, I am not sure what is next.
>> >
>> >Bo, I did try and RDP in using the VMs local admin account but I still get
>> >the same response.
>> >
>> >I appreciate both of you taking the time to respond. if you have any other
>> >ideas, I would be glad to hear them. Thanks. John
>> >
>> > Proto Local Address Foreign Address State
>> > TCP util2:http util2.hhhhh.local:0 LISTENING
>> > TCP util2:epmap util2.hhhhh.local:0 LISTENING
>> > TCP util2:microsoft-ds util2.hhhhh.local:0 LISTENING
>> > TCP util2:1025 util2.hhhhh.local:0 LISTENING
>> > TCP util2:1037 util2.hhhhh.local:0 LISTENING
>> > TCP util2:1240 util2.hhhhh.local:0 LISTENING
>> > TCP util2:netbios-ssn util2.hhhhh.local:0 LISTENING
>> > TCP util2:netbios-ssn util2.hhhhh.local:0 LISTENING
>> > TCP util2:2314 exchange1.hhhhh.local:epmap ESTABLISHED
>> > TCP util2:2315 exchange1.hhhhh.local:1026 ESTABLISHED
>> > TCP util2:ms-wbt-server util2.hhhhh.local:0 LISTENING
>> > UDP util2:microsoft-ds *:*
>> > UDP util2:isakmp *:*
>> > UDP util2:1026 *:*
>> > UDP util2:1027 *:*
>> > UDP util2:2320 *:*
>> > UDP util2:ipsec-msft *:*
>> > UDP util2:ntp *:*
>> > UDP util2:1028 *:*
>> > UDP util2:1067 *:*
>> > UDP util2:1092 *:*
>> > UDP util2:ntp *:*
>> > UDP util2:netbios-ns *:*
>> > UDP util2:netbios-dgm *:*
>> > UDP util2:ntp *:*
>> > UDP util2:netbios-ns *:*
>> > UDP util2:netbios-dgm *:*
>> >
>> >"Robert Comer" wrote:
>> >
>> >> Yes, you definitely can use RDP (Terminal Services) into a VM running
>> >> on Virtual Server, there is no requirement to only use VMRC.
>> >>
>> >> >I do have Remote Desktop enabled in the VM. The firewall is NOT running. I
>> >> >have been trying to get this going for a week now and I am running out of
>> >> >ideas.
>> >>
>> >> I would suspect a firewall somewhere is getting you, but it's real
>> >> hard to tell.
>> >>
>> >> First thing I'd try is a NETSTAT -a in the VM to see if it's even
>> >> listening on the normal RDP port 3389.
>> >>
>> >> --
>> >> Bob Comer
>> >>
>> >>
>> >> On Tue, 1 Apr 2008 10:55:01 -0700, JohnnyF
>> >> <JohnnyF@discussions.microsoft.com> wrote:
>> >>
>> >> >I have a 2003 Server running Virtual Server 2005 with all updates.
>> >> >
>> >> >I have only one Virtual Machine running. The VM is a server 2003 machine.
>> >> >The VM 2003 Server can access the network and Internet. I can ping it from
>> >> >desktops on the LAN and other servers. Everything seems to be working as
>> >> >expected except one thing. I cannot Remote Desktop (Terminal Service) into
>> >> >the VM from any PCs.
>> >> >
>> >> >When I am at my desk I Remote Desktop into all my other servers to do Admin
>> >> >stuff. When I try to get into this VM I get "This computer can not connect
>> >> >to the remote computer". I can ping the VM and from Windows Explorer I can
>> >> >view the VMs files. (\\util2\c$) I have tried it from 3 or 4 different
>> >> >machines.
>> >> >
>> >> >So I guess the first thing to ask is, Can you Terminal Service into a VM or
>> >> >do you HAVE to use the VMRC?
>> >> >
>> >> >I do have Remote Desktop enabled in the VM. The firewall is NOT running. I
>> >> >have been trying to get this going for a week now and I am running out of
>> >> >ideas.
>> >> >
>> >> >Any thoughts?
>> >> >
>> >> >Thanks,
>> >>
>>

You're welcome, glad you got it going!

--
Bob Comer


On Tue, 1 Apr 2008 13:25:03 -0700, JohnnyF
<JohnnyF@discussions.microsoft.com> wrote:

>Finally got it running.
>
>It turned out to be something in the Terminal Services Configuration setup
>under Administrative Tools. I had been in there before but didn't see
>anything the first time. This time I went to connections and then the
>properties of the RDP-tcp connection. I changed the settings for the network
>adaptor and I also added the Domain Admin group in the permissions. Not sure
>which one fixed the issue but it is working.
>
>Thanks for your input Bob and Bo.
>
>Now to actually do something productive with this thing!
>
>John
>
>"JohnnyF" wrote:
>
>> I have a 2003 Server running Virtual Server 2005 with all updates.
>>
>> I have only one Virtual Machine running. The VM is a server 2003 machine.
>> The VM 2003 Server can access the network and Internet. I can ping it from
>> desktops on the LAN and other servers. Everything seems to be working as
>> expected except one thing. I cannot Remote Desktop (Terminal Service) into
>> the VM from any PCs.
>>
>> When I am at my desk I Remote Desktop into all my other servers to do Admin
>> stuff. When I try to get into this VM I get "This computer can not connect
>> to the remote computer". I can ping the VM and from Windows Explorer I can
>> view the VMs files. (\\util2\c$) I have tried it from 3 or 4 different
>> machines.
>>
>> So I guess the first thing to ask is, Can you Terminal Service into a VM or
>> do you HAVE to use the VMRC?
>>
>> I do have Remote Desktop enabled in the VM. The firewall is NOT running. I
>> have been trying to get this going for a week now and I am running out of
>> ideas.
>>
>> Any thoughts?
>>
>> Thanks,