No IP unless connected to a router

[MattB]

When I connect my Kanga (running 9.1) to my wireless router with an ethernet cable, it gets an IP and connects to the internet no problem (I'm posting this message from it). However, when I connect it directly to one of the ethernet jacks in my apartment, the system can't get an IP or connect to the net (my WinXP-based machine will connect fine this way and pulls an IP with no issues). Is there any way to configure TCP/IP settings in 9.1 to direct connect like this?

 

[ClassicHasClass]

Is your Kanga configured for DHCP, or is it just using a static IP? 9.1 has a DHCP client, so it can definitely fetch addresses. The fact that your XP machine can get an IP implies that your apartment network has a DHCP server, so it's not that.

 

[Dennis Nedry]

The router is likely connected to the wall with the WAN port, so it is establishing a connection in a way that the building likes. The router then creates its own subnet for the LAN ports that the PowerBook likes. This is my observation. It seems possible that the PowerBook could have a static IP that the router allows. As mentioned, verify that you are set to use DHCP without manual address.

Is there a reason that you don't want to use the router? Connecting directly opens you to all sorts of hackery from anyone in the building whereas the router provides a very nice firewall and can split your connection to your PC.

 

[MattB]

The system is set to pull an IP from a DHCP server in the TCP/IP control panel, so the settings should be correct. Is there anywhere else where the system might be trying to use a static IP The primary reason for my attempt to directly connect to the network rather than use the wireless router is that the router is physically located in my office room and the Kanga is set up on a desk in my bedroom (both rooms have ethernet jacks).

 

[Dennis Nedry]

This is a very strange problem.

Is there a way to check link status in OS 9? Maybe a link isn't even being made. That may provide a clue. I have an almost-dead 100Mb switch that has a couple of ports that only work with certain computers because of low voltages. You may have an iffy switch in your building or your onboard ethernet may have gone a bit out of range.

Might you consider a wifi card for your PowerBook to run off of your router? That could be cool.

 

[MattB]

I may actually just get an 802.11b card for the Kanga. It's already got software installed for one, suggesting that it had one at some point before I owned it. I doubt it's a problem with the onboard ethernet hardware, namely because the other Kanga I have does the exact same thing. Both can get IPs from a router, but not from the wall jack.

 

[Anonymous Freak]

What kind of addresses are you talking about, anyway?

If they're 169.254.x.x, then they are what is called an "Automatic Private IP". They are self-assigned from that pool set aside specifically for local networks that have no IP-assignment infrastructure such as DHCP.

I seem to recall that some older versions of the Mac OS would *NOT* assign an automatic private IP, they would just sit without any address, if no DHCP (or BootP, etc,) server was available.

 

[MattB]

There is definitely a DHCP server on the network because the router (or a PC when connected to the wall jack) gets an assigned IP address rather than an automatic private address. The TCP/IP control panel isn't showing any IP address and just appears to be waiting for one from the DHCP server.

 

[Dennis Nedry]

Try zapping the PRAM.