Dropping Wi FI Signal

Oh and I forgot to ask, but since I have a roommate I would like to not disrupt my setup here for his sake. So coming from the 2WIRE gateway I have a ethernet cable running to my room which is connected to a hub to split the connection between my desktop, xbox, and cable box. My question is, whatever router I end up getting, can I place it between the gateway and the hub? Or even better yet, after my hub? Will it still work, and basically give us two wireless networks?

Thanks for the help.

forum1983 wrote:
Oh and I forgot to ask, but since I have a roommate I would like to not disrupt my setup here for his sake. So coming from the 2WIRE gateway I have a ethernet cable running to my room which is connected to a hub to split the connection between my desktop, xbox, and cable box. My question is, whatever router I end up getting, can I place it between the gateway and the hub? Or even better yet, after my hub? Will it still work, and basically give us two wireless networks?

Thanks for the help.

Okay so I was just looking on the Apple store at the Airport Extreme and Express. I wondering how reliable they are, particularly the Express. And like I said before if it would be compatible with the existing network or I would have to do away with the existing router. You know what, I think I'll go to my local Apple store. Luckily I live like 5 minutes away from it :-D

Yeah I think I'm having the same problem.

Example:
I see that it has full signal now, so I use it, and then after a while I'll go away after I close the lid. I come back a while later and to use, when I see that the signal has dropped almost to nothing, and sometimes no connection at all. I tinker with it by clicking on the icon in the menu bar as it tries to search for the thing. When I doesn't, I Log Off and Log back in, and Voila! It's FULL signal! How is this possible? I did nothing to change anything before.

Thank you.

forum1983 wrote:
Please provide an explanation of why someone using Apples own router is still having issues! I am starting to seriously think about getting a new router but if their own equipment can't even work with their computers then what hope does 3rd party products have.

I've said before if you have issues when using an AirPort router, you've either got interference issues causing your problems or a system issue.

I've also said before that as a debugging step, whenever possible:

1) Vist an Apple Store
2) Try your machine on their network
3) If the connection drops, make them fix it.

Reason being, I've tried and checked log after log and have never seen a connection drop inside an Apple Store.

My gut reaction would be interference but the easiest move may be to check it in an Apple Store if at all possible.

