You know, that's not a bad thought. Use a tool such as the WAN killer in the Solarwinds package (or any other traffic generator). Start it up and see which port on the switchs lights up. Shouldn't take more than a minute or two to narrow it down.
Mark ------------------------------------------------- Two rules to success in life: 1. Never tell people everything you know. -----Original Message----- From: Matthew W. Ross [mailto:[email protected]] Sent: Tuesday, March 31, 2009 4:10 PM To: NT System Admin Issues Subject: Re: locating one machine Horribly old-school method of finding a computer on your network. I don't suggest you do this during work hours: Ping the box. Keep the ping running (windows command of 'ping -t ip.add.re.ss' Walk up to your switches, and start unplugging connections. After each unplug, see if the ping is continuing. If it is, plug the port back in, it's not coming from there. If it isn't, Follow that network wire to the next switch/hub or to the box itself. It's slow, painful, and extremely painful for people/servers that don't want to be unplugged, but it works. --Matt Ross Ephrata School District ----- Original Message ----- From: Ben Scott [mailto:[email protected]] To: NT System Admin Issues [mailto:[email protected]] Sent: Tue, 31 Mar 2009 12:57:41 -0700 Subject: Re: locating one machine > On Tue, Mar 31, 2009 at 3:44 PM, John Aldrich > <[email protected]> wrote: > > Yeah... Well, I already tried a domain-admin group member... my alternate > > login. :-) Funny thing... it wouldn't let me supply a username when trying > > to browse to the admin shares.... just a password.. Hmm... > > Hmmm.... I thought that only occurred when talking to domain > members, the idea being that since you're already logged in to the > domain you can't give credentials again. But I could be wrong on > that. > > Okay, one more idea: > > Start ping'ing the mystery machine. > > Start unplugging patch cables from the switch one at a time. When > the ping stops, you know the machine is downstream from that jack. > > This will tend to disrupt network connectivity, of course. So do it > tomorrow, and blame it on the Conficker worm. ;-) > > -- Ben > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ Please consider the environment before printing this email. ________________________________ CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipients(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
