Assigning a network address

[PsychoSavager]

I'm trying to connect my computer to the internet, and the network won't assign an IP address to the computer. There's nothing wrong with the internet - it works on my laptop, so what settings do I need to change on my computer?

 

[Wildcard]

Hi,

If the network you are on is setup to assign IP addresses automatically, right click your my network neighborhood icon and choose properties. Then right click on your network card and choose properties again. On the general tab, you will see a box that says this connection uses the following items. If you scroll down, look for one that says internet protocol tcp/ip. Click on it so it is selected and then click the properties button. Check off the obtain ip address automatically as well as the one below it for the DNS. If you need a specific IP address, you can change the setting and then enter in the ip address you want :)

 

[PsychoSavager]

How do I find out what my computer's IP address is?

 

[Wildcard]

Click on start, then run, then type cmd into the run line. It will open a black window. Type ipconfig and then hit enter. It should show your ip address and other information.

Are you using a router to connect to the internet? You may need to power it off and also your computer for like 30 seconds if you are having network connectivity issues.

 

[PsychoSavager]

I've tried that. The network status said it was connected, but webpages weren't loading and MSN messenger wasn't signing in.

It says the subnet mask is 255.255.0.0 Is that normal?

I'm not using a router.

 

[Wildcard]

I think the subnet mask is dependent upon the network you are connected to. I think mine at home is 255.255.255.0 but I am at work so cannot verify that. Did you have an ip address listed when you did the ipconfig?

Also, are you able to ping any external sites? If you open up the same window you did the ipconfig in, type in something like ping Yahoo! and see if it shows response times. If it gets stuck, do a ctrl+c to break the command. If it doesnt respond, try pinging the local loopback on your NIC card. Type ping 127.0.0.1 and see if it responds. If it doesnt, then you need to take a look at your NIC. Also, if you go back to the network neighborhood properties and check your NIC card, is it enabled?

 

[PsychoSavager]

It doesn't work for external sites but it worked for 127.0.0.1 (response time <1ms)

 

[donkey42]

I think the subnet mask is dependent upon the network

true, mine is also 255.255.255.0

how do you connect to net ?

is DHCP turned on in the device that connects you to net ?

Edit: & are enough IPs being assigned for all network devices, because your internal network appaer to be working, try pinging google.com

ping google.com

 

[m60dude5]

127.0.0.0 works because that is your computer. It shouldn't have any problems talking with itself. So that means NIC is good.

 

[Wildcard]

Are you using a firewall? Some firewalls have a feature to stop your network connectivity.

 

[PsychoSavager]

Problem fixed! It was simple - I was disconnecting the ethernet cable from my laptop and plugging it straight into my other computer.

All I had to do was turn off the modem, plug it into the computer, and turn it on again and it reconfigured itself for my computer.

Thanks for your help!

 

[Anti-Trend]

Problem fixed! It was simple - I was disconnecting the ethernet cable from my laptop and plugging it straight into my other computer.

All I had to do was turn off the modem, plug it into the computer, and turn it on again and it reconfigured itself for my computer.

Thanks for your help!

Glad you figured it out. If you want to run both at once, you might want to look at a cheap NAT router. Or better yet, if you have an old PC sitting around, you could convert it into a free router/firewall:

IPCop.org :: The bad packets stop here!
m0n0wall -- lightweight open source firewall
pfSense Open Source Firewall Distribution - Home
Untangle -- all-in-one, open-source gateway appliance

127.0.0.0 works because that is your computer. It shouldn't have any problems talking with itself. So that means NIC is good.

Hate to contradict you, but 127.0.0.1 is a loopback address, and has nothing to do with the NIC. It's the OS talking to itself. All that proves is that the network stack is working.

-AT