New Posts  All Forums:Forum Nav:

No IP from Linksys WRT54G when hardwired. Help!

post #1 of 18
12/4/03 at 7:52pm
Thread Starter 
Ok I just got my 8890 with XP Pro. Then I tried to hook it up to my home network. I'm coming from 98SE so XP is a bit fuzzy to me, but I'm getting the hang of it. Anyways here's what's good: I can connect to the internet by directly connecting my cable modem to the nic. So I know the nic works. I can connect to the router and web by using my Linksys WPC55AG connecting to the Linksys WRT54G router. (IT's really nice and fast, except for some intermittent loss of the connection. Interference from 2.4GHz phone users in my apartment complex??) What I can't do is connect to the router when hardwired to it. I can't get an IP from the router, which should be 192.168.1.xxx. I can't release the ip and renew it .

So here's what I've tried so far. Manually entering IP, DNS, etc. didn't work. I've tried to power down, and reset and all those combinations, including following the router directions and that didn't seem work. I can't ping the router. I can't access the router setup page. My desktop works fine through the router, so does wireless. I've tried different cables and different connectors on the router itself, no go.

Anybody have any ideas??
Thanks,
Chris

edit: Could there be defective hardware, or is it just a software/OS issue?
Reply
Reply
post #2 of 18
12/5/03 at 12:39am
It's likely a software-only issue. You have already verified that the nic works by hooking the cablemodem directly to it, also that the network works by using the wifi.

I would think the subnet mask is different, do this:
Click START -> RUN -> CMD to bring up a command window (DOS window)

Type "ipconfig /all" and post the results here... The do the same from the desktop that is hard-wire connected to the router... post that also, and we'll see what's up.

Make sure you have the DNS and IP auto-configured in the NIC's properties. If you've hooked up the cablemodem directly, you probably set the DNS hardcoded into the NIC propertied. This should go back to automatic from the DHCP server.

-myrkat
Reply
Reply
post #3 of 18
12/5/03 at 3:19am
Thread Starter 

Here are some numbers

Ok, so I ran ipconfig through both computers. Here are the results

First, my desktop which has no problems:
Windows 98 IP Configuration

Host Name . . . . . . . . . : C
DNS Servers . . . . . . . . : 24.93.1.119
24.93.1.250
24.93.1.118
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No

0 Ethernet adapter :

Description . . . . . . . . : PPP Adapter.
Physical Address. . . . . . : <REMOVED>
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :

1 Ethernet adapter :

Description . . . . . . . . : 3Com EtherLink PCI
Physical Address. . . . . . : <REMOVED>
DHCP Enabled. . . . . . . . : Yes
IP Address. . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . : 192.168.1.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . : 12 04 03 6:13:52 PM
Lease Expires . . . . . . . : 12 05 03 6:13:52 PM

Now, this is my 8890 with the wireless adapter, which works fine.Windows IP Configuration

Host Name . . . . . . . . . . . . : CZWorkcomp
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Realtek RTL8169/8110 Family Gigabit
Ethernet NIC
Physical Address. . . . . . . . . : <REMOVED>

Ethernet adapter WPC55AG:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Dual-Band Wireless A+G Notebook Adap
ter
Physical Address. . . . . . . . . : <REMOVED>
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::20c:41ff:fe16:1d3f%7
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 24.93.1.119
24.93.1.250
24.93.1.118
fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Lease Obtained. . . . . . . . . . : Thursday, December 04, 2003 10:10:31
PM
Lease Expires . . . . . . . . . . : Friday, December 05, 2003 10:10:31

To keep it organized I'm breaking it into two posts, check the next one.
Reply
Reply
post #4 of 18
12/5/03 at 3:26am
Thread Starter 

ipconfig results (con't)

Ok, I removed the wireless adapter, pluged in the ethernet cable and restarted the system, here's what I get:
Windows IP Configuration

Host Name . . . . . . . . . . . . : CZWorkcomp
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8169/8110 Family Gigabit
Ethernet NIC
Physical Address. . . . . . . . . : <REMOVED>
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.249.3
Subnet Mask . . . . . . . . . . . : 255.255.0.0
IP Address. . . . . . . . . . . . : fe80::290:f5ff:fe0d:b1bd%4
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1

Then I tried to manually enter some numbers, which didn't work, but here are the numbers anyway.Windows IP Configuration

Host Name . . . . . . . . . . . . : CZWorkcomp
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8169/8110 Family Gigabit
Ethernet NIC
Physical Address. . . . . . . . . : <REMOVED>
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.102
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 24.93.1.119
24.93.1.250
24.93.1.118

I can't figure it out. Maybe at some point I'll bring the 8890 to campus and try to get on to the network there. Plug into a ethernet outlet in the library or something. I don't understand why the wireless is working with DHCP all nice, but I can't get the router and the computer and a few wires to play ball. I've double checked and made shure that the router is properly setup for DHCP and auto IP. I've also made sure that the MAC filtering is disabled as are all firewall functions. The only security I use for this is wireless WEP and disabled SSID broadcast.
Reply
Reply
post #5 of 18
12/5/03 at 10:04am

The bridge?

This may have nothing to do with it, but check the network connections and make sure the the stupid WinXP software connection "bridge" is not enabled. I have had nothing but trouble when that is running. If you check properties and see a "Network Bridge" item in there along with your other adapters, just right click and delete the thing. All of your network adapters will fix themselves and behave propery.

As Led Zepplin once said: "Has anybody seen the bridge? Where's that confounded bridge?"
Reply
Reply
post #6 of 18
12/5/03 at 10:58am
Mmmm, nasty but known problems....

Just see if these work:


Solution 1.
Try to set the IP address proporties manually. So go into Internet Protocol (TCP/IP) Properties and enter:

* Use the following IP address:

IP Address. . . . . . . . . . . . : 192.168.1.102
Subnet Mask . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . : 192.168.1.1

* Use the following DNS server addresses:
Preferred DNS Servers . . . : 24.93.1.119
Alternate DNS server . . . . :24.93.1.250


Solution 2.
My internal (11mbps) 8890 WiFi did not get an IP address from my router until I topped maximum speed of the latter to 11mbps (was 22 mbps). Different speeds ma result into problems when "negotiating" for IP addresses.
Reply
Reply
post #7 of 18
12/5/03 at 11:27am
I understand you need help..but posting your i.p. for the whole world to see is a big I hope you have a DYNAMIC i.p. and not a static one!
Reply
Reply
post #8 of 18
12/5/03 at 11:49am
Quote:
Originally Posted by Element
I understand you need help..but posting your i.p. for the whole world to see is a big I hope you have a DYNAMIC i.p. and not a static one!
He is going through a router, so the machines behind the box will not be seen. But he better have changed the default password. Personally, I like to assign the IP ranges (10.0.0.100-200, with the router at .250 and printer below 50)...

I also noticed the IP assigned:
Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8169/8110 Family Gigabit
Ethernet NIC
Physical Address. . . . . . . . . : <REMOVED>
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.249.3
Subnet Mask . . . . . . . . . . . : 255.255.0.0
IP Address. . . . . . . . . . . . : fe80::290:f5ff:fe0d:b1bd%4
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1Is a WINDOWS IP, if I'm not mistaken. There is NO GATEWAY listed, either, so it's not connecting to the router. Also, the DNS server IP's should be your router/gateway.

Usually, the DHCP Server, DNS Servers (only one), and the Default Gateway are the SAME IP address. This is the address of the router.

The above (bolded) address came from WINDOWS not your router, basically.

-myrkat
Reply
Reply
post #9 of 18
12/5/03 at 11:53am
Yeah I know but giving away the MAC address of your cable modem/router is totally n00bed out lol....with that information it's quite easy to cause havoc on a target network...
Reply
Reply
post #10 of 18
12/5/03 at 12:32pm
Quote:
Originally Posted by Element
Yeah I know but giving away the MAC address of your cable modem/router is totally n00bed out lol....with that information it's quite easy to cause havoc on a target network...
it's been "fixed" now...

-myrkat
Reply
Reply
post #11 of 18
12/5/03 at 3:00pm
Element is right, listing a MAC address for a device can be a dangerous thing, because with it you can spoof other hardware to make an attack lookas if it came from somewhere else.

That, and the MAC address is crucial to determing who gets access and who doesn't on many cable and DSL network ISPs, so better safe than sorry.
Reply
Reply
post #12 of 18
12/5/03 at 5:31pm
Thread Starter 
I completely spaced (it was really late) on leaving my MAC there, DUH. Thanks for the save myrkat.

I don't think the ip in this case is critical because I can always change that. Besides anyone who looks up linksys documentation on the web can find it. And yes my ISP is DHCP and has dynamic IP. (I'm pretty much a network novice, so i'm kinda stumbling through the dark here, but trying to be logical)

I checked to see if any bridges are installed or active and there aren't any. I know that the IP I got when connect by ethernet cable to my router is generated by Windows and not the DHCP of the router. This is my problem. Why is this happening?

hanko panko: I did try to enter the numbers manually, exactly as you have posted, no go. And I don't think solution 2 applies here, because I can connect fine through my Wifi adapter card. I just can't connect when there is an ethernet cable connecting my 8890 to my router. However both the 8890 and router lights come on when the cable is plugged in, it's really strange.
Reply
Reply
post #13 of 18
12/5/03 at 5:37pm
have u tried setting the speed of the nic to 10mbps instead of auto negotiation or 100mbps. i have the same exact problem when hooking up my 8890 to my linksys through a network cable. it works fine through wifi...i never figured out why it doesn't work through the cable.
Reply
Reply
post #14 of 18
12/5/03 at 6:27pm
Thread Starter 
Thanks Jebus, it worked.

Instead of auto-negotiate I set it to 10Mbps full duplex. That did the trick. I guess it was too much for my router to handle. Don't know why, but it works now.
Reply
Reply
post #15 of 18
12/5/03 at 10:30pm
After reading through the fun I'm glad you got it to work. The only reason I'm replying now is that I'm surprised the wireless card worked on your 8890, I had one of those for my 8886 and had to take it back because the Ti chipset for the PCMCIA was incompatible with the card. Anyway some insites:
169. is the address Microsoft defaults to when it can't find a network.
It is suggested that you use 192.168.200 as your router start addresses for the following reasons which may or may not apply.

1. It's not the default range so it adds one extra step for hackers.
2. Most businesses (mine included) use .1.1 behind the firewall and VPN starts at .200.1

As for the intermittent signal Linksys suggests:

Quote:
If your wireless signal is intermittent, then you are most likely you are experiencing 2.4 GHz interference. You will need to try switching channels and changing the SSID on your WRT54G. The best channels are 1, 6 and 11. To switch channels:


1.Using a computer that is plugged into the router directly with a network cable, open a web browser.
2.In the "Address Bar" type http://192.168.1.1 and press Enter.
3.A box should appear asking for a "User Name" and a "Password". Leave the "User Name" field empty, and type your WRT54G router password into the "Password" field (the default "Password" is admin) and click the OK button or press [Enter].
4.The WRT54G "Setup" page should now appear. Click onto the Wireless page.
5.When the "Wireless" page loads, you should be on the Basic Wireless Settings sub-section.
6.Look for the "Wireless Channel" option. The default channel is set to "6 - 2.437GHz". Change it to either "1 - 2.412GHz", or "11 - 2.462GHz"
7.Click on the Save Settings button toward the bottom of the page to save changes. Click Continue when prompted to reload the page.
8.The channel of your WRT54G has now been changed. Restart your wireless computers so that they can automatically connect using the new channel.
9.If you still experiencing interference using channels 1, 6, or 11, try switching the router to the other channels as well (2, 3, 4, 5, 7, 8, 9, 10) and find one that captures a good connection.
Anyway we might want to sticky this subject as it may come up again.
Reply
Reply
post #16 of 18
12/6/03 at 12:06am
the weird thing is that i have an older linksys 4 port router. it detects my nic fine at 100mbps. it must be a hardware/firmware problem on their part. hopefully there will be a fix soon.
Reply
Reply
post #17 of 18
12/6/03 at 2:10am
Thread Starter 
The setting of the NIC speed is an important one. I didn't find because it was as obvious as the other settings. The card worked fine. I did install the updated driver from Linksys and disable the Windows Management of Wireless Networks as was recommend in another thread.

Once I had everything working properly, I went back and changed the defaults of the router to my custom preferences and everything works as it should. I still can't figure out exactly why the Linksys router won't negotiate a speed with my NIC, the Private Windows IP defualts to 100Mbps, which I now know means basically nothing.

Thanks again for all the help. These forums and the knowledge of the people on them was one of my majors factors leading to the purchase of my Sager.

-Chris
Reply
Reply
post #18 of 18
11/27/05 at 1:49am
Thank you guys so much for this help. After owning my M-tech 870P (which is the same as a Sager or Prostar) laptop for about a year and having a couple of hardware problems, I thought that my NIC card was finally starting to die. After doing quite a few searches on the net for help I finally found this site and this post. Turns out it looks like this new Linksys router I bought doesn't like to negotiate a speed with my NIC. Thanks to all the people who helped with the problem above. I'm sure to check back with this site often when dealing with my notebook from now on.
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home