Remote Windows 2000 Server from Windows XP Home 1

[nacfiadmin]

I have set up a file server using Windows 2000 Server and want to use Windows XP Home as client to run Windows 2000 Server Remotely. How is the best way to do this.

 

[flypoo]

VPN to Win2000, then Remote Desktop?

That's what I do.

 

[Claudek]

You could also install Terminal Services on the Windows 2000 server and then use the Remote Desktop Client on XP Home to access it as another option to the one above. I use both methods currently.





Claudius (What certifications??)

http://www.iteq.com.au

 

[nacfiadmin]

I have set up Terminal Services on the W2k Server but it I am doing something wrong. In Terminal Services Manager the message says "You could not be authenticated on this server." what am I doing wrong. Something is set up wrong in the Terminal Services Configuration. What Should the settings be.
I am running Terminal Services Client on the WinXP computer.
Thanks flypoo and Claudek for the support.

 

[nsanto17]

Did you install it as application mode or administrator mode?

 

[TidyTrax]

When are you getting that msg, that doesnt sound like a Term Services login error, more like a connection error.

 

[TidyTrax]

Is your term server behind a firewall???

 

[JimWells]

When you say "Terminal Services Manager" says that you can't be authenticated - do you mean when you try to manage the terminal server via the tool in "Administrative Tools"?

What user account are you logged in with when you do this? Domain/Local User? Administrator?

 

[nacfiadmin]

nsanto17
I an running it in administrater mode.

TidyTrix
It may be a connection error. I have two network cards in the server and one is setup for the remote server with a static address and the WinXP is setup for DHCP. This could be the problem, but the client on this computer is setup with this address. The Terminal Services Manager is in the Administrative Tools and I am logged on as Administrator.
I am behind a Linksys firewall. Do you think the firewall could be the problem? I think the problem is in the W2k Server do to the error I am getting from Terminal Services Manager. By the way I am not using a domain name, could that make a differance.



Thanks for your support I will continue to change settings until I get it right.

 

[JimWells]

When you say you have two network cards in the server -- can you tell us more about your network setup?

Can you see and manage the server you're trying to connect to in Terminal Services Manager? Is the "Terminal Services" service started on that server?

 

[nacfiadmin]

JimWells
What im am trying to do is use the Windows XP Home to be able to change settings and deal with any problems with user groups and users. This server is a file server and is not connected to the internet. The 1st network card is static and serves pier to pier to the workstations. The 2nd card is static to connect to the Windows XP Home computer. All workstations use DHCP using a Linksys Router to conect to the internet including the Windows XP Home that I am trying to set up. All workstations are using AVG 7.0 Antivirus. Terminal Services Manager does not show anything but a message "You could not be authenticated on this server. Terminal Services Manager is running on Windows 2000 Server and Terminal Services Client is running on the Windows XP computer. Also we are not using Domain, we are using Workgroup. We have groups that have the users set. The old Windows 2000 Server is setup the same as the new Windows 2000 Server and this system has been very stable for years, We had a spike that fried one Motherboard, a External Hard Drive, transformer and the Motherboard on the old Windows 2000 Server, it still runs but runs very slow, all of these are on a Battery Backup even the Cat 5 cable. The New Windows 2000 Server has two SATA hard drive on Raid 1 and a ATA Hard Drive for backup, it also has a USB2 External Hard Drive for backup. We use Robocopy to back up all files.


Thanks for your support.

 

[JimWells]

OK - this makes more sense.

When you say "the second card is static to connect to XP Home" - does that mean that the XP Home computer also has a second card?

If the Windows XP Home computer is on the same physical network as the rest of the workstations, why don't you just connect to the server without the use of the the second NIC?

All of your workstations can see the new 2000 server, right? If that's the case, you can connect via Terminal Services to that server over your regular network. There's no advantage on a normal LAN to using a direct connection between the two computers.

 

[nacfiadmin]

JimWells
Both computers have two network cards.
All computers are on the same network including the Windows XP Home computer.
Will using the two computers for remote slow the network down with only one network card.
All computers can see the new 2000 server and connect to it. If I am understanding you, you mean to use terminal services on both computers. I am having a error in Event Vewer about a conflict over two Addresses in NetBIOS Local Name Table. Please tell me the best way to do this, what programs to use on both computers to Remote Administer from the XP computer. The Server Computer is very hard to get to, so I want to be able to change the Users and Groups remotely. I now how to build a computer and repair it. This Network Administrator job was added to my Project Manager job when an employee left, but I am learning.


Thanks for your help in this matter

 

[JimWells]

If all you want to do is add local users and groups to the server, you don't have to connect remotely via system services. On any computer on the same network, right-click My Computer, Click Manage. Right-click on the computer name and choose "Connect to another computer." Choose the server, and you can manage probably all of what you need through various snap-ins.

I'm curious why you say terminal services slows the network down? You must have a very old network or one violating some hub principles if this is the case, because terminal services is designed to operate over slow links when necessary.

I've not connected two computers together that were already on the same network - that could very well have implications for NetBIOS. You might try reposting this question in a networking forum as "Terminal Services Admin mode over a crossover cable.

 

[TidyTrax]

Just so i understand a bit better - you have a pier-2-pier network with X Workstations, The XP Home machine and the Term Services Server. Both the XP home machine and the TS Server have two network cards, one for the pier-to-pier network and the other for the network between the XP Home and the TS Server. I think JimWells makes a good point in asking to what purpose this serves?!?!!? Are you trying to make Term Services only assessible from the XP machine perhaps?!?!? Also are the two NIC's in the XP and Server on different subnets?!?!?

Its seems to me that the extra NIC's in the XP and Server are really redundant and you could easily achieve the setup you want by removing those and just connecting the XP Machine via Term Serv to the Server via the first two NIC's. This will almost certainly solve the NetBIOS error you are getting also.