Is the 10.6.2 update going to address any airport issues? I've tried all the fixes...I mean all of them. I had this issue in 10.5 and found a work around by running istumbler. I had taken it in apple and they knee jerk replaced the airport card. It didn't fix my problem. When istumbler was running it would constantly be searching for networks and my connection would stay strong. (I shouldn't have to have had a work around, but you do what you have to do.)

I installed snow leopard hoping this would fix this problem. Of course it didn't and it rendered my work around (istumbler) useless. I am so frustrated. I have called apple several times and they want me to send my MB in to be tested. I'm sure they will replace the card again and send me on my way. It doesn't take much research to see that this problem is a software issue. This is unacceptable. I could not be less satisfied in my computer.

It doesn't take much searching to see that I am not the only one with these issues. I know my problem is in the MB. I have another laptop and xbox that use my network no problem. We need a fix. I know this problem is not widespread, but it is affecting enough people that apple should take notice.

sonofdon wrote:
Is the 10.6.2 update going to address any airport issues?

It would be speculation and a violation of the Terms of Use to address this.

We'll find out what's in 10.6.2 when it's released.

It doesn't take much searching to see that I am not the only one with these issues. I know my problem is in the MB.

Both true, but this can be said about pretty much every computer problem.

Reading the thread in detail, it is clear that many of the problems in this thread are common wireless problems and solvable. In fact, many have been solved. If you follow all the advice given here, I suspect you will find solutions.

Yes, troubleshooting is a pain, but do not give up and simply blame Apple. Yes, Snow Leopard is not perfect, and may have some specific wireless bugs. BUT it can work! Millions of Snow Leopard users have no problem. There is no particular reason why your system can't work also (unless the hardware is broken which you can check in an Apple store).

Name a step in trouble shooting and I've done it. I could list them all but it's not worth the typing. If this was so easily solvable this thread wouldn't be 16 pages long. It's a software issue that affect's a small percentage of macs. It's not widespread but do a simple google search on snow leopard airport issues and see how many hits you get. I have and I continue to troubleshoot my airport issue. I have talked with apple and I have research online. Nothing has been a fix. When I change any setting with my MB I have some temporary relief to the issue, but it's only temporary. Everytime my connection slows I option click the airport icon and it shows that my transmit rate is very low (1-3 usually). When the connection is working well it's normally 50+ or if I'm on a N network 120 or better. I have a linksys router, but I have hooked up an airport express. I have used it on other networks with the same problems. I've updated firmware and I do not have some new interference from another router. I've switched the channel several times. I've reset the pram. I've removed the system preference file. I've changed locations. I've reset my router to a WPA. On and on... All steps would give me temporary relief, nothing is a solution.

I do not need someone cheerleading for apple, I need a fix. I am not the only one who needs a fix. This is a real problem.

todhop wrote:

Reading the thread in detail, it is clear that many of the problems in this thread are common wireless problems and solvable. In fact, many have been solved. If you follow all the advice given here, I suspect you will find solutions.

Yes, troubleshooting is a pain, but do not give up and simply blame Apple. Yes, Snow Leopard is not perfect, and may have some specific wireless bugs. BUT it can work! Millions of Snow Leopard users have no problem. There is no particular reason why your system can't work also (unless the hardware is broken which you can check in an Apple store).

I would dispute most of that. It's not such a common wireless problem to find one specific operating system dropping signal while other computers do not.
Also 10.6 has not been out very long at all so this millions of satisfied users is more wishful thinking then anything else.

We don't even know how all those millions are connecting to the web, and so you can't claim, as some here have, that the connection drops have nothing to do with Apple while also claiming the apparent lack of huge numbers complaining means that connectivity works-it's not logical.

In my own situation I found that the wireless router I replaced (A westell made for bellsouth) doesn't accept any firmware updates-that's the way it was designed. So why was there a problem with that? Maybe something to do with my ISP?

I agree with sonofdon fanboys are not needed but they better hope that their wireless parameters don't vary nor that they encounter a wifi network somewhere that doesn't measure up to Apple's connection phobic OS because then they'll be looking at this from the other side.

todhop wrote:



Reading the thread in detail, it is clear that many of the problems in this thread are common wireless problems and solvable. In fact, many have been solved. If you follow all the advice given here, I suspect you will find solutions.

Yes, troubleshooting is a pain, but do not give up and simply blame Apple. Yes, Snow Leopard is not perfect, and may have some specific wireless bugs. BUT it can work! Millions of Snow Leopard users have no problem. There is no particular reason why your system can't work also (unless the hardware is broken which you can check in an Apple store).

You really can't call any of these a so called "solution", more like temporary work around. And I seriously stress temporary. Most of the people that said they finally fixed their issue for good, replaced the router; and where one router would work for one person, it wouldn't work for someone else.

sonofdon: you and I seem to be the only ones, at least on this thread, that had this issue before we upgraded to SL. The Apple store also replaced my Airport card on my first visit, on my second visit they asked me to have my ISP check their equipment, on the third visit the Apple store replaced my computer out-right. I still had the issue after all of that and all of the troubleshooting tips from this thread and Apple Care over the phone. I went back to the Apple store for the fourth time, and this time the employee felt bad for me and brought out the store manager, whom I talked with for some time. I went to the store to ask about a replacement router, and the manager was very kind and offered to give me a full refund if I wanted to return my MBP (which I got in January). I told him that I wanted to try a replacement router, so he gave me approval for 30 day return on the router. I bought an AirPort Extreme and I connected it back to back with my original router to provide a separate secondary wireless network. Thus far it has seemed to solve my problem. But is spending $200 (with tax) after spending $2000 for the computer for a new router an actual fix? I think not. It should never come to this. There has been someone on here that said their Airport Extreme didn't fix their problem but so far it has for me, so this is another solution for some but not for all. Some have fixed it with cheaper 3rd party routers but I figured Apple brand router must work with Apple computers. (Note: I opted for the more expensive AirPort Extreme instead of the Express or another cheaper router because my current router (being used at my girlfriends house) is pretty outdated and was needing replacement. A cheaper alternative may be better for you.)

Perhaps if people are unhappy, and their local Apple store has a sympathetic manager, you might get your money back and just get a different computer. And just perhaps, after Apple starts seeing product returns, they might like to address this one way or another.

I agree with sonofdon fanboys are not needed

Name calling won't help. I have discovered over the years that anger is the worst enemy of troubleshooting. Unfortunately, I've also discovered that suggesting that people put aside their anger tends to make them angry. Ironic isn't it.

I do not discount your problems. My personal Macbook is still 10.5.8 (which connects great) even though I have a SL upgrade on the shelf. That's why I'm following this thread. But I also manage SL laptops that are doing okay.

There are problems with newer Macbooks. It's likely several problems, including the firmware of the new airports (my prime candidate). Everything I know to try is somewhere in this thread though some steps are drastic and difficult. Some might have to be done in a particular order. At one point, I tried to make a checklist to help, but I lost track after 10 items.

If it helps, here's my experience so far. I currently manage one new Macbook, one Snow Leopard upgraded, and one 10.5.8 Macbook that all appear to be working though the newest system took a bit of coaxing at initial setup. The problem with the newest system seemed primary related to dropping DNS. It also does a bad job of scanning the Windows workgroup and LAN domain names, something the 10.5.8 system never had trouble with. Setting DNS servers manually solved the DNS issue. I have not solved the Windows/domain networking weakness. I believe this is simply a new incompatiblity with my older server (which I can't upgrade) so I work around it (low priority). I also had a serious Samba compatibility problem with both Snow Leopard and a new Windows Vista machine. The solution to that was server side (deleted old ".dsstore" files on the server that cause SL problems for some reason). Oh, the Windows Vista machine required a registry hack if you care.

