![]() To answer Grawity, I would say I wouldn't either. And please sign your posts with four tildes: ~~~~ - grawity 13:13, 25 April 2008 (UTC) Reply I think UltraVNC deserves a look. Or you can use a trojan horse such as SubSeven - they work well for monitoring. Anyway, for Windows, you could try radmin, or VNC. R.Rajesh Kumar -Preceding unsigned comment added by 122.164.51.157 ( talk) 12:39, 25 April 2008 (UTC) Reply I won't start talking about rights to privacy, but if (an example) the administrator at my workplace did this kind of monitoring, I certainly wouldn't work there. Main thing The person Don't to Know if i watching my system from Remote place. ![]() Somthing so i want to watch the system at any other system is connected in lan. I need Help from You pepole.Please clear it.Mointering the Remote system through lanĬonnection is Possible? and if it is Possible how is it? please explain me.īecause I am Adminstrator in my company.In My company many of them Open the Server And Doing k a i n a w ™ 16:15, 25 April 2008 (UTC) Reply Moniter the remote system Those routers/switches tend to have names which identify their general location. It will break through the "it is somewhere on this continent" range and show you which routers/switches were used to get to the IP address. JSBillings 13:14, 25 April 2008 (UTC) Reply While whois is helpful for finding out which company owns an IP address, it is worthless for finding out the location of people using large ISPs. ![]() The tutorial you list must be somewhat dated to have such a simplistic view of mail systems. Most ISPs nowadays bounce the message around through primary MX systems, some antivirus/antispam systems and finally to mail-store systems. JSBillings 13:11, 25 April 2008 (UTC) Reply Also, the topmost Received: header isn't always going to be the point where your ISP accepted the connection from the sender's ISP. Unfortunately, as with services like Google Mail, who uses a private network internally, it won't be too helpful. You need to look at the Received: header where the ISP accepts the connection from the sender, which might be the second-to-last Received: header. Given what you say above about the RFC1918 address space, is there any way I can identify the sender? - Bluegrouper ( talk) 12:34, 25 April 2008 (UTC) Reply That page you gave is somewhat correct, but in your case, the sender's IP isn't actually helpful, because it's on a private network. It also says (point 3, a little higher) that the topmost Received: header (which I'm assuming is the one JSBillings describes as "the IP address of the system logged by your own ISP" contains the IP address of the sender's email server, not the IP address of the sender himself. This tutorial suggests (point 5, three-quarters of the way down) that the sender's actual IP address will always be the in the bottommost Received: header. Yes, I know email can contain forged headers, and no it's not spam I'm trying to trace. Spoon! ( talk) 12:26, 25 April 2008 (UTC) Reply Thanks for the replies. Perhaps you should look at the next IP in the trail. It is probably a step in the routing of your email that involved one server sending to another mail server internally on an internal network. JSBillings 11:53, 25 April 2008 (UTC) Reply We have an article on private networks like 10.*.*.*. Anything else can and will be added by the sender, and is possibly forged. You want to look at the IP address of the system logged by your own ISP, because that's really the only reliable Received: header (given that you trust your own ISP). Atlant ( talk) 11:36, 25 April 2008 (UTC) Reply Don't bother trying to track down a 10.*.*.* IP address, that's an IP in the RFC1918 address space, used on private networks (such as the user's home LAN or the sender's ISP's internal network). Astronaut ( talk) 10:53, 25 April 2008 (UTC) Reply You understand that E-mail can contain forged headers, right? See E-mail and E-mail authentication for more information. Remember though, if you are trying to track down someone who is sending you spam, they are unlikely to respond to your attempts to get them to stop and are more likely to add you to their "suckers list" instead. I usually try ARIN, then the links to other the continental Whois services at the foot of that page, and finally Sam Spade. Have you tried all of them? Also, so there are many "Whois" servers. Can the email header tell me any more? - Bluegrouper ( talk) 08:30, 25 April 2008 (UTC) Reply The email headers usually feature lots of different IP addresses. I was expecting more from WHOIS, like a domain name or something. I know how to get the sender's IP address through email headers, but when I run a WHOIS search on the IP address (which begins 10.*), all it tells me is that the address is owned by the Internet Assigned Numbers Authority. I am trying to trace the sender of an email.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |