Wireless problems

Discussion in 'Wireless' started by Phoenix, Jun 6, 2004.

  1. Phoenix
    Honorary Member

    Phoenix 53656e696f7220 4d6f64

    5,749
    200
    246
    Today i post a question! :)

    I have a Linksys WAP54G Access point that supports 802.11b and g
    now yesturday i had it working but it ceeased to work half way through the day, today i can access it from the wireless side, but not the wired side, meaning i cant reach the router and hence the internet
    the default gateway is set up correctly, but i cant ping the device from the wired network, and cant ping the wired network from the wireless laptop
    i have changed cables/switches and reset the config on the device and started again, to no avail

    any help would be appreciated :)
     
    Certifications: MCSE, MCITP, VCP
    WIP: > 0
  2. tripwire45
    Honorary Member

    tripwire45 Zettabyte Poster

    13,493
    180
    287
    Hmmmm. A couple of things come to mind. One is that the wired port on the AP has gone bad but that's a little rare. I don't know about the configuration of this device but are both wireless and wired access to the AP done on the same subnet using the same IP address? It sounds like signal routing is not making it from the wireless to the wired network.

    The AP controls should be accessable through a web interface. Can you access it at all and see the settings. If all else fails, there should be a reset button on the AP that will return it to it's default settings (SSID, IP address, logon and password). From there, you should be able to access it and reconfigure it.

    That's about all I can come up with off the top of my head, "neighbor". :)
     
    Certifications: A+ and Network+
  3. Phoenix
    Honorary Member

    Phoenix 53656e696f7220 4d6f64

    5,749
    200
    246
    nope can still access the config and stuff, even reset it a few times to try and fix the problem
    wired port lights up correctly when plugged in
    and as its an AP it works at the MAC layer not the IP layer so no routing required, its more like a switch really

    only reason it has an ip is for config stuff, beats me, ill have another play around see what i can come up with
    worked yesturday thats what bugs me the most lol
     
    Certifications: MCSE, MCITP, VCP
    WIP: > 0
  4. tripwire45
    Honorary Member

    tripwire45 Zettabyte Poster

    13,493
    180
    287
    I hate intermittent problems. Thought maybe you had a wireless router which is why I suggested the IP address check. Make sure all the security (WEP, MAC address filtering, etc...) is turned off. It shouldn't affect the wired connection but you never can tell. The only other thing is to make sure that your laptop is on the same subnet as your wired computer(s). Regardless of what an AP does, if they are set to different subnets, there won't be contact between the wired and wireless network nodes.

    Wireless is still half magic so a lot of times all you can do is to play around with it. If nothing else works. Reset the AP and start building the connection from scratch including deleting the wireless connection. Go through (assuming Windows 2000 or Windows XP) the network connection wizard again...you never know. Sometimes a connection goes bad for unknown reasons.
     
    Certifications: A+ and Network+
  5. Jakamoko
    Honorary Member

    Jakamoko On the move again ...

    9,924
    74
    229
    Ain't that the truth, Trip, but at work, when I tell Users that over the phone, do they believe you ? :eek:

    Same for uninstall and re-install the hardware - they refuse to believe that this possibly be the cause of their problems !!! :eek:

    I'd reckon it fixes at least 50%, which ain't bad going !
     
    Certifications: MCP, A+, Network+
    WIP: Clarity
  6. AJ

    AJ 01000001 01100100 01101101 01101001 01101110 Administrator

    6,897
    182
    221
    Fair point Gav but there's a lot to be said for a good old fashioned restart.

    If hardware is 50% then a restart has got to be the other 50% :D
     
    Certifications: MCSE, MCSA (messaging), ITIL Foundation v3
    WIP: Breathing in and out, but not out and in, that's just wrong
  7. Jakamoko
    Honorary Member

    Jakamoko On the move again ...

    9,924
    74
    229
    I agree AJ - I should have maybe said that I assume a restart has been done, prior to recommending the above :wink:

    Anyway, at the risk of incurring Trip and Phoenix's wrath ... :offtopic

    :oops:
     
    Certifications: MCP, A+, Network+
    WIP: Clarity
  8. tripwire45
    Honorary Member

    tripwire45 Zettabyte Poster

    13,493
    180
    287
    WRATH!!! :x :lol: :wink:
     
    Certifications: A+ and Network+
  9. Nelix
    Honorary Member

    Nelix Gigabyte Poster

    1,416
    3
    82
    I had a similar problem a while back and could I get it to work, could I heck. after about 4 days of trying to fix the problem I discovered that for some reason Zone Alarm had started to refuse connection to the wireless router.

    Just a though, try disabling your firewalls and see if that helps.
     
    Certifications: A+, 70-210, 70-290, 70-291, 74-409, 70-410, 70-411, 70-337, 70-347
    WIP: 70-346
  10. tripwire45
    Honorary Member

    tripwire45 Zettabyte Poster

    13,493
    180
    287
    Zone Alarm, of course. Not that this has to be the answer but I have had troubles in the past when I have added a new node to a small network forgetting the Zone Alarm was in place. I had to add the name and IP address of the new computer to each device running Zone Alarm as "trusted" in order to get it to connect.
     
    Certifications: A+ and Network+

Share This Page

Loading...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.