Prev: Roaming Profiles v Terminal Server Profiles
Next: Win32_SessionDirectorySession - DisconnectTime
From: Nancy Villa on 31 Aug 2006 10:06
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 10:44
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: Nancy Villa on 31 Aug 2006 11:23
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: Nancy Villa on 31 Aug 2006 11:25
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 12:04
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.
 |  Next  |  Last
Pages: 1 2
Prev: Roaming Profiles v Terminal Server Profiles
Next: Win32_SessionDirectorySession - DisconnectTime