SBServer and TServer stopped talking

I know I've screwed this up but I need help pls.

This morning we couldn't get our Terminal Server to talk to the LAN.
It would "see" all the devices, including the SBServer, but would get
no further.....


After a lot of resetting, re-routing, checking DHCP, DNS, etc, etc I
finally tracked it down to a flakey LAN cable!

However, during my fumbling arround I removed the server from SBS's
list of Server Computers and the used the Wizard to add it back.

It all looks fine, except SBServer doesn't seem to be recognising the
this server as a Terminal Server.

I've clutched at straws and re-reun the Remote Connection Wizard, and
also re-started both systems, but it still doesn't appear on the list
of servers you can connect to.

If I look at it in My Netwrok Places, it shows up but as soon as I
click on it I get:
"\\name is not accessible. You might not have permission to use this
network resource. Contact the admininistrator.......
The trust relationship between this workstation and the primary domain
failed"

I'm sure something I've done has broke it. Can anyone help me fix it?

TIA,

JohnK

Al
Thu Jul 10 07:19:01 PDT 2008

Did you disjoin the TS from the domain (at the TS console)? You'll need to
do that to regenerate the SID. To do it set the TS to workgroup and reboot
it, then redo it's account on SBS and rerun connectcomputer. Careful, this
will affect any domain profiles on your TS.

--
Allan Williams



"John F Kappler" <john@pceffect.co.uk> wrote in message
news:nf4c74hbe04ghju4kelaianeh4lhptr15p@4ax.com...
>I know I've screwed this up but I need help pls.
>
> This morning we couldn't get our Terminal Server to talk to the LAN.
> It would "see" all the devices, including the SBServer, but would get
> no further.....
>
>
> After a lot of resetting, re-routing, checking DHCP, DNS, etc, etc I
> finally tracked it down to a flakey LAN cable!
>
> However, during my fumbling arround I removed the server from SBS's
> list of Server Computers and the used the Wizard to add it back.
>
> It all looks fine, except SBServer doesn't seem to be recognising the
> this server as a Terminal Server.
>
> I've clutched at straws and re-reun the Remote Connection Wizard, and
> also re-started both systems, but it still doesn't appear on the list
> of servers you can connect to.
>
> If I look at it in My Netwrok Places, it shows up but as soon as I
> click on it I get:
> "\\name is not accessible. You might not have permission to use this
> network resource. Contact the admininistrator.......
> The trust relationship between this workstation and the primary domain
> failed"
>
> I'm sure something I've done has broke it. Can anyone help me fix it?
>
> TIA,
>
> JohnK

John
Thu Jul 10 07:24:06 PDT 2008

Another clue:

Just logged out of the TS and attempted to re-login (as Admnistrator)
on the domain. Now get error messge:
"Windows cannot connect to the domain, either because the domain
controller is down or otherwise unavailable, or because your computer
account was not found. Please try again later. If this message
continues to appear, contact your system admin........."

Domain is definitely there with other users logged in and I can log-in
to the SBServer as Administrator......

It sounds like the domain controller is not talking to the Terminal
Server..........



On Thu, 10 Jul 2008 14:50:30 +0100, John F Kappler
<john@pceffect.co.uk> wrote:

>I know I've screwed this up but I need help pls.
>
>This morning we couldn't get our Terminal Server to talk to the LAN.
>It would "see" all the devices, including the SBServer, but would get
>no further.....
>
>
>After a lot of resetting, re-routing, checking DHCP, DNS, etc, etc I
>finally tracked it down to a flakey LAN cable!
>
>However, during my fumbling arround I removed the server from SBS's
>list of Server Computers and the used the Wizard to add it back.
>
>It all looks fine, except SBServer doesn't seem to be recognising the
>this server as a Terminal Server.
>
>I've clutched at straws and re-reun the Remote Connection Wizard, and
>also re-started both systems, but it still doesn't appear on the list
>of servers you can connect to.
>
>If I look at it in My Netwrok Places, it shows up but as soon as I
>click on it I get:
>"\\name is not accessible. You might not have permission to use this
>network resource. Contact the admininistrator.......
>The trust relationship between this workstation and the primary domain
>failed"
>
>I'm sure something I've done has broke it. Can anyone help me fix it?
>
>TIA,
>
>JohnK

John
Thu Jul 10 07:42:58 PDT 2008

Saved my bacon Al!

Thanks for that - it all seems okay now.

Phew - I'd booked a days leave tomorrow and didn't want to leave my
customer without remote access!

Thnx again,

JohnK

Al
Thu Jul 10 08:00:08 PDT 2008

No problem.

As FSJ used to say :-( Peace out.

--
Allan Williams



"John F Kappler" <john@pceffect.co.uk> wrote in message
news:ts7c74lhk7s5pv57jp9iboe8as7t1ut3ij@4ax.com...
> Saved my bacon Al!
>
> Thanks for that - it all seems okay now.
>
> Phew - I'd booked a days leave tomorrow and didn't want to leave my
> customer without remote access!
>
> Thnx again,
>
> JohnK