Prev: Roaming Profiles v Terminal Server Profiles
Next: Win32_SessionDirectorySession - DisconnectTime
From: Nancy Villa on 31 Aug 2006 13:56
I deleted the rdp-tcp connection in the terminal server configuration and
re-added the connections and I no longer get the error with the dependencies
however, I am still not able to connect via terminal server for some reason.
I have two servers set up. One is the domain controller with two nic cards,
the second nic card using the external ip address. When I put in the address
it will connect to a terminal server session on the dataserver and not the
domain controller. It is almost like it is passing through the connection.
When I try to connect to the domain controller while connected to the
dataserver I receive an error message.

The client cannot connect to the remote server. Remote computer might not
be enabled or the server might be to busy to accept new connections.

I know you solved my first problem should I restart a new quesion?

"cendrars" wrote:

> How did you make out?
>
> "Nancy Villa" wrote:
>
> > it isadomain.
> >
> > "cendrars" wrote:
> >
> > > Look inside the Terminal Services Configuration\Connections window. You can
> > > find this within the Administration tools. You will see your RDP listener
> > > there. Check the permissions on the RDP listener, should see local admins
> > > have access, be sure they are there.
> > >
> > > You can remove and recreate the listener.
> > >
> > > Does this SBS server reside within a Domain, or a workgroup? Thanks.
> > >
> > >
> > > "Nancy Villa" wrote:
> > >
> > > > I am running a windows 2003 SBS server and had termianl services configured
> > > > for administration. It was working for about a year and then it stopped.
> > > > I trouble shooting the issues. The terminal service is started. When I
> > > > check the proproperties and click the dependency tab, I receive the following
> > > > error:
> > > >
> > > > Service Dependencies; WIN32:the RPC server is unavailable.
> > > >
> > > > I check the RPC server service and it is started but when I click on
> > > > properties I receive the same error for dependencies; WIN32: the RPC server
> > > > is unavailalbe.
> > > >
> > > > I check the network conections and terminal services are binded to all
> > > > availalbe NIC cards.
From: cendrars on 31 Aug 2006 14:32
For the NICs servicing the local network, do you have the default gateway
address configured within the TCP-IP properties? Are both server configured
with static addresses?

You have checked the permissions for RDP? You are logging in with admin
account?

"Nancy Villa" wrote:

> I deleted the rdp-tcp connection in the terminal server configuration and
> re-added the connections and I no longer get the error with the dependencies
> however, I am still not able to connect via terminal server for some reason.
> I have two servers set up. One is the domain controller with two nic cards,
> the second nic card using the external ip address. When I put in the address
> it will connect to a terminal server session on the dataserver and not the
> domain controller. It is almost like it is passing through the connection.
> When I try to connect to the domain controller while connected to the
> dataserver I receive an error message.
>
> The client cannot connect to the remote server. Remote computer might not
> be enabled or the server might be to busy to accept new connections.
>
> I know you solved my first problem should I restart a new quesion?
>
> "cendrars" wrote:
>
> > How did you make out?
> >
> > "Nancy Villa" wrote:
> >
> > > it isadomain.
> > >
> > > "cendrars" wrote:
> > >
> > > > Look inside the Terminal Services Configuration\Connections window. You can
> > > > find this within the Administration tools. You will see your RDP listener
> > > > there. Check the permissions on the RDP listener, should see local admins
> > > > have access, be sure they are there.
> > > >
> > > > You can remove and recreate the listener.
> > > >
> > > > Does this SBS server reside within a Domain, or a workgroup? Thanks.
> > > >
> > > >
> > > > "Nancy Villa" wrote:
> > > >
> > > > > I am running a windows 2003 SBS server and had termianl services configured
> > > > > for administration. It was working for about a year and then it stopped.
> > > > > I trouble shooting the issues. The terminal service is started. When I
> > > > > check the proproperties and click the dependency tab, I receive the following
> > > > > error:
> > > > >
> > > > > Service Dependencies; WIN32:the RPC server is unavailable.
> > > > >
> > > > > I check the RPC server service and it is started but when I click on
> > > > > properties I receive the same error for dependencies; WIN32: the RPC server
> > > > > is unavailalbe.
> > > > >
> > > > > I check the network conections and terminal services are binded to all
> > > > > availalbe NIC cards.
First  |  Prev  | 
Pages: 1 2
Prev: Roaming Profiles v Terminal Server Profiles
Next: Win32_SessionDirectorySession - DisconnectTime