I am sympathetic. And I am trying to help. And now I'm cluttering the list with unecessary blather, so...

Cheers,
tod

todhop wrote:

I agree with sonofdon fanboys are not needed

Name calling won't help. I have discovered over the years that anger is the worst enemy of troubleshooting. Unfortunately, I've also discovered that suggesting that people put aside their anger tends to make them angry. Ironic isn't it.

It wasn't intended as name calling. For me it's discernment. I've been at many forums and spent a lot of time helping at the ubuntu forums. Often people think that they are "taking one for the team" if they minimize or otherwise diminish a poster's problem. Fandom is simply that; blind adherence to or loyalty for a brand without regard for the experiences and situations being described.

Some posters here have acted as fans. There's not much I can do about that. It's not really necessary to make Apple bad on this either-provided they are willing to spend the time and energy to correct this problem instead of using fanboys to deflect the focus.

I also am watching this. I have SL on an iMac and my Pro with no issues. I tried to install it 4 times on my macbook and it never worked (always got a static IP address assigned no matter what I did)..so it stays at L. My father-in-law just got a macbook (as the deals are fantastic). It came pre-loaded with SL...at first it was fine. Upgraded the router to n technology (ESR) and he gets the dropping wifi. Also we lost Back to my mac (error says to enable NAT or UPnP...which are enabled). So I suppose it is an interaction of firmware, hardware and software which creates the issues. This is also why it is difficult to trouble shoot as interactions likely show up intermittently. Suppose Mac developers should learn how to do factorial designs to understand the potential interactions...LOL

You've encountered two specific issues that seem to be common: interaction with DHCP and "n" compatibility. For the first, I suggest assigning a valid static IP and manual DNS entry. There is really no downside to this once you figure out how to manage static IPs on your LAN (not terribly hard). Create a "network location" first before trying this and leaving your automatic settings on DHCP. You may find that once you've done this, you can turn DHCP back on and it will work. This trick can help with any network connection by the way since failing to negotiate DHCP is pretty basic, and not uncommon.

As for "n" compatibility, this standard was only finalized this year and many devices just don't play nicely. Try disabling "n" functions in your router and see if that helps. Can "n" be disabled at the adapter? If "n" connections are the specific problem, search for that and your specific router settings as there are other things to try. Also look for any 2.4Ghz devices in your home (wireless phones and microwaves are primary candidates) and move your router as far away as possible all of these (and from any neighbors wireless access point). This effects all wireless, but "n" connections seem more sensitive to this interference. If you connection drops when the phone rings, that's your problem.

Oh, and disabling (not enabling) UPnP at your router is commonly cited "fix" for SL connection problems. UPnP has had a long and sordid history, so if disabling it works, I suggest you just leave it off unless it breaks something else.

cheers,
tod

Just in case someone is keeping track. I got one the the new Mac Books last week and am running Snow leopard. I have had an terrible time keeping on the wifi network at work and at home. I took the computer to the network help desk and they ran the disk permission repair and got me up and running for a day. I really hope this get fixed in the new update. I am a loyal Mac user and expect better from Apple.