Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Giving out an IP address 1

Status
Not open for further replies.

Hickeycapt

Technical User
Jul 13, 2006
2
US
Just curious,..recently my landlady's grandson got an internet adapter for his Playstation, and asked what our network IP address was. He was told (by my landlady AND myself) NOT to give the IP address out to ANYONE!
As it turns out, he did anyway!
Since then, I find myself constantly needing to disable & re-enable my network adapter just so I can surf the net?!
Has he endangered our network & what can I do to re-protect (and FIX) our network?
PS- Anybody want this kid???? CHEAP!!!! LOL
 
Quite frankly, if you have a public IP address on the internet, everybody already knows about it. Giving out doesn't make you any more vulnerable. It's very unlikely that the fact that he gave it is related to your network adapter problem - if they are related, you have some odd condition that should be fixed anyway.

More info about the network would be needed to diagnose that problem. I would guess that we're talking about a broadband connection, personal home router, a few pc's and a playstation - close?
 
If it was a private IP, it wont work on the internet as it isnt routable. If it was a leased IP from your ISP it has changed. If it was a fixed IP from your ISP, get a new one. And dont give it out. (Are you on medication?)

pc.gif

Jomama
 
if your network ip address is one of the following:

10.0.0.x
172.16.x.x - 172.31.x.x
192.168.x.x

(where X represents a number)

Then this is private so it doesnt matter who you tell...

However regardless of this fact, not telling anybody about it makes no difference whatsoever! And this I would almost certainly say has nothing to do with your network adapter issue.

'When all else fails.......read the manual'
 
However regardless of this fact, not telling anybody about it makes no difference whatsoever! And this I would almost certainly say has nothing to do with your network adapter issue.
Except if it is a public IP given to him by his ISP and more than one node has it, there will be a conflict.

pc.gif

Jomama
 
Except if it is a public IP given to him by his ISP and more than one node has it, there will be a conflict."

Well if that is the case and it is broadband cable, all he has to do from the "Dos command prompt" is ipconfig /release and then ipconfig /renew and he should get another IP addy unless the ISP has given him a static address (that is an address that is directly been reserved for you computer - by way of your MAC address)

 
cyberspace said:
if your network ip address is one of the following:

10.0.0.x
172.16.x.x - 172.31.x.x
192.168.x.x

(where X represents a number)

The RFC1918 private network address space is actually:

10.x.x.x
172.16.x.x - 172.31.x.x
192.168.x.x

And the vast majority of attacks are attacks of opportunity, not targeted attacks. Bots are constantly scanning every IP address in the routable space and attempting to compromise whatever system they find. In the rare cases of targeted attacks, it is generally a corporation or specific domain that is targeted, and those addresses can be retrieved from any DNS server on the net.


pansophic
 
Somehow nobody got the IANA private IP addressing range correctly.

Network Working Group IANA
Request for Comments: RFC3330 September 2002

Special-Use IPv4 Addresses​

10.0.0.0/8 - This block is set aside for use in private networks. Its intended use is documented in [RFC1918]. Addresses within this block should not appear on the public Internet.

172.16.0.0/12 - This block is set aside for use in private networks. Its intended use is documented in [RFC1918]. Addresses within this block should not appear on the public Internet.

192.168.0.0/16 - This block is set aside for use in private networks. Its intended use is documented in [RFC1918]. Addresses within this block should not appear on the public Internet.

 
Actually,

10.0.0.0/8 = 10.x.x.x
172.16.0.0/12 = 172.16.x.x - 172.31.x.x
192.168.0.0/16 = 192.168.x.x

Just CIDR format addressing.


pansophic
 
OK folks, thanks for trying to help....but it turns out it was a Comcast screw-up.
Everything works fine now!
 
The RFC1918 private network address space is actually:

10.x.x.x

My bad - that's what I meant :)

'When all else fails.......read the manual'
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top