• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1636
  • Last Modified:

netgear prosafe wg103 disconnecting

Hi i have 2 netgear prosafe wg103 i have created point to point connectivity with my remote office across the road , it was working fine but suddenly it start getting less signals and disconnecting in between
is there any new release of firmware for the same ?
kindlya dvice
0
sanjeevkmrs
Asked:
sanjeevkmrs
  • 6
  • 4
1 Solution
 
sanjeevkmrsAuthor Commented:
how can i see the current firmware installed ?
0
 
g8kbvCommented:
Chances are something else has appeared using the same or close by radio frequencies.

There are "Lots" of other things that use the 2.4GHz spectrum, and most will seriously mess with WiFi.  Has anyone else local to you recently installed a new security system, wireless video surveylance cameras, another WiFi system?  The list is long!

Take a bit of time and read this:-
http://preview.tinyurl.com/p9d2vs

(Goes to:-
http://www.cisco.com/en/US/prod/collateral/wireless/ps9391/p
s9393/ps9394/prod_white_paper0900aecd807395a9_ns736_Networki
ng_Solutions_White_Paper.html)

Then work through things methodicaly, see what you can discover.

Regards.

DaveB
0
 
g8kbvCommented:
PS:  Sorry, forgot...

It's worth first checking your own premises for new 2.4GHz wireless gadgets (phones etc).   Also, is anything like a "Wall Wart" power uint for one or other APs started running hot.  That could indicate trouble.  Any suitable regulated 12VDC power unit capable of running at 1.2A or more should do the job, but check the polarity and type of DC connector.  I see from the data sheets, they can use PoE for power.  If your using that, check all the cable connections, as well as the power injection device etc.

As to the AP's firmware versions,  You need to log into their administrative page via the wired LAN I suspect.  That should tell all you need to know in that respect.  Of course, you did make a note of the admin user login details for each of them, didn't you?

DaveB
0
Who's Defending Your Organization from Threats?

Protecting against advanced threats requires an IT dream team – a well-oiled machine of people and solutions working together to defend your organization. Download our resource kit today to learn more about the tools you need to build you IT Dream Team!

 
g8kbvCommented:
PPS:  !!

Product support page from Netgear. for the WG103

http://kb.netgear.com/app/products/model/a_id/8123

Including documentation and firmware if needed.

DaveB
0
 
sanjeevkmrsAuthor Commented:
please see the logs i have copied from the netgear which is connected in my main office with lan and connecting accross the road with another netgear

20:50:01 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:50:06 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:50:11 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:50:16 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:50:21 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:50:26 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:50:31 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:50:36 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:50:41 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:50:46 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:50:51 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:50:56 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:51:01 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:51:05 kernel: DEBUG!!! ath_inact 3434 No Free MMPDU for last 10 sec....reset
Mar  3 20:51:11 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:51:16 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:51:21 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:51:26 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:51:31 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:51:36 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:51:41 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:51:46 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:51:51 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:51:56 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:52:01 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:52:06 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:52:11 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:52:14 kernel: DEBUG!!! ath_inact 3434 No Free MMPDU for last 10 sec....reset
Mar  3 20:52:21 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:52:26 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:52:31 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:52:36 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:52:41 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:52:46 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:52:51 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:52:56 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:53:01 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:53:06 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:53:11 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:53:16 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:53:21 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:53:26 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:53:31 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:53:36 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:53:41 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:53:46 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:53:51 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:53:56 kernel: DEBUG!!! ath_inact 3434 No Free MMPDU for last 10 sec....reset
Mar  3 20:54:01 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:54:06 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:54:11 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:54:16 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:54:21 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:54:26 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:54:31 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:54:36 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:54:41 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:54:46 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:54:51 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:54:56 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:55:01 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:55:06 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:55:11 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:55:16 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:55:21 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:55:26 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:55:31 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:55:36 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:55:41 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:55:46 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:55:51 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:55:56 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:56:01 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:56:06 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:56:11 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:56:16 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:56:21 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:56:26 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:56:31 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:56:36 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:56:41 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:56:46 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:56:51 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:56:56 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:57:01 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:57:06 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:57:11 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:57:16 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:57:21 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:57:26 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:57:31 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:57:36 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:57:41 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:57:46 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:57:51 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:57:56 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:58:01 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:58:06 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:58:11 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:58:16 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:58:21 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:58:26 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:58:31 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:58:36 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:58:41 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:58:46 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:58:51 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:58:56 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:59:01 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:59:06 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:59:11 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:59:16 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:59:21 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:59:26 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:59:31 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:59:36 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:59:41 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:59:46 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:59:51 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 20:59:56 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:00:01 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:00:06 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:00:11 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:00:16 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:00:21 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:00:26 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:00:31 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:00:36 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:00:41 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:00:46 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:00:51 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:00:56 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:01:01 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:01:06 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:01:11 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:01:16 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:01:21 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:01:26 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:01:31 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:01:36 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:01:41 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:01:46 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:01:51 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:01:56 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:02:01 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:02:06 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:02:11 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:02:16 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:02:21 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:02:26 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:02:31 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:02:36 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:02:41 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:02:46 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:02:51 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:02:56 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:03:01 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:03:06 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:03:11 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:03:16 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:03:21 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:03:26 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:03:31 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:03:36 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:03:41 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:03:46 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:03:51 kernel: NETDEV WATCHDOG: wifi0: transmit timed out
Mar  3 21:03:56 kernel: NETDEV WATCHDOG: wifi0: transmit timed out

kindly advice
0
 
sanjeevkmrsAuthor Commented:
also i would like to ask that do i need a very clear vision of both the devices ? as these devices are behind the glass walls and one side having curtain in between
please advice
0
 
sanjeevkmrsAuthor Commented:
Hi g8kbv:
                 please advice
0
 
sanjeevkmrsAuthor Commented:
can i have a settings and step by step configuration of both my netgear prosafe wg103 devices to configure it as point to point .
please advice
0
 
g8kbvCommented:
Hi, sorry for the delay, I've been working some 200 miles away, and the hotel wifi was so restrictive the only thing you could do was surf "ordinary" websites, and slowley too, mobile internet access was rubbish too, out in the sticks..

It might be worth you at firat looking on Netgears user forum for this device, and see if anyone else has had similar troubles.  You can find that from either of the two links I already posted.

I think if you are seeing kernel debug messages in the logs (Is it juse one with this in the logs, or both?)  A firmware update to both devices could be in order, again the Netgear site has all the info you need to do that.

First try a factory reset (little button on the back behind a hole) but you'll need to re-configure them with your settings afterwards, but if they spring back to life for a while, then fail again, definately update them.

Just make sure that when you re-configure them afterwards, you make a note of the settings you use, even make a backup of the config files (I assume you can do that from the admin/config web UI, like their routers.)  Those files are Linux format text files, so you can examine them later if needed.

As they were working OK, then suddenly appeared to fail, it'd still be worth trying to do a WiFi survey, even with something like NetStumbler (google it) on a PC, though that will only "see" WiFi signals, not other interference.   For other interfenerce, you'd need some sort of spectrum analyzer, many 1000's of $ for an "instrument" but there are some WiFi spectrum sniffer dongles about for a few 10's of $ that can show you much the same.

I can't help much more now, until Tuesday at the earliest, I have a very busy weekend coming up, and nothing to do with computers I hope.

All the best.

DaveB
0
 
sanjeevkmrsAuthor Commented:
Thanks
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now