Hi all, hopefully there's some networking guru out there who can help me with this one. Here's the situation:
I have a cable modem (Motorola) and an iBook (G3-600 dual-USB). I purchased a Linksys Wireless-B router to go between them and add wireless capabilities (the iBook has an Airport card). Now, when I hook up the iBook to the router via cable it finds DHCP but is not able to ping or http what claims to be the router at 192.168.1.1. So it finds the router enough to make the light blink on the front, and assign an IP address (in a weird way, more on that later) but not enough to do anything with the connection beyond DHCP. Wireless is same deal, Linksys' documentation says you have to configure it with a wired connection before you can turn on the 802.11b, which is understandable for security purposes.
My original thought was a DHCP conflict between the cablemodem and the router. But when the cablemodem is totally disconnected the same problem occurs. now here's the two funny things that suggest to me this is something in the iBook's config (I am on 10.3.2 here): #1 -- I cannot renew my DHCP lease until I reboot, like some Windows peon. In other words it keeps self-assigning IP addresses if I just plug things in without rebooting, unable to locate the DHCP. But if I reboot, it's fine when it comes up. #2 -- in ifconfig, my en0 interface frequently has 2 IP addresses assigned to it, like this:
---- what ifconfig reports (excerpt):
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.1.100 netmask 0xffffff00 broadcast 192.168.1.255 <-- the IP assigned to me by DHCP or manual
inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 <-- the mysterious IP assignment
ether 00:03: blahblah
media: autoselect (100baseTX <full-duplex>) status: active
supported media: none autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback>
blah blah, en1, fw0 config info (all inactive)
-------
If apache is on then 192.168.1.1 comes up as my localhost web server default page. If not it just doesn't connect to anything.
I have shut off all sharing and all port configs except Ethernet in network prefs. If I go sudo ifconfig en0 192.168.1.100 or whatever it will eliminate the duplicate IP address in ifconfig, but the GUi tools don't catch it because they only assume one IP per network interface. Coincidentally this 192.168.1.1 IP is the admin IP for the Linksys router, but it appears in my ifconfig whether or not the router is hooked up. It's something else. If I do eliminate it manually via ifconfig, I can no longer ping myself at 192.168.1.1, but I also can't ping/http the ROUTER either even if it's hooked up.
And here's the final clue. In Sharing Preferences, when I click on the 'Firewall' tab, it says 'Other firewall software is running on your computer. Please turn it off before you can adjust the firewall settings here'. And I'm like what the hell because I am not aware of any firewall software I am running (Virex etc is not installed on this machine).
Any ideas? This is a tough one.
.
NT
Your post showed a broadcast to that address, not that you were assigned the .255 number. As to x.x.1.1, this can be a valid IP to assign. I don't recall what IP the router is at.
Bob
A valid address for your iMac, on a Linksys router (wireless or wired) should be 192.168.1. <100 - 150>, as it comes from the factory. If you cannot get an address in that range in the TCP/IP tab, the easy answers are:
1. Are you using a "straight-through" cable.
2. Are you set for DHCP?
3. Is the Router in the default condition?
Since you have played with the Apache server software, it is possible it has assigned itself 192.168.1.1 (a very common private IP address for a server). If it is still running and using that address, it will prevent the Linksys Router from serving you an IP address.
Hoping this helps, Bob
I have had a hard-wired ethernet network with a linksys router for several years. When I decided to go wireless, I purchased a linksys wireless router and figured it would be a piece of cake to add it into the mix - after all I'd been solving all my own networking issues for a long time... Boy was I ever wrong! I felt like I'd been placed on an alien planet. I read manuels, searched online help databases, etc., etc. I finally hired someone to help me and it was the best money I'd ever spent. I am completely convinced that wireless networking is like a foreign language - you need to hire a guide to really communicate with the natives! My advice is that when you finally feel completely frustrated, give in, call in a IS guy who understands wireless networking (I was lucky enough to have a buddy who worked the evening for dinner and a sixpack - ask around you may be as lucky too) and put your pride aside. I have since added additional computers and printers - a Mac and two Airport Expresses - and they have recognized the liksys like a charm. Good luck - this stuff gets confusing - but once it's set up right, it really is easy to manage.
| Forum legend: | |
| Locked thread | |
| Moderator | |
![]() |
CNET staff |
![]() |
Samsung staff |
| Norton Authorized Support team | |
| AVG staff | |
| Windows Outreach team | |
![]() |
Dell staff |
| Intel staff | |