No user can connect to Terminal server after installing Win2kSP3

S

Saq

Hi,

I have already posted this question two times before but
no body helped me. I have One Windows 2000 Server with
Terminal Server. Windows 2000 has Service Pack 2. All
remote users use Internet / DSL to connect to this server.

When I install Service pack 3 in Windows 2000, no user can
connect to the server. I checked the port (3389) is opened
(no change). I checked that the terminal server service is
up and running. I recreated the RDP client session again
but it did not work too.

Please let me know what do i do in this condition.

Thanks in advance
Saq
 
M

Matthew Harris [MVP]

After you install SP3, can you telnet to port 3389 on the
server? Can you ping the server? Are there any eventlog
entries?

-M
 
S

Saq

yes, I am able to telnet the port 3389 and I can ping the
server too. But there is not entry in eventlog.

I also tried to see that is it listening the port but it
seams to me not listening on that port.

Saq
 
M

Matthew Harris [MVP]

That doesn't make sense. If you can telnet to port 3389
then the port should be listening. if you do a netstat -
an, did you see anything on port 3389?

When you telnetted to port 3389, did you do something like:

telnet <ip_address> 3389

-M
 
S

saq

Yes I did telnet IP address 3389 and responded because I
have port 3389 opened for it on the my DSL router. But
when I am trying to netstat server it does not reply to
this port i.e not listening.

My question is that If it is not listeneing what do I need
to do? I have already checked the registry keys in win2k
they have same port # 3389.

Hopefully you will understand and help me in this
condition.

Thanks
Saq
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top