General discussion

Locked

WINPOP - Tracing the Source

By marshall ·
A student has logged onto our Win NT 4.0 SP 4 system, under a generic logon, and sent inappropriate messages (via Winpop) to our server (PDC and BDC). The client is a Win 98 system. A check of the computer lab reveals that 3 computers were logged on under that generic name. Is there anyway to trace the message back to a specific computer ? Either at the client end, or the server end? Are there any files that might be created (on the client side)that would have the text of the message embedded somewhere?

Any comments/suggestions appreciated.

Marshall

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

WINPOP - Tracing the Source

by dtiongco In reply to WINPOP - Tracing the Sour ...

I would try to check the User Manager for Domain /Policies /Audit. See if Successful log in is check. If it is, go to Event Viewer under Security, you will see the time, user, and computer name of the users who successfully log in.

If the Successful log in is not check, put a check on it. This will start logging in both unsuccessful and successful log ins.

Collapse -

WINPOP - Tracing the Source

by marshall In reply to WINPOP - Tracing the Sour ...

The question was auto-closed by TechRepublic

Collapse -

WINPOP - Tracing the Source

by Gary Sharp In reply to WINPOP - Tracing the Sour ...

Theres a small chance that the full header of the message may have the dns name of the PC that sent it.

I don't knoe winPop at all, but does it not have logs that give the source name and ip address for the originator?

Also, you may consider disabling pop access for your generic logons (bolt that stable door!

cheers

g

Collapse -

WINPOP - Tracing the Source

by marshall In reply to WINPOP - Tracing the Sour ...

The question was auto-closed by TechRepublic

Collapse -

WINPOP - Tracing the Source

by marshall In reply to WINPOP - Tracing the Sour ...

This question was auto closed due to inactivity

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums