Sudden WRT300N Wireless Issues

Hi all,
We bought a WRT300N router just less than a year ago and it has been working perfectly until this weekend. As I'm writing this (and browsing pages in ohter tabs) I'm noticing that the speed of the internet has also lowered by a noticable amount, I suppose that this could possibly be connected. I noticed yesterday that the wireless SSID was no longer picked up by any wireless equipment. Nothing in the router has been changed - at all; no settings were updated, it was not moved or bumped, etc. The only possible change in the environment is that we have had some new neighbours move into the upstairs flat and they could possibly have their network on the same frequency as ours. I have been playing all day with different settings, in addition to resetting the router to factory defaults, carrying out the hardware reset by holding the reset button for 30 seconds, none of which seems to have made any difference.
I have asked about this issue in the #help IRC channel (on EFNet) and been told that there is an issue with this particular model of router over-heating (didn't even know this would be possible) and apparently this causes the wireless to cease functioning.
This leads me to my question(s);
1. It should be under warranty, since it was only bought in February 2008, is this correct?
2. We no longer have the box for the router. Can it still be returned under warranty?
3. Would the replacement for the router have to be the same model? (it looks from the website like this model was discontinued)
I have looked at the RMA page on linksys.com, but I am not sure if you are supposed to get an RMA number before filling out that form, if you are supposed to ask permission on the forum (or somewhere else maybe) to actually request an RMA number or if you need to get the RMA number before even going to that page... could someone please explain this for me?
Thanks

Here are my answers:
1. I think it's still within warranty because WRT300N like the old G routers has a 3-year warranty period.
2. It's okay if you don't have the box anymore as long as you still have the serial number (can be found on the sticker under the device itself). Linksys verifies the warranty basing on the serial number.
3. Contact Linksys tech support. They're will give you the go-signal if the device is qualified for a replacement and will give you the RMA number that you will need in filling out the RMA form. And I think the replacement will be of the same model and version number.
Follow your heart, not your mind, coz there's a saying that goes.... NEVERMIND.

Similar Messages

  • Wrt350n wireless issues

    Ok so I went out and bought a wrt350n, i take it home hook it all up WIRED to my pc(s) and everything works dandy, couple days roll by and my roomate keep telling me he gets randomly disconnected on his laptop, i decided to just ignore him thinking he had to of made an error on his comp. I go to play xbox-live today(i use the wireless adapter) and i keep getting disconnected at random as well. Ive already updated the firmware to 1.03.whatever yet i still get this problem.
    I looked around on the net and found someone who said it might be a security issue but ive got no idea how to fix it, I hope this isnt a stupid issue thats been answered billons of times. Thanks in advance for any help.

    I registered just to tell you THANK YOU. My router had been working fine for 2-3 years, when suddenly the wireless went out none of the laptops in the house could get online. I had it down to either the router was going bad or something was horribly wrong with the internet all over the world
    Ihave been muddling with computers for20 some odd years, and have a degree in IT with emphasize on networking and spent 3 hours trying to figure it out. my wife is a FB addict and I love games and such so she was pretty much ready to go charge another router. One I hate the new style of routers (linksys) out there and I only use linksys (cisco loyal ) products.
    I spent some time searching and after reading your post I had it fixed in under 5 minutes. So again just a quick note to say thanks for the help and possibly to clarify a couple of things.
    When you switched the channels you are dodging a lot of the "traffic" out there from new users that just set it and forget it yes?
    WHat exactly did the other settings do to help alleviate the problem?

  • Wireless Issue

    Hi, I'm having what is turning out to be a common issue for iPod Touch users after the 3.1.1 update. I have a 1G 32gb iPod Touch that is no longer able to sustain connections to any wireless network since I updated to 3.1.1. I didn't want to post earlier (because I wanted to try all the solutions I have seen posted here and elsewhere first) but I'm hoping the intelligensia here can help me with this problem.
    Wireless issue: When I try to log on to any network with my touch, it will either not connect automatically at all (although it can certainly see the network - the SSID is broadcast at least in my home), or it will automatically appear to be connected, but no data can be downloaded from the network - there is only the "cannot download from server" message (in Mail) and a neverending "connecting..." circle (in Safari and most other apps).
    I have my router running a mixed network, with WPA encryption, with the latest firmware and still nothing but the impression that the touch has detected the network but can't log on. Sometimes there seems to be a short period where it is able to download something (i.e. I will get an email in my inbox that consists of a title only, with the message "content not downloaded from server") but this is fleeting (less than 5-10 seconds at a time).
    I have cycled, restarted, restored and upgraded the firmware on my router (both with and without security) and nothing seems to have helped on this end, and other computers, both Mac and PC, are able to log on to this network.
    I have renewed the lease of the network, reset the network settings, disabled-enabled the WiFi, restored the iPod and performed every trick on the touch that I can think of or read about here. Nothing helps. I am not having the problem in terms of sensing reduced sensitivity to networks that some people here are mentioning, but I am not able to log on to any network I've tried (so far, 3 private, 5 commercial).
    I don't want to assume its some kind of technical problem with update 3.1.1, but that's the only thing I can think of, with all of the similar complaints posted around the net and the fact that this wasn't an issue a few weeks ago.
    Does anyone wiser than I am have any useful suggestions?

    Scott Campbell sounds like they 'said':
    > JFYI: Fresnel zone != LoS
    > So you can have a clear line of sight but still encroach on the
    > fresnel zone.
    >
    > When the links drop take a look at airview(?) IIRC that is the tool
    > built in to airOS which will show noise across the frequency. You'll
    > need to do so before hand (it will cause a drop in the bridge) and
    > monitor during the event but if you suddenly see a burst of noise
    > you'll have an answer.
    >
    > You may need to do it from one end for one event and then the other
    > end to get a picture as to what is happening.
    >
    > Or, for the sake of a hundred bucks you could replace the kit at both
    > ends and see if that solves the problem. If it doesn't then you know
    > you probably have something at one of the sites generating noise...
    So my response to Scott's comment is...
    Thinking it was STP enabled on the APs.....<smacks forehead>
    Will know for sure Monday morning.
    Stevo

  • THis Wireless Issue is a Head Scratcher

    As some know, I bought 2 Macbooks in Dec '06 and was experiencing all sorts of wireless issues early on. Dropped connections, SLOW transfer speeds while networked to my Imac, etc.
    At some point Netgear released new firmware for the 824, and all seemed right in the wireless world for at least 2 months.
    No issues with OS updates or airport updates, it seemed.
    Al of a sudden last week, I went back to the extremely slow speed when networked from the macbook (wireless) to the iMac G4 800 (wired) and nothing so far will fix it.
    The wireless transfer happens in 500K packets and a 4 meg file takes 4 minutes to transfer. Yet if I plug in the ethernet cable to the macbook - it works as it should.
    What I can't figure out is what happened to make this annoying issue return out of the blue.
    I am also back to slow page loads via Safari and page hangs.
    Of course I have rebooted the router -
    I can't figure out why for at least 2 months everything worked perfectly after months of sub par wireless performance and then back to **** - with everything back to sub par except not dropping connection anymore.
    Thoughts?

    I think the first thing I'd check for is if some source of interference returned after a few months of absence. I have a 2.4 GHz cordless phone that will nuke my 2.4 GHz WiFi connections - but only sometimes - when the phone happens to pick a channel that coincides with my WiFi. It could well be that a phone in your neighbor's house gets on your channel, and if the the phone doesn't experience any trouble may sit on your WiFi channel for a long time. In my case, my Panasonic phone bothers the WiFi, but the WiFi never bothers the phone.
    The other thing you might want to look for is how many IP packets are being discarded by your Mac's network interface. You can do that my opening a terminal window and doing "netstat -s | more" The -s option gets you a rather extensive list of Ethernet statistics. What you want to look for is anything related to retransmitted packets. If you are experiencing more than a 1% IP packet loss, Ethernet performance can degrade rather ungracefully. (Note, I'm talking about layer 3 and above IP packets). It isn't unusual for 15-20% frame loss at layer 2 in the WiFi connecdtion.
    There are a lot of variables here, and it is difficult to give you an answer that would be a one-step magic pill. There could be several problems at once. The best test would be: does one computer have lousy web page load times over WiFi, but the other computer has quick web access.
    If both computers are having problems loading web pages, then there is something wrong with the router and/or WiFi interference. If just one computer has poor performance, then you need to look at the software on that computer.
    Best wishes for finding it.
    Bill

  • New MacBook Pro 13 i5 Wireless Issues.

    I got the new MacBook Pro i5 2.3 the day it came out. So maybe a week and half ago.
    I`m having intermittent wireless issues. I have done some testing and even replaced my older AirPort Base Station with the new Dual-Band one, but still seeing a drops from the network. I have a ping going to my router and to the ABSE. I tried changing the channel and using 5GHZ or 2.4GHZ. I also have a AirPort express and seen similar results. I tried reseting the PRAM, repairing permission, I did not reinstall the OS but I dont see how this would help. I think there is a hardware issue with the wireless card/antenna.
    I did upgrade RAM and HDD was changed to SSD (intel G2 SSD). There are no other issues, machine is fast, no lock ups. Other devices on the network do not seem to drop any connections (ATV, ATV2, iPhone4, iPad etc..)
    The network drop outs are short but are noticeable and if a ping is going I can see the drops
    *-- 192.168.1.1 ping statistics ---*
    *1527 packets transmitted, 1505 packets received, 1.4% packet loss*
    *round-trip min/avg/max/stddev = 0.779/12.203/396.084/42.274 ms*
    Any help is appreciated as I`m really frustrated but this issue.

    Here are some of the pings.
    +*64 bytes from 192.168.1.3: icmp_seq=2190 ttl=255 time=1.138 ms*+
    +*Request timeout for icmp_seq 2191*+
    +*Request timeout for icmp_seq 2192*+
    +*64 bytes from 192.168.1.3: icmp_seq=2193 ttl=255 time=1.701 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2194 ttl=255 time=1.653 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2195 ttl=255 time=1.723 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2196 ttl=255 time=1.470 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2197 ttl=255 time=1.435 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2198 ttl=255 time=1.217 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2199 ttl=255 time=1.115 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2200 ttl=255 time=1.433 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2201 ttl=255 time=1.002 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2202 ttl=255 time=1.057 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2203 ttl=255 time=1.222 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2204 ttl=255 time=0.769 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2205 ttl=255 time=0.821 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2206 ttl=255 time=0.723 ms*+
    +*Request timeout for icmp_seq 2207*+
    +*64 bytes from 192.168.1.3: icmp_seq=2208 ttl=255 time=54.892 ms*+
    +*Request timeout for icmp_seq 2209*+
    +*Request timeout for icmp_seq 2210*+
    +*64 bytes from 192.168.1.3: icmp_seq=2211 ttl=255 time=1.313 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2212 ttl=255 time=0.936 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2213 ttl=255 time=1.839 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2214 ttl=255 time=0.879 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2215 ttl=255 time=63.446 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2216 ttl=255 time=24.384 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2217 ttl=255 time=105.923 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2218 ttl=255 time=41.322 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2219 ttl=255 time=1.853 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2220 ttl=255 time=0.811 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2221 ttl=255 time=0.721 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2222 ttl=255 time=0.791 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2223 ttl=255 time=3.816 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2224 ttl=255 time=1.052 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2225 ttl=255 time=0.688 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2226 ttl=255 time=89.272 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2227 ttl=255 time=49.459 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2228 ttl=255 time=15.891 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2229 ttl=255 time=0.745 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2230 ttl=255 time=0.724 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2231 ttl=255 time=0.680 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2232 ttl=255 time=1.950 ms*+
    +*64 bytes from 192.168.1.3: icmp_seq=2233 ttl=255 time=0.600 ms*+
    +*Request timeout for icmp_seq 2234*+
    +*64 bytes from 192.168.1.3: icmp_seq=2235 ttl=255 time=0.725 ms*+

  • If you have a Blue Screen / Error due to Wireless issues (B110a), fix in here.

    For the original thread created by somebody else, please see here:
    http://h30434.www3.hp.com/t5/Printer-All-in-One-In​stall-and/B110a-network-connection-problem/m-p/319​...
    Here's a youtube video of what happened to me: http://www.youtube.com/watch?v=adE1kq36ld4
    I'm reposting it here so it can hopefully help some of you guys if anybody else stumbles across this. In short, my printer was fresh out of the box and I attempted to connect it to the wireless network. It would throw a blue screen on the LCD with an error of B8126AD6.
    I narrowed it down to an issue with DHCP. For some reason the printer connects to the wireless access point but as soon as it tries to get an IP address from the DHCP server it crashes with that blue screen and the error code in the first post above. This look like a massive bug in the printers firmware! For reference my router is a Billion 7401VGPR3 which is acting as my default gateway and DHCP server. I have a Linksys WRT54G as my Access Point for the house. 
    To solve it, I turned DHCP off on my router and then tried connecting the printer to the wireless network. This time it connects fine but you still can't talk to it because it doesn't have a proper IP address. If it still doesn't connect properly, try turning WPA/WPA2/WEP off on your Access Point. Leave it completely open for a moment until you can reach the web interface (as below). 
    To fix the IP issue, I then went into the Settings menu on the printer and printed the "HP Network Configuration Page". Note that under the Wireless menu option there are a couple of different "Print Network Test Page" options. I believe it's the 2nd one that I selected. You'll know you have the right one when it prints out the page with the following info:
    IPv4 IP Address
    Subnet Mask
    Hostname
    Default Gateway
    Primary DNS
    etc, etc.
    Take note of the IP Address from the printout above and the Subnet Mask. My IP was 169.254.73.5 and subnet mask 255.255.0.0. Now I manually configured my computers IP address to be similar (within the same subnet): 169.254.73.10 with the same subnet mask.
    Now you can load up the web interface of the printer using http://169.254.73.5 in my case. (You should also be able to ping the printer at this point too). In here you have a Network tab where you can now manually set the IP Address of the printer. Set the address you want it to be in your network (in my case 192.168.0.3 with a subnet mask of 255.255.255.0 and default gateway 192.168.0.1 and dns server 192.168.0.1).
    Once I clicked OK I changed my PC's IP back to normal, and I can now reach the printer on its IP address set above. YAY!
    The great thing is, in the web interface you get a million more options to play with. You can manually set the IP address, gateway, DNS, wireless settings such as WPA1/WPA2 AES/TKIP Encryption, WPA Passkey, etc. So if you had to set the Access Point to completely Open, setup the encryption again and put the passkey in here. When I did this I had to go back into the Settings menu on the printer LCD and select "Disable Wireless" then "Enable Wireless" to force it to re-join the network.
    Finally I went into the Settings menu again and Updated the software on the printer. I don't know if the new software fixes the bug or not - I haven't tested it (can't be bothered!).
    Hopefully this will help some of you guys out there too!
    EDIT: I've just stumbled across another couple of posts with similar results to mine:
    - http://h30434.www3.hp.com/t5/Printer-networking-an​d-wireless/How-to-install-Photosmart-B109n-z-on-a-​...
    - http://forums.techguy.org/networking/627989-hp-698​0-printer-wireless-problem.html

    Many thanks to gardz for an exhaustive overview on this critical problem with the B110a printer!
    I am happy to report that I have managed to set the printer to a static IP and am now able to connect to it wirelessly from my home computers, and also able to use the web apps and ePrint features on the printer. The printer shows the IP address and I am able to use the EWS (Embedded Web Server) to connect to its IP address from my PC's internet browser. The Wireless Network Test Report also showed no problems. I have also completed the Product Update on the printer, and there are no more pending updates now.
    However, the core wireless problem is still not satisfactorily resolved.
    I get the BSOD and blinking-lights error ("Please turn off printer and then on"), only if I start the printer when Wireless is enabled on the printer. If wireless is disabled prior to printer boot, there is no error. 
    The workaround I have adopted for now, is to always switch off the printer's wireless, before switching off the printer, and enabling the wireless setting only when I need to print/scan.
    Is this happening with anyone else? Why would the printer crash if it boots with wireless enabled? If it is already set to a static IP, why would it still conflict with the DHCP on the router?
    My router is perfectly working, it is in the same room as the printer, so the signal strength is good. The printer itself is quite stable except for this crash-after-boot-if-wireless-was-enabled issue on the printer.
    I made the mistake of connecting the USB cable to my primary computer before installing the printer drivers, so even the USB option is not working (Windows recognizes the printer as an unknown USB device). If anyone can point me to the printer drivers (inf files), I would be grateful. The CD does not have the driver files in a convenient location. It seems to be embedded within the setup package somewhere.
    Gardz and PrintDoc, I hope you can help us out on this one. I know many B110a users are struggling with the wireless issues, so HP needs to release a firmware fix and driver update soon. Wireless ought to work out-of-the-box, as this product is aimed at the SOHO users.

  • Is anyone else having email problems such as apps exiting in the middle of an email? It may be a wireless issue. I use First Class for work and yahoo email for personal. I will be in the middle of typing a long email and the app just quits, all data lost.

    Is anyone else having email problems such as apps exiting in the middle of an email? It may be a wireless issue. I use First Class for work and yahoo email for personal. I will be in the middle of typing a long email and the app just quits, all data lost.

    Have you tried restarting or resetting your iPad?
    Restart: Press On/Off button until the Slide to Power Off slider appears, select Slide to Power Off and, after the iPad shuts down, then press the On/Off button until the Apple logo appears.
    Reset: Press the Home and On/Off buttons at the same time and hold them until the Apple logo appears (about 10 seconds). Ignore the "Slide to power off"

  • I have had wireless issues sense Leapord, any fixes yet? its a shame that my wife has to sit in front of our 27 inch imac on a $300 Windows computer to use the web effectively. I have tried all fixes  and some work while others don't but all temporary

    This Lion wireless issue has become more than just an irritation, so much so, my wife has resorted to sitting in front of a 27 inch imac with a 300 dollar Walmart Windows computer to get the bills paid and use the web. And yes, there is not a fix out there I haven't tried over the last year or so, some worked and some didn't, but all were temporary at best. Same issue with my Macair, I wonder if its a hardware issue, like the video card in my 2006 MBP, it went out after the warrenty and then I found out there was a calss action suit going on over it, unfortunately Apple wouldn't cover it and wanted 7oo bucks to fix it, sold that as parts.
    While i really like me Macs, I own three, I may have to bow out and stick with LINUX, that has yet to let me down, anyone know if Mountain will fix this issue? or are we all just waiting for defective WiFi cards to fail at our own expense, PS, got three Macs for sale.

    Sounds like you're getting kernel panics, which are usually, but not always, caused by hardware problems, with memory being one of the regular culprits.
    First thing I would do is to get our your original OS X disks, insert the first one (should say 'AHT version x.x' in small print on the label - if not, find the one that does), and reboot holding the Alt key down. Choose the Apple hardware test, and when prompted, choose the extended test. If you have either of the TechTool programs, they can do similar testing. Does that identify any hardware issues?
    Next, I'd download rember from http://www.kelleycomputing.net/rember/ . This is a memory testing program that you can set to run overnight. Does it come up with any errors? If so, try resetting your memory card(s) by removing and putting back into the computer. Rerun memory test.
    This FAQ will provide other details: http://www.thexlab.com/faqs/kernelpanics.html

  • This is a workaround for the MBP wireless issue

    There have been many topics on the MBP wireless issues already, but I thought some people might find this workaround helpful.
    Firstly, my system is a 2.2Ghz MBP, running 10.4.10, and also airport extreme update 2007-04. I am using an airport express base station. My previous Powerbook never had any wireless problems, so I really couldn't blame the basestation for the MBPs poor wireless.
    Warning - The workaround requires a little bit of work in the terminal. A little bit of understanding of how networks work is assumed here as well. So it is probably not for everyone ...
    What I have observed - whenever the MBP loses connection, the airport basestation IP and MAC addresses are missing from the ARP table.
    - To view the ARP table, type (in a terminal window) arp -a.
    So, when the MBP wireless hangs, open up the terminal and type that in.
    Do a Cntrl-C if the arp command is hanging and not returning anything.
    In normal situations, a list of IP addresses and MAC addresses will show up.
    As others have already noted, clicking on the airport icon in the menubar, will magically bring the wireless back to life. When this happens, the ARP table also gets magically populated correctly. Coincidence? I think not!
    So, the workaround is to store a PERMANENT entry in the ARP table for the airport basestation IP and MAC address. In my case, I can use the Airport Utility software to confirm what the basestation IP and MAC addresses are (note MAC address = Airport ID in Airport Utility). I found the basestation IP=10.0.1.1 and the MAC=0:11:24:07:d7:f
    To create a permanent ARP table entry for my airport basestation, I opened up a terminal window, and did the following -
    1) login to my administrator account
    2) type in the following command sudo arp -s 10.0.1.1 0:11:24:7:d7:f
    3) type in my administrator password to authorise the change
    4) type in (to confirm the changes have been made) arp -a
    5) logout of my administrator account (from the terminal)
    Ever since I did this, my MBP wireless performance has been flawless.
    Note, if you shutdown or restart your computer, the arp entry disappears. This is ok for me as I hardly ever power down my MBP. As insurance I have added an account startup item to remind me to do the arp table entry.
    This workaround is great for me because I don't have a need to use multiple wireless networks. It might not be practical for people who roam around onto different networks.
    Give it a go and see if it works for you.
    Message was edited by: michael louey

    OK, after some further experimenting, I changed the multicast rate on my airport express. It was set at 6Mbps, and I changed it to 2Mbps.
    I have read that the default multicast rate for previous 802.11g versions of Airport basestations is actually 2mbps. Excellent results so far !! I have set up a terminal command to continuously ping my airport router address every 15 sec, and there have been virtually no dropped packets so far over many hours.
    ping -i 15 10.0.1.1
    Interestingly, in Apple's Airport Admin software in my MBP there is no option to set the rate at less than 6Mbps (!!!!), so I had to use the Windows XP version of Airport admin software to make this change using a windows machine. Using the XP software you can set the muticast rate as low as 1Mbps.
    If you are using Apples airport admin software (Tiger and Leopard) and you commit any sort of change in settings, the multicast rate will be re-set at a minimum of 6Mbps. My understanding of the multicast rate is that setting it too high is similar to shrinking the coverage area of the basestation, and limiting access only to clients who can transmit at the required multicast rate.
    So my new theory is that the dropouts are caused by the MBP dropping off the airport due to not being able to achieve the set multicast rate. (this could be due to factors such as low signal strength, excessive interference or noise).
    If you are using Apples more recent Airport admin software, you are having a minimum 6mbps muticast rate set, and this might be too high for your particular environment.
    Just a theory.
    (oh yeah, I enabled interference robustness on the MBP and the basestation just for good measure)

  • Macbook Pro (Late 2008) - Windows 7 64-bit, Bootcamp 3.1 - Wireless Issue

    Hi Everyone,
    I have a Macbook Pro (15-inch, Late 2008) model with Snow Leopard and Windows 7 64-bit dual boot. I have done a search and cannot find any reference to this problem on my hardware.
    I have had no issues in Windows 7 when using Bootcamp v3.0. In the last week I have upgraded to Bootcamp v3.1. (completed twice, rolled back in between to prove that the issues was related to the Apple Update)
    After I update to v3.1, I have issues with my wireless network. The network cannot resolve the name for any internet address. I can connect to wireless networks (tried multiple networks), all the DHCP settings seem to be retrieved correctly (Gateway, DNS etc) and I can ping local and machines outside my network without an issue provided I use the IP address. (Skype works - which uses direct IPs rather than names I have found over time)
    As soon as I use a name for a destination for Web traffic, Mail, pinging (any application), my Macbook Pro cannot resolve the address and just bombs out.
    If I connect to a wired network, the machine works perfectly and name resolution on that interface works. If I rollback (using Windows 7 rollback capability) to before the v3.1 Bootcamp is installed, the wireless networking also works perfectly.
    I noticed this in the support area at apple:
    http://support.apple.com/kb/TS3196
    But this refers to wireless issues in Bootcamp drivers prior to v3.1 and on 13 inch Macbook. Wonder if this is a similar issue or related?
    Anyone else seen this or point me in the direction of a fix?
    Thanks,
    Thommo

    I'm looking into running Windows 7 64bit on the exact same MBP you have, so I'm curious as to whether or not you've found a solution yet outside of the forums.
    Do you think it might be that the bootcamp 3.1 update is only for Windows 7 32bit and not for the 64bit version?

  • MacBook wireless issue (ongoing) & DIY airport card replacement

    Hello,
    With reference to the ongoing MacBook/OSX (10.5.3) Leopard intermittent wireless issues discussed in this forum has anybody gone ahead and taken matters into their own hands and purchased and installed a new Airport card for their MacBook from www.ifixit.com?
    Further details at: http://www.ifixit.com/MacBook-Parts/MacBook-Core-2-Duo-Santa-Rosa-Penryn-802-11n -Airport-Extreme-Card/IF186-062
    If so, did it resolve your intermittent Airport issues?
    It seems to me that when the MacBook is running on battery power only the Airport card does not realise that the MacBook has come out of sleep sometimes and therefore does not always function correctly. Maybe the Airport card does not receive sufficient power when the MacBook comes out of sleep mode whilst running on batteries only?
    Typically when I run the MacBook connected to power the intermittent wireless problem does not occur.
    This issue has been a recurring problem for me for 6 months now and unfortunately I have not seen Apple address this issue.
    My MacBook is 6-months old and is a black MacBook using a 2.2GHz processor running Leopard OSX 10.5.3.
    Cheers,
    treaders

    Visit Apple Store and replaced the Airport card.

  • WRT310N v1 and MacBook Pro wireless issues

    Hi all,
    I've been having ongoing wireless issues with my WRT310N v1. I have a macbook pro (early 2009) with mac os 10.5.8. I have cable internet, with a DHCP connection. I have a computer and PS3 hardwired through the router, and they work flawlessly. The wireless, however, has never been what it should be. Internet loads slow, even though the connection speed is pretty good (not as fast as hardwired devices, but close).
    Here are the wireless settings:
    wireless config: manual
    network mode: mixed (the Macbook can get wireless-n, by iPhone is only g)
    Radio band: standard 20 mhZ
    wide channel: 9 (can't change this with this config, unless i go wide channel at 40 mhZ)
    standard channel: 11
    SSID broadcast: enabled
    I've got WPA2 security, with AES encryption. I've set the Beacon interval to 75, and left the Fragmentation and RTS thresholds at default. The firewall is activated, and "filter anonymous internet requests" is disabled.I'm wondering if I'm losing so much speed by broadcasting a mixed signal, instead of just G or just N. I've tried transmitting only in Wireless-N, but there's no noticeable change (and the iPhone can't connect at all). 
    Any input at all would be really appreciated. I'm hoping I don't have to fork over $30 to linksys just to get tech support. Thanks in advance.
    Solved!
    Go to Solution.

    Well its not necessary to power cycle your router everytime whenever you make any changes on your Router. But if you re-configure all the settings on your from scratch, then its better to power cycle your router.

  • How to set six WRT300N wireless router use the same SSID

    I have six WRT300N wireless router and cannot setting shared the same SSID....
    Somebody can help me?

    please explain like how are you trying to set up these routers..... even if you set up these routers using the same ssid , they won't communicate with each other wirelessly....

  • Is the WRE54G range extender compatible with the WRT300N wireless router?

    I bought a WRT300N wireless router, hoping it would give me better range than my old hub.  It's pretty good, but I still have dead spots in my apartment.  I'd like to buy a WRE54G range extender, but I don't know if it's compatible.  Anyone try this?

    i don't think that the wre54g would work with the n-router .. rather i would suggest you to setup a wap200 or wap54gp wired to the router and configured as an AP ... if it still falls short of the wireless range .. configure another one in a repeater mode ...

  • Is this a dropping connection or a wireless issue....

    Hi all,
    We've been having some problems with our Infinity setup for a few months now and it's getting a bit annoying, I could use some help in fixing it
    So, every evening (could be daytime too, we dont use it then really) our connection seems to drop every 10 mins or so. If I'm gaming, it will drop me out of a game and I'll have to reconnect. I can usually reconnect in seconds. If we're watching Netfilx, it will stop, and restart a few minutes later...
    Oddly, the blue Hub lights (HH3 I believe) never falter, solid blue throughout.
    Restarting the router (and white box thingy) works pretty much everytime - and only occasionally are we disconnected for more than a few minutes.
    The setup is Infinity 2 I think, into the master socket. I'm running a handful of Apple devices, a home server, a Mac and a PS3. Probably important that none of these devices have changed at all location, spec or otherwise.
    Occasionally my server cannot be found on the network either, despite it running continuously - a restart usually cures this but would it point to a dodgy router? (it's a wired connection,so no wireless issue)
    I'm guessing I need to run some tests but not sure what?
    I did try and call BT Support a while ago, but the chap said he couldn't help me because my Mac Air has no ethernet cable, just wireless

    seems to me like a faulty router or modem mate, to make sure its not actually dropping fully you will want to login to the router page using 192.168.1.254 then going to troubleshooting and then helpdesk and it will tell you the uptime. login with the password which should be on the back of your router. do this when the wireless next drops. btw dont keep resetting the white modem, it will cause your speeds to drop as it will think its a line fault, just reset the homehub. if the uptime is less then 2 mins then its dropping fully, if its more than than lets say 1 hour for example (and you reset it one hour ago before the wireless dropped) then its most likely just the router being faulty.

Maybe you are looking for

  • PSD File to Illustrator Vector - How To?

    Hello all, I have searched the web far and wide and can't seem to find any sufficient answer to the issue I'm having, which stems the following; I've created a PSD file in Photoshop with some layers (stock images I've bought and some text), and I'm l

  • How duplicate ora11 on windows to another host with different directory structure

    Hi, I need help. I want to duplicate db (11.2) running on windows from server A to Server B Directory structures on server A and Server B are different; my steps on server A 1.backup database plus archivelog delete input; 2.insert into table t values

  • How to use division with a Where() clause

    I have to report four specific time periods dynamically so I made Date variables. I cannot use division of the metrics without applying the date codes to the individual metrics. There has to be a way I am not thinking of. This is a massive report so

  • System Landscape Directory is not accessible on NW04 Sneak Preview

    Hi, I installed Netweaver sneak preview Full Java edition on a server and when i access the NW administrator at the url http://...:50000/nwa. In "Overview" of system management there are 2 warnings : System Landscape Directory is not accessible and O

  • Hp 5610 officejet all in one

    Hi,  my printer was working fine until an error message came up. The error comes up on the printer screen as Cartridge Error: it then tells me to troubleshoot. I can't find what is wrong, so any suggestions are welcome. Thanks in advance, Lee.