More attempts.... Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\>ping 127.0.0.1 Pinging 127.0.0.1 with 32 bytes of data: Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Ping statistics for 127.0.0.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping www.google.com Ping request could not find host www.google.com. Please check the name and try a gain. C:\> ARGH!!!!!!
the 169.254 IP address is window's default IP address. Windows is saying i cant get a valid IP address from the dhcp server, so im giving you this one. can you test the ethernet jack by connecting another computer or laptop? when i ping stuff, i usually ping IP addresses like 216.40.198.6 or something so we can eliminate DNS out of the loop. all the best.
Okay guys, how many pins does the connector of a cat 5 cable have? I'm thinking I might have purchased the wrong type of cable, this one seems to have 4 little things in the connector. (i'm talking about the little plastic part that you stick into the NIC that resembles the end of a phone cord.
Cat 5 has 4 pairs of twisted wires, but then so do Cat 3 and Cat 4 from what I remember. Hmm... Cuttino Mobley... #5... hmm... Cat 5. Coincidence? You decide...
Only 4 wires? ...sounds like your network cable was home-grown by some lazy technician who didn't want to have to route all 8. It should still work (provided they are in the right place) since only 4 are actually used for Tx/Rx but no guarantees... BTW...props for calling it a NIC, and not a "NIC Card". You win bonus points with me...
Woooooooohooo! I guess I just initially bought the wrong type of cable, I went out and got another cable and I got it to work. I have to say that the setup for the dorm room internet access is still fairly difficult considering the average PC user knows only how to log onto AOL. Anyways, thanks for the help guys.
Lucky you! I was given the cable by the school itself so I know it's right, I just don't know what the hell I'm doing! But good for you, SCF! I'm quite jealous.
Apollo, did you get it resolved? As was mentioned already, the 169.254.164.88 address is the default auto-config address that windows will assign if it doesn't see a DHCP server..have you tried a known good network cable? get one from someone whose computer is connecting and try it with yours. Your network protocols seem to be working correctly, that was why you tried pinging 127.0.0.1..as long as ipconfig is showing the auto config address, don't waste your time trying to ping anything else..it aint gonna work. As long as you followed the config instructions, the problem is more than likely physical...(ie cable, jack) you could upgrade your NIC drivers or uninstall TCP/IP and reinstall it to cover all bases...but in my experience the problem is normally cable or jack related in situations like this. sorry for the delay in responding...yesterday was a busy day for me...couldn't get my CC.net fix till I got to work today.
I haven't fixed it yet! I'm pretty sure the cord isn't messed up, it was given to me by the residental life and housing office specifically for this purpose... Whenever I try to do the renew IP address thing like I was recommended to do, it pauses for a really long time, and then says something like the DHCP is unavailable or something along those lines...
Okay, here's everything I've been told to do so far... Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\>ipconfig Windows IP Configuration Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : IP Address. . . . . . . . . . . . : 0.0.0.0 Subnet Mask . . . . . . . . . . . : 0.0.0.0 Default Gateway . . . . . . . . . : C:\>ipconfig/all Windows IP Configuration Host Name . . . . . . . . . . . . : T406B Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Broadcast IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethe rnet NIC Physical Address. . . . . . . . . : 00-08-02-2F-AF-98 Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 0.0.0.0 Subnet Mask . . . . . . . . . . . : 0.0.0.0 Default Gateway . . . . . . . . . : DHCP Server . . . . . . . . . . . : 255.255.255.255 DNS Servers . . . . . . . . . . . : 129.7.1.1 129.7.1.20 129.7.1.6 C:\>ipconfig/renew Windows IP Configuration An error occurred while renewing interface Local Area Connection : unable to con tact your DHCP server. Request has timed out. C:\>ping 127.0.0.1 Pinging 127.0.0.1 with 32 bytes of data: Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Ping statistics for 127.0.0.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 169.254.164.88 Pinging 169.254.164.88 with 32 bytes of data: Reply from 169.254.164.88: bytes=32 time<1ms TTL=128 Reply from 169.254.164.88: bytes=32 time<1ms TTL=128 Reply from 169.254.164.88: bytes=32 time<1ms TTL=128 Reply from 169.254.164.88: bytes=32 time<1ms TTL=128 Ping statistics for 169.254.164.88: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>ping 216.40.198.6 Pinging 216.40.198.6 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 216.40.198.6: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\>
Just because they gave it to you doesn't mean it isn't defective. Try a *known* good one and see if anything changes...
Apollo, I had the same problem, and I think the problem was a conflict of my network card and my sound card. Get on control panel, then systems, and check to make sure that both are working properly. I believe I had a Soundblaster Live! Value card and a generic network card. I updated my drivers and it worked. However, if you are running Windows XP, that shouldn't happen. Anyone else here have a clue?
Rockets2k, one of the reasons I'm pretty sure the hardware is working correctly is that as soon as I plug the cord into both the computer and the jack, the automatic windows XP hardware thingy comes up and says "Local Area Connection 10Mbs" and when it's unplugged it goes away, so it makes me think that aspect of it is working correctly...
XP has weird problems, same thing happened to me w/ me dsl when I first hooked it up. Try this and see if it works. ipconfig/release -you should get 0.0.0.0 for all ip, then type ipconfig/renew now try browsing again and see if it works
Appreciate the advice, but that was suggested earlier... The results of what happened are posted in one of my many replies...
All that tells you is that the cord is plugged in. doesnt mean it works all the way down the line. but anyway... Ok man, good luck.
