Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In a Windows Server 2003 network with domain, is it possible to obtain the IP address or PC name only with username? Using Windows cmd.exe commands from any client on the network.

share|improve this question

closed as not a real question by Brent Pabst, HopelessN00b, rnxrx, Ward, Michael Hampton Sep 30 '12 at 23:10

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Its not clear what you want to do other than get an IP address, can you detail your question more please. – Brent Pabst Sep 26 '12 at 15:59
Are you a domain administrator? if no then the answer is no, if yes you need MUCH more training and until you get that let someone else do your job. – Chopper3 Sep 26 '12 at 16:01
@Chopper3 That seems like a particularly cruel thing to force on this "someone else" you make mention of. – HopelessN00b Sep 26 '12 at 16:02
up vote 4 down vote accepted

No, this is not possible as asked, primarily because user-accounts/usernames do not have IP addresses or PCs.

Users, on the other hand, often have have PCs, which may be assigned IP addresses, and if that's what you're trying to track, it is possible to track down the IP address of the PC that a given username logs into or accesses over the network.

However, this involves reading logs (start on the Domain Controller(s)), rather than expecting an arbitrary instance of cmd.exe on an arbitrary computer to automagically know what networked resources an arbitrary username is being used to authenticate against.

share|improve this answer
Nice answer. I agree with Chopper3's remark as well. I've been training junior admins lately... At least, they claim to be admins... – Tonny Sep 26 '12 at 16:08
Just to defend myself, I'm not a network admin, just an IT worker trying to access with remote desktop to a particular PC but didn't know its IP or name. Users at my office can't help me too much giving me that information. – Delmonte Sep 26 '12 at 16:12
@user316687 Your users can't 'Start' -> 'Run...' -> cmd -> ipconfig /all? – Aaron Copley Sep 26 '12 at 16:15
No, because doing "psloggedon \\pcname" instructs the psloggedon command to go to the specific PC specified by "\\pcname" and query for the username that is currently logged into it. A tool that did something like "psloggedon username" would have to scan the whole network since that user could be logged into any PC on the network. If your users have dedicated workstations, then you should have some way (database, spreadsheet, etc) of tracking the PC that was assigned to them and go off that to figure out which PC they are likely using. – August Sep 26 '12 at 16:59
@user316687 In addition to what August said above, get your SA(s)/network admin(s) to grant you access to the Domain Controller's security event logs, from which you can search for a given username to see what IP it's authing to the DCs from. You don't even need to log onto the DCs, you can use the Event Viewer on your PC to target a remote system's event logs. May motivate them to mention that this would enable you to handle more "user shit" without their help, and would result in you bothering them for logged information less. – HopelessN00b Sep 26 '12 at 17:08

Not the answer you're looking for? Browse other questions tagged or ask your own question.