No user can login after Win2k SP3/SP4 installation - Posting for 4th time

[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

-----Original Message-----
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

.

..

 

[Matthew Harris [MVP]]

Ok...if you did a netstat and port 3389 isn't listening,
then I would try deleting the rdp-tcp connection in your
terminal services configuration and then recreating it.

Then run netstat again to make sure it is listening.

And FYI...saying stuff like, "posting for the 4th time"
isn't a very good motivational prompt to get people to
reply to your topic. All the people who post into this
newsgroup are volunteers only

-M

 

[Saq]

I have already recreated rdp-tcp connection but it did not
work.

FYI- I know everyone is volunteer here but no MVP had
answer to this problem as I have posted it for the 4th
time. You already have given me this option but it did not
work. The wordings " posting for th 4th time" is for
reference purposes only for you.

I hope you can understand.

Saq

 

[Matthew Harris [MVP]]

So what happened when you recreated the rdp-tcp session?

Have you tried removing terminal services and
reinstalling? What happens if you bring up the
tsadmin.exe utility? What does it say about the rdp-tcp
listener?

If this doesn't work, then you might need to remove all
terminal services registry entries and then reinstall (not
to mention, you should have the latest service pack
installed).

-M

-----Original Message-----
I have already recreated rdp-tcp connection but it did not
work.

FYI- I know everyone is volunteer here but no MVP had
answer to this problem as I have posted it for the 4th
time. You already have given me this option but it did not
work. The wordings " posting for th 4th time" is for
reference purposes only for you.

I hope you can understand.

The term MVP only means that the person has show exemplary
knowledge in a certain field. MVPs are not hired or paid
by Microsoft. It does NOT mean that they need to answer
your question even if you have chosen to post to this
newsgroup 4 times. If a person doesn't reply to your post
it either means they didn't understand your post, don't
know the solution, or didn't want to answer your post at
that time.

-M

 

[Guest]

Hope this helps!

BELOW is a list of items that should be eliminated as a
possible cause for trouble.

Are the client machines "joined to the domain" (if there
is one),
sounds like you may want to search using "persistent
connection" as part of your string.

Look at your performance monitoring stats to see what is
happening on Terminal Services.
http://support.microsoft.com/default.aspx?scid=kb;en-
us;186536&Product=termsvr

Slow Network Performance with Terminal Services
http://support.microsoft.com/default.aspx?scid=kb;en-
us;191370&Product=termsvr

Home Directories for Terminal Svcs?
http://support.microsoft.com/default.aspx?scid=kb;en-
us;186521&Product=termsvr

http://support.microsoft.com/default.aspx?scid=kb;en-
us;186631&Product=termsvr

Active Directory and Schema Trouble?

Windows 2000 Service Pack 3Link
http://www.microsoft.com/windows2000/downloads/servicepacks
/sp3/default.asp


Are their multiple sessions listed on the server as being
in use but no actual user
connected or data being transmitted or files open?
Terminal Services Connection configuration
What is the setting of the SESSIONS TAB for Active
Session Limit
and Idle Session Limit? (both)

Unsuccessful logins in Logs?

Any system logs in event viewer with any of these Error
numbers?
http://www.microsoft.com/windows2000/docs/tslicensing.doc

Error 1000 - "Unable to acquire a license for user '%1',
domain '%2'."
Error 1003 - The terminal service client '%1' has provided
an invalid license.
Error 1004 - The terminal server cannot issue a client
license.
Error 1007 - Unable to log in the Internet user as
TSInternetUser. If the problem is not corrected
Error 1008 - The terminal services licensing grace period
has expired and the service has not
Error 1009 - The terminal services licensing grace period
is about to expire on %1 and the service
Error 1010 - The terminal services could not locate a
license server.
Error 1011 - The terminal services client %1 has been
disconnected because its temporary license has expired

 

[Guest]

I am jumping on your post about TS not working. I am using W2003 and we have some strange errors...

I can login to my TS no problem. As any authenticated user as well. But when the user tries to login from their desktop at home or laptop, they receive a license error from the Server. I think it has to do with the fact we replaced the TS Server shortly after it was introduced. I went into EVentid.net and found a post where I should delete the MSlicensing registry key. I did so but I am still out of luck. Any ideas?

Thanks, kevin

 

[Cláudio Rodrigues]

Do you have a licensing server up and running and activated?

--
Cláudio Rodrigues

Microsoft MVP
Windows Technologies - Terminal Services
http://www.terminal-services.net

I am jumping on your post about TS not working. I am using W2003 and we have some strange errors...

I can login to my TS no problem. As any authenticated user as well. But

when the user tries to login from their desktop at home or laptop, they
receive a license error from the Server. I think it has to do with the fact
we replaced the TS Server shortly after it was introduced. I went into
EVentid.net and found a post where I should delete the MSlicensing registry
key. I did so but I am still out of luck. Any ideas?