More 9.2.2 Net Connect Issues

John,

Don't worry about Classic issues.

For the OS9 intrenet problem, can you check that AppleTalk is enabled on the Mac and that it is directed to use Ethernet.
Can you also check that File Sharing, etc is enabled over TCP/IP (an option in the FileSharing CP).

That was the easy options, otherwise ....

Can you also tell us if it is one of the routers that provides IP addresses to the Macs, or is it the OSX 10.4 Server Mac ? (ie. running OSX 10.4 Server, rather than OSX 10.4 Client, being used as a server).

If it's the 10.4 Server Mac allocating IP addresses, I think it uses some trendy new protocol, Open Directory, to do this, which base OS9 might not have. I think there is something with OSX 10.4 Server DVD, to allow OS9 to use it. Sorry I have no exact details, I looked at it about 8-9 months ago, but it didn't offer anything I needed.

You may find that the OSX 10.4 Server is supplying IP addresses to the OSX 10.4 Macs, while the modem / router supplies IP addresses to the OS9 Mac (and maybe OSX 10.4 Server Mac).

Hope I've not made this more complicated than it is.

John,

Well you've made it further than I did trying to get a router to provide DHCP while using OSX Server. I think most of my issues were that the Mac I was running the server on was so underpowered, and testing everything took so long. But you've given me new hope to try again with another Mac.

Back to your OS9 Mac. Now the only thing in OS9 you need to be able to access the internet / intranet are:
A router address, usually supplied by the DHCP provider, your router. Is it set and correct ?
DNS addresses, also usually provided by the DHCP provider, your router.
A correct subnet mask for your LAN, usually 255.255.255.0, also provided by the DHCP provider. This appears to be correct in your case.

I know these are obvious things, and that you've probably checked them a dozen times, but I'm starting to think that OS9 may be asking the OSX Server Mac for some of this info, rather than the router, which will get the important bits from the ISP (DNS). The fact you can't get onto google by IP makes me think the roter IP address is missing or incorrect, ie. it is the OSX Server mac rather than the router.

John,

Just open the TCP/IP control panel on OS9 and tell us what is in the four boxes.

"IP address" should be a valid IP address for your LAN, ie of the same form as the IP address of the Mac OSX macs, eg. 192.168.0.x

"Subnet Mask" should be the same as the OSX maccs also, 255.255.255.0 was mentioned earlier.

"Router Address" should be the IP address of the router (!!). This should not be blank. This would explain why the OS9 mac cannot connect to google, even when you put the IP address in explicitly.
background:The router then tries to find the IP address locally, it can't, so it passes it on to the ISP, who doesn't find it locally, so they pass it on to some router higher up the WWW - you can see the route taken with something like TraceRoure, or Traceroute in OSX's Network Utility. It takes me 21 "passes" to get to google.

"DNS Server Addr" should be one or preferably two (or three) DNS server IP addresses, supplied by the ISP. These do NOT have to be present. If they are not present, the address is passed up the chain again, to the router first, who will have the DNS Server addresses set - it does or your OSX macs would be useless as well.

I have been reading your post and I am having a similar problem. I am running 9.2.2 on a iMac400 and can't connect to the internet. When I plug in the router, I get the IP address filled in inside the TCP/IP settings but it isn't my router address which is 192.168.2.2. I am thinking my OS is missing something... I bought this computer used and without software to try out to see if I wanted to switch to Apple... well the verdict is still out on that subject and is not looking good.
Any Ideas?

Nordic,

So what are the addresses in the TCP/IP control panel ?

I'm also a bit suspicious at the router address. Router addresses, by convention rather than as a rule, usually use .0 or .1 in the lower end of their IP addresses if they're acting as DHCP, ie. 192.168.0.1 or 192.168.1.1. This was convention because it allowed the greatest flexibility with the use of bespoke subnets, ie. 255.255.252.0 which would make a subnet of all addresses between 192.168.0.1 to 192.168.3.255. Having 192.168.2.2 won't make any difference to a home network, it should still work.

