ghost computer in my network!

[celestina]

hello, everybody!

I took a new job and found 30+ computers in a network. One of those computers, however, can't be *found* physically. I don't know where it is located in the building, but I can see it in the network every day for the past month. It must be a co-worker, so I'm expecting colaboration.

We don't have a server running yet. Question: could I send a "message" to this computer, any kind of dialogue box with a plead "hey, please call Department such and such, etc)". No file is being shared.

I'm on a Windows 2000 here, I don't know the other computer's OS (of course). Any suggestion for such a situation?

[Siliconjunkie]

"net send computer name call 555-1212" will do it if it is running the messenger service. You could port scan it and get an idea of what it is, but that wont answer the where question.

Best thing to do is probably to work afterhours and start pinging and chasing cables and pulling plugs. Then you can find what drop it is off of. If the network is routed you can narrow it down some with a tracert.

Does it go away at night? Perhaps someone is bringing a laptop?

[Telexen]

I didn't think "net" worked with anything but XP?

[BobOmega]

net send works with anything nt based afaik it worked on nt4.0 boxes at my school. but not on the 9x. works on my 2k and xp

[Siliconjunkie]

NT, 2k and XP and there is an add on for 95/98 I believe.

[celestina]

Siliconjunkie: I know in which router this machine is. 24 probable culprits so far. The problem is that I'd have to sit in every computer to check its identification. Possible, of course, but if I can avoid this...

And yes, this person works on business hours. Unless he's hiding in the male's restroom... I haven't checked there, I admit.

I have an evil idea. I already know this machine's IP. I'll put the same IP in another machine in my office. That, I imagine, will cause some incompatibility problems. When my phone rings with the complaint "my internet is not working" I will have found my ghost computer. Do you think this might work?

I'm serious. Unless I find another solution, this one is starting to sound viable.

[PresterJohn]

>I know in which router this machine

if you know which router it is and if you have the router ports documented (to the floor/space locations), then you're set.

just "ping -t" the addy and start with port #1 and disconnect each patch cable. once you've identified which cable is the ghost link, then its just a matter of legwork.

[muno]

w9x had 'winpopup' which was gui for net send (was far better than the command line tool).

Yep, send a message to him asking for him to call you, and after that, unplug the cable that goes to his computer.
-M

[berkelyblue]

oh man you must have a very disorganized network. I think you should do a survey of all your computers, put down information like IP, location, computer type and what ever you deem important into a spreadsheet and then print a carbon copy handy just in case.

[originel]

berkely blue has a good idea there.

also i would try net send first and see if that produces anything.