Terminal Services in Windows 2000

ASKER

I'm sitting at it. Just tried. Yes.

BigC666

i don't understand, your setting at the server and trying to get into it. are you trying to ts to a workstation or what. i ment can you ping the server from the workstation that you'r trying to connect to the server from

ASKER

Starting off, I just want to be able to do a loopback test. I have tried from multiple workstations all of which I can ping and none of them will connect.

BigC666

man, i don't think that you can do a loop back test, however if on the server you have set up terminal services and on the workstations you've setup the clients, it's pretty straight forward, i've never experienced problems.

sorry maby someone else can help.

ASKER

I know, neither have I.

On Windows server 2003 I know that you can do a loop back. Actually, when using Citrix Metaframe over TS, you have to if you want to be able to control things a certain way.

Perhaps loopback isn't possible in 2000. But I still can't connect remotely -- even though the workstation and server are on the same subnet and not going through any firewall appliance. It's really wierd. First time I've ever had this issue too.

Any one else help?

ASKER CERTIFIED SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

That should be services.msc (rubbish typist.....)

ASKER

I did check to see that the service is running. I checked the administrator account to be certain that it was enabled for remote access under the terminal services, remote control and dial-in tabs of the account. Checking error log now.....

ASKER

... I looked in the event log and there is nothing in any of the entries that appears to have anything to do with the terminal services. The one strange thing is that there is absolutely nothing at all in the security log. I'm trying to figure out how to turn that loggin on right now so that I can see if anything wierd shows up there. Do you know where to turn that specific loggin on in W2K?

SOLUTION

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER

Where is the tcp/ip advanced config located?

open services.msc and confirm that the Terminal Server service is running, and all dependencies are running. Also, do you have IIS installed and running on this box?

ASKER

Opened services.msc. Terminal server service is running. When looking at dependencies it says that there are none. IIS is running on this machine.

Hi
Nothing that looks like any of these then?
Error Messages Generated When Logging on with Terminal Services Client
http://support.microsoft.com/?kbid=246109
And which service pack are you on?
What erorrs do you have some of these might not look related bu they could be...

1. Can you connect to the default website from an external box?

2. TCP/IP advanced config -> Open network connections, Local Area Connection.
First, in the Advanced tab here, make sure you have no windows firewall running.

Go back to the General tab, click on TCP/IP and click properties
there will be an advanced button near the bottom of the properties pane.
Make sure that there is no filtering enabled.

Also, does this machine have a NAT IP or a real IP? Paste the first 2 octets of the IP for me.

ASKER

There is no filtering happening in TCP/IP. The IP address is 192.168.0.40.

ASKER

Debsyl99,

none of the info in that web link was what I am seeing. . . .

1.) Are the machines that you are trying to connect from in the same subnet? (192.168.0.xx)

2.) Does the server have two NICs (Network Interface Cards) If so, one may be external IP and one may be internal.

3.) Can you view the webpage that the IIS is serving from another box ( type the IP in a browser). If no website is set up, you should see a default page.

4.) Forget about loopback. Try to connect from a machine in the same subnet.

Ok - Don't want to get involved in confusing you with multiple suggestions here - so let's see what transpires.......

ASKER

Tried all the above. All but connecting to the server work. Any other thoughts? All on same subnet. Communicate with server from the workstation okay for regular traffic; tcpip goes just fine; not two nics; iis is accessible from all machines on the intranet. Still no dice. I'm really stumped.

I must admit this is odd - usually terminal services in remote admin mode goes in like a charm.......
You are on SP4?
You can ping the server ok by name and ip from a workstation - any dns errors on the server at all?

ASKER

All okay and current on service packs (all except the last two minor ones that came out for IE issues). No dns errors that I can see. This has me stumped too.