In the TCP/IP settings, I have it set to Ethernet, using DHCP server, DHCP client 'blank', and it gives me the IP address as 169.254.61.98, subnet 255.255.0.0, and router address as 169.254.61.98.

My router address on my Dell PC (when I have the same cable plugged in) is 192.168.2.2 (I have the iMac and Dell side by side and just switching the 'straight' cable between them.) I have another PC hooked up to this router as well. I believe that the router address for that computer is 192.168.2.1, but I would have to check.

Nordic,

The mac has it's IP address 'self-assigned' when it is in the 169.254.x.x range. Meaning that it is NOT getting an address from the router.

Again are you sure that the router address is 192.168.2.2 ? and then 192.168.2.1 for the other computer ? I would have expected them to be the same. These addresses sound like the IP addresses allocated to the PCs by the router.

Is the router a 'real' hardware router, or is it some PC configured to act as a DHCP server ? I might suspect that the Ethernet cable you're using to connect to the iMac is a 'crossover' cable, rather than a 'patch' or 'straight-through' cable, meaning that it just cannot communicate with the router. You'll need to invest $2 on a 'patch' cable if this is the case. Also depends if it's a real router or not.

You' should also check that AppeTalk is on and is configured to go through Ethernet on the iMac. There is a corresponding control panel for this, it might be that it is configured to go via IrDA or something nutty.

Yes, the router is PC configured, I checked the DHCP box in the router settings. The cable is labled 'straight cable'from the factory.
I clicked on AppleTalk and it said 'TCP?IP cannot run over Appletalk because it is inactive'
Well... I just made AppleTalk 'Active' and set it to 'Ethernet'192.168.
Now What? I still get the same IP and router address

Nordic,

What is the make and model of the router ?

So you now have AppleTalk active and using Ethernet ?
Same with TCP/IP ?

And your IP address is still 169.254.x.x ??

If you run the Apple System Profiler on the iMac, it should describe the Ethernet port, either active or inactive, and what the speed is (10Mbps / 100Mbps). Tell us what it says.

In Apple System Profiler, in the Network Overview: Ethernet built in, Link: down, Speed: n/a, Duplex: n/a

Appletalk and TCP/IP installed and Active

Router is a Dell Truemobile 2300 wireless

Could be you just need to restart the imac for it to pick up the DHCP server. OS9 was pretty poor at detecting network changes. OSX is top dog at this.

I restarted the iMac and nothing happened, just still the same.

Nordic,

OK, then the Ethernet cable is hosed, or the Ethenet port on the iMac is hosed.

The full checklist - and I know you've checked all these before, but it doesn't hurt to do it again - is:

Ensure AppleTalk is active and using Ethernet.
Ensure TCP/IP is active and using Ethernet.
While in the TCP/IP control panel, click Options / Advanced (can't remember from memory), you should get an option to have TCP/IP active only when needed, turn this off.
Check the Ethernet cable in the PC again.
Check the Ethernet cable is firmly plugged in to the iMac - more than once on mine I found it just not all the way in resulting in network failure.
Check the Ethernet cable is firmly plugged in to the router - take it out and plug it in again.
Check for Ethernet cable running alongside power cables - not good.
Check for sharp kinks in the Ethernet cable - most Ethernet patch cables are of the "stiff" variety, sharp kinks can damage the cable.
Is there an activity light on the router for the port where the Ethernet cable from the iMac is plugged in ? Does it come on when the cable is plugged in ?
Restart the iMac. Does the light on the router come on ?
Try the Ethernet cable in a different port on the router.

Otherwise, the Ethernet card in the iMac might be toast.
One last option is to look in the iMac Extensions folder - in the System Folder) for extensions prefixed "Duplexer", with suffixes of "10" or "100" followed by "half" or "full", ie. "Duplexer100full". Remove all that you see, and restart.