Help re-setting up Network

[rx321]

Hi everyone, the last few days I've had a major problem. My computer almost got nuked in the way that it's HIVE files became corrupt and I had to use the recovery console to copy registry files around and such.

I got that fixed and was able to restore all the links on my computer manually, but right now I'm having a problem connecting to the internet. I'm using a client computer connected to a router that has 2 other computers on a network. Right now all the computers on that network work except for mine and I'm assuming it's because some settings for my comp got reset and right now it's not recognizing that I have a network. I'm using a linksys router and a win xp operating system.

I've tried every option available and every network setup option. Is there something that I'm missing? My ISP is comcast and I've tried calling them up to see if maybe there's a username/password I have to enter in order for my computer's internet to be enabled, but they all say that I don't, if so how do I make my computer recognize the network it's on. The cable is in and so is the card, can anyone help me?

[z1p]

welcome aboard rx...

There's some simple things to check right out of the gate and it will help narrow doen where the problem is.

Is your network showing that it is connected?
Also, go to the device manager and see if there is an exclamation mark on the icon for the network card.

Lastly, run "cmd /k ipconfig/all" and post the info back.

[rx321]

ok here's what I got, and the network card is functioning properly

name: rx321
primary dns suffix: n/a
node type: broadcast
IP routing enabled: no
WINS Proxy enabled: no

ethernet adapter lan connection

connection specific dns suffix:
ne2.client2.attbi.com
description: smc ez card 10/100 PCI
DHCP enabled: yes
auto configuration enabled: yes
IP address: 0.0.0.0
subnet mask: 0.0.0.0
dhcp server: 24.34.241.34
dns: 63.240.70.19
204.127.198.19

[z1p]

OK more questions.

Is your router set up to do NAT and act as a DHCP server?

Is your network connection setup to obtain its IP address and DNS server automatically?

[rx321]

I'm not sure, how would I figure that out?

[z1p]

for the network connection, go to network connections and open the properties for your connection. select TCP/IP and open its properties. The setting are on the general tab.

For the router settings, you need to log onto the router. For now check the 'obtain automatically...' settings on your machine and one that is working. post back any differences.

[rx321]

Okay, I've checked the TCP/IP properties for the computer with the router and the client that's not working, and they're both set to obtain automatically. The router also shows a connection light for the client that's not working.

If I were to do the Files and Settings Transfer Wizard, could I basically automatically fix this issue with it that way?

[z1p]

got me there!! I haven't used it nor do I know what it goes. I have a feeling it won't help.

Try the steps outlined in this M$ KB (http://support.microsoft.com/default.aspx?scid=kb;en-us;822123)

[rx321]

okay I tried those, but didn't seem to work. Here's some screenshots of my connections, it's like they're on but my computer doesn't know it.

http://img49.exs.cx/img49/2188/pic10vv.jpg
http://img49.exs.cx/img49/2122/pic23jp.jpg

and I get errors when I try to repair my connections. The first is for the internet connection, the 2nd for the LAN


http://img49.exs.cx/img49/5868/pic36pv.jpg
http://img49.exs.cx/img49/2227/pic48wp.jpg

[z1p]

You don't care about 1394 connection, that's fire wire and your not using it. You got pisture 3 (http://img49.exs.cx/img49/5868/pic36pv.jpg) when you tried to repair the local lan connection, correct?

And you've made sure that TCP/IP is installed as a protocol for the local LAN connection?

[Cryptkeeper]

ok here's what I got, and the network card is functioning properly

name: rx321
primary dns suffix: n/a
node type: broadcast
IP routing enabled: no
WINS Proxy enabled: no

ethernet adapter lan connection

connection specific dns suffix:
ne2.client2.attbi.com
description: smc ez card 10/100 PCI
DHCP enabled: yes
auto configuration enabled: yes
IP address: 0.0.0.0
subnet mask: 0.0.0.0
dhcp server: 24.34.241.34
dns: 63.240.70.19
204.127.198.19

This is my first post so hi to you all!!

I find this information you gave here very strange. Looking at that my first guess would be that the dhcp settings from your router are wrong.
I'm assuming everything from your network card's tcp/ip settings are set to auto.

- If your pc couldn't connect to the dhcp (wich is on the router) you would get a default ip adress from windows ( it starts with 169 I think). This here is not the case.

- The dhcp and dns servers are set, wich means that you got those from the dhcp or you set them manually.

Try to type ipconfig /renew and then again ipconfig /all and post that info again please.

I am no expert on networking so if my assumptions are totally wrong please say so. I'm eager to learn :)

[ceh383]

Try this.....

In network connections, right click on "Local Area Connection" Select Properties.

In the "This connection uses" box, is "Internet Protocol(TCP/IP) listed and checked?

If it is, go to Start button>>Run>>CMD

At the command line type "ping 127.0.0.1" (no quotes) enter, post results.

If it is not, click the "install" button>>Protocol>>Add button>>Internet Protocol>>OK button.....follow instructions(you may need your XP disk)

Post results.....

[rx321]

wow, thank you guys! It was the "IP /release" "IP /renew" that has fixed this problem. For some reason it was giving me errors like, "windows cannot find this file", but I just did it again and it worked so I've enabled my network via ZoneAlarm. Can't thank you guys enough for the help!

[z1p]

Glad to hear your up and running and thanks for posting back.

[Archangel122184]

Damn!

I had the solution and it would figure it was solved. The clue was in one of your first posts

"IP address: 0.0.0.0
subnet mask: 0.0.0.0
dhcp server: 24.34.241.34
dns: 63.240.70.19
204.127.198.19"

It found a valid dhcp server, or at least though it did, it just couldn't bind a new ip from it. The only reason this happens is registry linkage errors easily fixed by a forced release (clears cached servers) and renew (full discovery). Anyway, glad you got it solved.