network funkiness: macbook/iMac/sympatico

mactrombone · Nov 30th, 2007, 10:05 PM

I have been having some problems of late with a home network that seems temperamental. I have Bell Sympatico HS coming into the house. That goes via ethernet to my intel iMac downstairs which is broadcasting my wireless network to the rest of the house so I can use my Macbook elsewhere.

Recently it seems that the Macbook and iMac have not been able to maintain the connection. The connection for the iMac is fine and I have consistent connection to the internet via the ethernet cable to the modem. I spent some time today tweaking things and thought that I had it. I may be able to tweak and get the connection on the Macbook but when I close it and then reopen it later it won't connect to the internet via airport. It connects via airport to my iMac network so I can see the other computer but no access to the internet.

I have reset the modem and restarted the iMac. Ditto for the Macbook. Most of these problems have been since the security update from the other day. I don't know if that is connected or not. I did reset the iMac TCP/IP to "Using DHCP with Manual address" with the address from this post:
http://www.ehmac.ca/mac-ipod-help-tr...-problems.html
That seems to have worked for the most part but by this point in time I don't know if I have completely reworked ALL my settings and wouldn't know how to get it back to basics except for "reset defaults".

Any help is appreciated.

mactrombone · Dec 1st, 2007, 11:07 AM

Well, it seems after some more tinkering and exploring on Apple's discussion forums that a restart temporarily fixes the problem. It does reconnect me but it doesn't solve the overriding network problem when the MacBook wakes after sleep.

Any other thoughts... Anyone... Anyone?

honeybee · Jan 4th, 2008, 03:53 PM

Sounds familiar...
I just bought an imac and I am constantly cycling the airport card on/off to renew my dhcp lease off my dlink wbr2310 router.
Funny, my 2 thinkpads don't have a problem and neither does my dell 1501.
I seriously believe, after having read several forums, that the self-tuning TCP parms in leopard are causing the conflict. My brother's imac with tiger does not have this issue.

mactrombone · Jan 5th, 2008, 07:36 AM

In my case it WAS the upgrade to 10.4.11. I archived and installed back to 10.4.10 and all is fine. That was actually the quickest solution. Saved hours of tinkering (which I had done already) and trouble shooting.