Jump to content

Recommended Posts

Posted

Hi all,

I have 5 terminal servers in "workgroup" mode (not joined in a

domain), two was upgraded from win2000srv to win2003std.

The servers work correctly, but running tsadmin.exe on 4 of them while

trying to connect to the last one (it's one of the two upgraded) it

gives a strange error "Authentication error, impossible to

connect" (the message colud be a little different, I traslated it from

italian).

I get same error tring to connect from windowsXP client running "\

\ts_not_working\c$\windows\system32\tsadmin.exe" with the right

adminstrator credentials.

I'm logged as administrator (of course) and, as I wrote, it works

correctly on the other TS.

Tsadmin from the server with the issue to the other 4, all works fine.

I tried to compare a lot of settings (permission, policies etc), read

events logs, googled about it, but I wasn't able to find a solution

(even it seems other people had/have same issue).

 

TIA

 

G.F.

  • Replies 5
  • Created
  • Last Reply
Guest Soo Kuan Teo [MSFT]
Posted

Re: TSADMIN not working correctly

 

Say, ServerA is the machine you cannot connect remotely with tsadmin, which

is upgraded to Win2k3 from win2k server, is in workgroup.

To rule out any potential cached credential, delete all net use, delete all

store names with cmdkey.exe /delete:ServerA

Please make sure that the administrator account and its password you use to

run tsadmin is identical across all machines.

Can you use ServerA IP to connect with tsadmin.exe remotely?

Can you please try to disable ServerA firewall and try to use tsadmin to

connect again?

Can you ping ServerA remotely?

Can you remote desktop to ServerA remotely?

what do you get when you run the following in a cmd shell from a remote

machine?

qwinsta.exe /Server:ServerA

what do you get when you run the following in a cmd shell locally on

ServerA?

qwinsta.exe

what is the value of the following regkey on ServerA?

HKLM\System\CurrentControlSet\Control\Terminal Server\AllowRemoteRPC

 

Copying tsadmin.exe from server to XP is not supported. To run tsadmin.exe

on XP, you need to use win2k3 admin pack:

http://www.microsoft.com/downloads/details.aspx?FamilyID=c16ae515-c8f4-47ef-a1e4-a8dcbacff8e3&DisplayLang=en

 

Thanks

Soo Kuan

 

 

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

 

"GF" <giovanni.ferloni@gmail.com> wrote in message

news:061662e2-fae2-4250-94dd-51b066b6d461@79g2000hsk.googlegroups.com...

> Hi all,

> I have 5 terminal servers in "workgroup" mode (not joined in a

> domain), two was upgraded from win2000srv to win2003std.

> The servers work correctly, but running tsadmin.exe on 4 of them while

> trying to connect to the last one (it's one of the two upgraded) it

> gives a strange error "Authentication error, impossible to

> connect" (the message colud be a little different, I traslated it from

> italian).

> I get same error tring to connect from windowsXP client running "\

> \ts_not_working\c$\windows\system32\tsadmin.exe" with the right

> adminstrator credentials.

> I'm logged as administrator (of course) and, as I wrote, it works

> correctly on the other TS.

> Tsadmin from the server with the issue to the other 4, all works fine.

> I tried to compare a lot of settings (permission, policies etc), read

> events logs, googled about it, but I wasn't able to find a solution

> (even it seems other people had/have same issue).

>

> TIA

>

> G.F.

Posted

Re: TSADMIN not working correctly

 

> Say, ServerA is the machine you cannot connect remotely with tsadmin, which

> is upgraded to Win2k3 from win2k server, is in workgroup.

Right.

> To rule out any potential cached credential, delete all net use, delete all

> store names with cmdkey.exe /delete:ServerA

Done. (even net use -> empty list, cmdkey /list shows no credential

stored)

> Please make sure that the administrator account and its password you use to

> run tsadmin is identical across all machines.

Yes I'm sure

> Can you use ServerA IP to connect with tsadmin.exe remotely?

Ye works fine, I can admin all other TermServ

> Can you please try to disable ServerA firewall and try to use tsadmin to

> connect again?

Firewall is disabled

> Can you ping ServerA remotely?

> Can you remote desktop to ServerA remotely?

Yes, I can connect to ServerA both user & admins account correctly.

> what do you get when you run the following in a cmd shell from a remote

> machine?

> qwinsta.exe /Server:ServerA

> what do you get when you run the following in a cmd shell locally on

> ServerA?

> qwinsta.exe

Shows correctly active connections

Fired from another server works fine too (prints currently active

connections) (!!!)

> what is the value of the following regkey on ServerA?

> HKLM\System\CurrentControlSet\Control\Terminal Server\AllowRemoteRPC

Already tried to set it = 1 (this key was missing)

 

Thanks

GF

Posted

Re: TSADMIN not working correctly

 

I feel that something go wrong with gateways.

The servers have 2 nic configured with to different class: NIC #1

192.168.0.X NIC #2 192.168.1.X

 

IP Working servers

Server #1

NIC #1 192.168.0.1

NIC #2 192.168.1.1

 

Server #2

NIC #1 192.168.0.2

NIC #2 192.168.1.2

 

..

..

..

ad so on

 

Server #5 (not full working)

NIC #1 192.168.0.5

NIC #2 192.168.1.5

 

pings are ok on both ip class on all server

 

RDPing from Server #5 works fine on all IP of the remaining TS (eg.

192.128.0.1, 192.168.1.1, 192.168.0.2, 192.168.1.2 ecc)

 

RDPing from Servers #1, #2, #3, #4 vs TS #5 works only on 192.168.1.X

class; trying to connect on 192.168.0.5 gives connection errors.

 

Is this information useful?

Guest Soo Kuan Teo [MSFT]
Posted

Re: TSADMIN not working correctly

 

can you please share what is the ServerA setting on the

TScc.msc->RDP-Tcp->Network Adapter->Network Adapter?

 

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

 

"GF" <giovanni.ferloni@gmail.com> wrote in message

news:1d2bc5e6-184e-4028-bb6e-e293ca24ef09@m36g2000hse.googlegroups.com...

>I feel that something go wrong with gateways.

> The servers have 2 nic configured with to different class: NIC #1

> 192.168.0.X NIC #2 192.168.1.X

>

> IP Working servers

> Server #1

> NIC #1 192.168.0.1

> NIC #2 192.168.1.1

>

> Server #2

> NIC #1 192.168.0.2

> NIC #2 192.168.1.2

>

> .

> .

> .

> ad so on

>

> Server #5 (not full working)

> NIC #1 192.168.0.5

> NIC #2 192.168.1.5

>

> pings are ok on both ip class on all server

>

> RDPing from Server #5 works fine on all IP of the remaining TS (eg.

> 192.128.0.1, 192.168.1.1, 192.168.0.2, 192.168.1.2 ecc)

>

> RDPing from Servers #1, #2, #3, #4 vs TS #5 works only on 192.168.1.X

> class; trying to connect on 192.168.0.5 gives connection errors.

>

> Is this information useful?

Posted

Re: TSADMIN not working correctly

 

On Jul 30, 5:19 pm, "Soo Kuan Teo [MSFT]"

<sooku...@online.microsoft.com> wrote:

> can you please share what is the ServerA setting on the

> TScc.msc->RDP-Tcp->Network Adapter->Network Adapter?

>

 

"All network card avaible" (trad. from italian)

 

GF


×
×
  • Create New...