troubleshooting Question

Why are incorrect server names showing up for User Sessions in the Shared Folders Snap-in?

Avatar of Spike99
Spike99Flag for United States of America asked on
Windows Server 2003Microsoft Legacy OSMicrosoft Server OS
7 Comments2 Solutions2298 ViewsLast Modified:
We have a fairly large server farm with nearly 100 terminal servers, 2 or 3 domain controllers, and about 10 file servers.  Since many of our customers are on terminal server load-balanced clusters, it can sometimes be challenging to figure out which terminal server they are on.  So, we use the Shared Folders snap-in in the computer management console for their file server to see which terminal server their session is on.

The problem is:  the server name that shows up in this list of user Shared Folder sessions is just wrong.  The server names that show up for some users make it appear they have sessions on servers they don't have rights to log on to.  Other server names that show up are old servers that are no longer in prodcution.  The incorrect server names are consistent:  Server A always shows up as Server B in the Shared Folders Sessions list.

Where does the MMC Mgt. Console or Shared Folders snap-in get the names for the servers?  I checked DNS & WINS: the old servers no longer have entries.  Obviously, the production servers do have entries, but I don't understand how a user on Server A would appear to have a session on Server B in the Shared Folders snap-in even though that user couldn't possibly be logged on to Server B.  Also, why does a user on Server C appear to have a session on decommissioned Server D, which doesn't even exist anymore (because it has either been moth-balled or reimaged/renamed using our new naming conventions).

Also, the machine accounts for the old servers were removed from active directory.  Some IPs have of decomm'ed server have been re-used, but one of the File Servers in question was put into production AFTER those old servers were re-imaged & the IPs re-used for other servers, so those particular file servers should have no knowledge of terminal servers that went out of prodcution before they went into production themselves.

Thank you in advance for your help,

Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 2 Answers and 7 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 2 Answers and 7 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros