Re: internal IP exposure
From: Ed (Ed_at_discussions.microsoft.com)
Date: 03/30/05
- Next message: Mark Randall: "Re: internal IP exposure"
- Previous message: Jeff Cochran: "Re: How to Map root level folders in Windows"
- In reply to: N. Miller: "Re: internal IP exposure"
- Next in thread: Mark Randall: "Re: internal IP exposure"
- Reply: Mark Randall: "Re: internal IP exposure"
- Reply: Phillip Windell: "Re: internal IP exposure"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 29 Mar 2005 16:43:01 -0800
I do have a linksys router. I didn't want to know how powerful your network
is. I am sure my fbi friend could get in ,but anyways that's for the help.
"N. Miller" wrote:
> In article <23257EC6-886C-44FE-9B9D-4DE00AA1CD92@microsoft.com>, =?Utf-8?B?
> RWQ=?= says...
>
> > I recently ran an online security check and there server told me my internal
> > IP is exposed. I am wondering how do i fix it.
>
> If you are speaking of "AuditMyPC", they use Java (not JavaScript) to fetch
> your internal IP address locally. You can try their site again, with Java
> disabled, and you should see that they can't pull your IP address. They may
> try other stunts with JavaScript, so disabling both while you are on their
> site should fix things.
>
> Having your internal IP address is useless. If you haven't changed from the
> factory default, yours is one of just millions of computers in the world
> with the same IP address. The BGP routers, which move packets between
> networks, do not recognize any of the addresses in several ranges, of which
> those identified in RFC 1918 for internal use are some. Even IP addresses
> with should be routeable won't be if they are not announced in BGP routing
> by their owners. Without the ability to route packets from your ISP
> (12.215.157.139; belongs to Mediacom Communications Corp.) to mine
> (64.161.31.129; belongs to SBC), knowing that my computer is at
> 192.168.102.100 is of no use to you. Your attempt to ping my IP address from
> your end will fail, even for a computer with a direct Internet connection.
> If you could successfully ping 192.168.102.100, either you have set your LAN
> IP address the same as mine, and are seeing one of your computers, or you
> have associated to my LAN with a WAP; a pretty good trick because my LAN is
> 100% wired, no WAP anywhere, and the taps are all within the bounds of my
> premises. You would need standard house burglary tools to reach my LAN! ;)
>
> --
> Norman
> ~Win dain a lotica, En vai tu ri, Si lo ta
> ~Fin dein a loluca, En dragu a sei lain
> ~Vi fa-ru les shutai am, En riga-lint
>
- Next message: Mark Randall: "Re: internal IP exposure"
- Previous message: Jeff Cochran: "Re: How to Map root level folders in Windows"
- In reply to: N. Miller: "Re: internal IP exposure"
- Next in thread: Mark Randall: "Re: internal IP exposure"
- Reply: Mark Randall: "Re: internal IP exposure"
- Reply: Phillip Windell: "Re: internal IP exposure"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
