[twsocket] Need Advice / Help on how to find the correct IP's
Mon, 12 Jun 2000 23:22:05 +0200
Please include the original question in future. As I remember you wanted to
know if you had a connection on witch interface it was or witch one was the
Wel if you can connect with addr '0.0.0.0' you have the ip of the server.
You can call LocalIpList to get list of all interface cards. Next step is to
set LocalAddr property to the first one and try to connect again. If it dont
work, then it's the wrong one, you can try the next, etc, and if connect is
ok then you have the interface witch is connected to internet.
If I'm completely wrong here pleas ask the original question again.
> -----Original Message-----
> From: firstname.lastname@example.org [mailto:email@example.com]On
> Behalf Of Ralf Buml
> Sent: maandag 12 juni 2000 19:43
> To: firstname.lastname@example.org
> Subject: RE: [twsocket] Need Advice / Help on how to find the correct
> Hi Wilfried!
> Thanx for your answer! :)
> It's ok... I knew the thing with the IP-Adresses already.
> But as your last paragraph says some users don't know
> which IP-Adresses are valid. (I was such a user some years
> ago, wondering why my Network never worked on TCP/IP :)))
> Is there no other way than checking these adresses?
> This way is much too unsecure for my needs and will be the
> last escape if any other way is possible...
> >Normally (if lan ip properly configured), the lan ip address should be a
> >private netwerk, and the internet ip address is a public one.
> Difference is
> >a private network is normally not routed. Private are:
> >class A (for very large networks):
> >10.0.0.0 / 8
> >class B (for large networks):
> >172.16.0.0 / 12
> >class C (small networks):
> >192.168.0.0 / 16
> >Note if someone does not untherstand: the /nn is the number of bits
> >belonging to the network. eg: the class B machines: is from 172.16.0.1 to
> >However, I have seen many LAN's with public addresses also because many
> >people (including the network administrators) does not know it.