log file storing ip address accessing w2k server


I have a w2k machine open out for access to the internet. Is there a log file in win2000 server keeping track of machine ip address accessing my server. If no, can anyone tell me how can i go about doing that.
kyh74Asked:
Who is Participating?
 
dew_associatesConnect With a Mentor Commented:
Without some form of Internet service running, there's no way to log the users hitting the server. IIS would be your cheapest bet.
0
 
PortangCommented:
For FTP and HTTP, see:

\WINNT\System32\LogFiles\......
0
 
kyh74Author Commented:
Im running a dedicated game server(counter strike)which doesnt have logfile that record ip address. Looks like i need to write my own script to track ip address.
0
Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

 
dew_associatesCommented:
KY, you can't log addresses in any of the MS server products except for IIS and Exchange 2000 Server. Anything else requires 3rd party software and/or a firewall product that enables IP logging.

Dennis
0
 
kyh74Author Commented:
Hi dew_associates
any 3rd party software to recommend.
0
 
dew_associatesCommented:
Sure, just give me an idea of the size of the network so I can find something reasonable, if not free.
0
 
kyh74Author Commented:
sorry for not replying, i just came back from a trip.
anyway what do u mean by size of the network. I only have one game machine connected to my ISP.
0
 
dew_associatesCommented:
Oh okay. Then is it a server and if yes, is IIS installed?
0
 
kyh74Author Commented:
no other services is running. Only dedicated to game server only.
0
 
dew_associatesCommented:
Or a good firewall (you good make one out of a junk machine) that you could use as a proxy/firewall.
0
 
dew_associatesCommented:
kyh74???
0
 
dew_associatesCommented:
kyh74???
0
 
dew_associatesCommented:
You could just set up auditing on your machines.  Launch the User Manager on your workstation(s), select Policies | Audit | Audit These Events and check Success for the Logon and Logoff events.

Checking Failure for the same events will give you an idea if people are trying to login where they're not supposed to.

BTW, don't go "audit-happy," by enabling auditing for all the listed events, as auditing can add quite a bit of system overhead, especially in the case of the File and Object Access and Process Tracking events.
0
 
dew_associatesCommented:
Thanks for the "B"~!
0
All Courses

From novice to tech pro — start learning today.