Topic: WeatherLinkIP datalogger not getting IP from Router

[Ed_G]

Installed my new WeatherLinkIP on my VantageVue Console a few days ago.  It is plugged in to one of the Ethernet ports on my home router (ASUS RT-N66U) . I set up my account with WeatherLink.com  and my datalogger is now successfully sending my weather data to my page on that web site.

HOWEVER,  I cannot seem to connect to the datalogger through my home LAN.  The problem seems to be that the Router is NOT seeing the datalogger that is plugged in to it.  Looking at my DHCP page in my router,  the datalogger MAC ID ( DID)  appears no where,  so the Router can not assign it an IP address for my home network.   YET,   the datalogger is successfully connecting to the Internet through my router.

I have discussed this with Davis Technical support and so far they seem  to stumped,  even though their excellent staff has spent substantial time with me on this issue.  I believe I am awaiting further response from an elevated level tech support.

Meanwhile I can't use my WeatherLink software with my weather station.    Has anyone else had problems like this where the WLIP datalogger could not be found on the home network even though it was working properly over the Internet?

I should point out that I have other many devices successfully connected to my router, including laptops,  tablets, remote cameras,  etc.  and none of my other devices, either wireless or LAN connected are having any problems....and no,  I have not come even close to the maximum number of devices my Router can handle.

Any suggestions or comments appreciated.

Ed

[jackman]

Curious indeed. I'd suspect the router. Perhaps it's issuing the IP address to the datalogger but not reporting it in the DHCP table. You might try rebooting the router. Then I'd consider trying a different router. That task may be simple or complex depending your network.

[Ed_G]

I did do a cold re-boot of the Router....to no avail.  Its a late model ASUS  RT-N66U with fairly recent firmware that has provided excellent service the past few months that I have had it.  It does recognized and assign IP addresses to a multitude of computers and devices as they are turned on and off,  so I doubt that the fact that it is not recognizing the MAC address of the new WeatherLinkIP datalogger is connected to the router....but I wont write that possibility off entirely.   Yet,  what could possibly prevent my router from recognizing this one device while it does recognize over a dozen other devices?

Ed

[jackman]

It's hard to diagnose without a better understanding of the network or doing some low level packet sniffing on the network. The datalogger packets are finding their way home to weatherlink.com somehow. If there's a logging capability in the router it may show where outbound packets are originating. I don't have any experience with the Asus product so it's hard to advise you any further.

I gather you already tried finding the datalogger using the WeatherLink software and the DID (MAC) address listed on the connector.

[JACK10562]

It's odd the router doesn't show the weatherlink client IP address, but sometimes when the datalogger IP address is configured statically, then that can explain why you don't "see" it in the DHCP tables. Check the live IP addresses in the DHCP listing under ‘Advanced Settings’. 

You might be able to enable system logging to see what network traffic is going where.

Another thing to try is launch your WeatherLink software, look under Communications Port, select TCP/IP and below that select local Device ID. If WeatherLink successfully finds your dongle, it should be able to connect to it and also display a remote TCP/IP address.

[Ed_G]

Jack,  yes it IS odd that the datalogger MAC address does not show up.  and yes,  I did try assigning it a static IP in my router,  but it was kinda in the blind since the router did not show the device in it's MAC address  table for devices connected to it.   Neither Static IP that I tried nor DHCP IP showed up in the router.  All my other computers' and devices' MAC addresses do show up,  except for this WLIP datalogger.  And  of course that is why my WinLink program doesn't find it either when I attempt to set up the communications settings in that program. 

Regarding system logging in the router ...that is currently beyond my experience.  I will look into that subject tomorrow to see if I can learn anything.

  I keep thinking that it is certainly possible I have a problem with my new datalogger.   My discussions with Davis technical support did not raise that issue.  I am hoping to hear from them again next week....at which time I  may raise that issue.  Maybe they could send me a loaner to try.... or someone else here with an ASUS RT-N66U router that has a WLIP datalogger working properly could pop in here to confirm it should work with the datalogger.

[Aardvark]

Let's try a long shot on this one.  Lets assume the router is fine as you are able to connect to this website, right?

Disconnect the cable from the WL IP.  Replace it with something else.. maybe the cable is bad in the first place, not the first time a cable was toast.

Now  power down your console, first put it into set up, then disconnect the AC power ( you do have the AC hooked up and running, or the electrical. it won't work on batteries with the IP).
Then remove the batteries,  then remove the IP logger.

Then, put back in the IP logger, then the batteries ( it will chirp), then hook up the AC power module.  take the console out of set up mode and wait for it to find your station again .  You might need to make setting correct.

NOW, open your Instruction manual for the IP logger and go through step by step.  However, you are going to do 2 things.. one is to use a different ethernet cable than the one that came with the weatherlink and then if you have the option, plug it into the router in a different port.

http://www.davisnet.com/product_documents/weather/manuals/07395-210_GSG_06510_6555.pdf

Now if that doesn't work, then contact Davis and tell them you bought and have this IP weatherlink that is poached and you will exchange it for a new one by return mail.

Finally, is your router relatively new?   I have an Actiontec Q1000 that Qwest put in years ago (I am guessing maybe 5)  and it works fine,  I would guess if your modem is old, then  that might be a remote issue.

Give this all a try and if you have done it already, do it again...

[jackman]

I've run into similar kinds of problems in my life as an IT guy usually caused by a bug of some kind or corruption in the hardware/firmware of the device in question. As a workaround I would set up a "lab" network using a standalone router configured with the same IP range as your "live" network. You can do this with a cheap router that can be purchased at a Walmart for about $20. It's handy to have a spare so it would be money well spent.

Connect the Davis datalogger/console to the "lab" router along with a standalone PC. A laptop works well for this. You don't need to use the Internet so there's no need to connect the "lab" router to your broadband connection. In other words there's no need to disturb your existing network or Internet connection.

Check the "lab" router DHCP table for the IP address that the router hands to the PC and the datalogger. If the datalogger still does not obtain an IP address then you can suspect a problem in the datalogger and follow up with Davis.

If the datalogger does obtain an IP address use your web browser to connect to the datalogger directly, e.g., using http://192.168.x.x in a web browser and assign a static IP address to the datalogger. You can do this without the WeatherLink software. The static IP address must be on the same subnet as your "live" network. Once assigned connect the datalogger back to the live network and attempt to use the WeatherLink software to finish the configuration by connecting to the static IP address you assigned.

All of this may take more networking skill than you're comfortable with. Another approach would be to take the Davis datalogger and console to a buddy's network for testing.

[d_l]

Can you ping the WLIP with either the DHCP or its assigned static IP?  Can you browse into the WLIP's configuration settings web page?

The above tests would tell you if the router was simply failing to show ther WLIP's connected MAC, but otherwise operating correctly.  It seems that it could be doing that as it is working correctly with weatherlink.com.

I presume that you have tried using the Davis WeatherLinkIP Network Information Utility: http://toolbox.davisnet.com/downloads/Weather/Network_Info/  This is probably the same routine that Weatherlink uses to find the WLIP, but it lists more info than simply not finding it.  Does it report anything unusual?

[hankster]

Have you tried rebooting the router?

[dalecoy]

Have you tried rebooting the router?

It helps to read the discussion - he answered that question in reply #2 above.

[hankster]

Excuse me, I did read the thread but missed that part. Sorry I tried to help. I won't offer my next suggestion since I've seen this before with other equipment.

[dalecoy]

Excuse me, I did read the thread but missed that part. Sorry I tried to help. I won't offer my next suggestion since I've seen this before with other equipment.

I apologize for the offense.  And please do not punish someone else if you have a solution.

[Ed_G]

Please, people,  try not to get upset when someone points out that you missed part of the information before responding with your help.  I appreciate it from all.

Now,  per some of the suggestions recently posted,  I must say I have met with success.  However I don't know why.

I set up my old router ( a Linksys SRT54G ) and a laptop and then connected the datalogger to the old router.   IT WORKED !   It was recognized by the Linksys and assigned an IP.   I then disconnected all, hooked the datalogger up to the new ASUS router.... it did not work.   I was suspecting a setting in my router but decided to repeat this process,  so again hooked the datalogger to the Linksys and it again worked.   Lastly I hooked up to the ASUS router..... but this time it recognized the datalogger and assigned an IP.   I confirmed all was well by connecting to the datalogger from my home computer web browser,  and then with the provided WeatherLink software.  It all works.   

I do not know why my first several attempts with my home router did not work.... perhaps by connecting successfully to the Linksys something was changed or reset in the datalogger?   Don't know but now that it is working I am a happy clam.

Thanks to ALL who provided input to my question.

Ed

[jackman]

I do not know why my first several attempts with my home router did not work.... perhaps by connecting successfully to the Linksys something was changed or reset in the datalogger?

Good show Ed! I suspect a bug in the router. It sure sounds like the router issued the DHCP address but did not record it in the DHCP table. And for whatever reason the WeatherLink S/W was not able to detect the datalogger using the device ID, aka MAC address, which is suggestive of a problem at the switch level of the router.

What I would do to prevent any problems in the future is put a static IP address on the WL datalogger. That way you'll know that you can always access it in the future without the need for router DHCP. I do this on all my important network devices.

Happy weathering and new year!

[Ed_G]

Good idea, Jack.  I will let things sit for a day or three and then do that.   I have static IPs set for my Printer and my three WirelessIP security camera.   Should be easy for the datalogger, too.

Thanks.

Ed

[JACK10562]

If you type the WeatherLink DHCP IP address into a browser window you should get a rudimentary GUI where you can assign the dongle a static address, among other things. Then go into your router and do the same there.

Once you give it a static address it will no longer show up in your router DHCP tables.

[DeKay]

I do not know why my first several attempts with my home router did not work.... perhaps by connecting successfully to the Linksys something was changed or reset in the datalogger?

Good show Ed! I suspect a bug in the router. It sure sounds like the router issued the DHCP address but did not record it in the DHCP table. And for whatever reason the WeatherLink S/W was not able to detect the datalogger using the device ID, aka MAC address, which is suggestive of a problem at the switch level of the router.

Ed, you might also want to try installing alternative firmware on your router.  I like Tomato by Shibby.

[Andy Thompson]

Back in January of 2009 when I first got started with the computer stuff, the problem I had was that the data logger wasn't seated in there correctly. Even though when I would plug it in and it felt like it went into place, I had to push it in even harder and then it would finally work. Don't know if this helps, but that was my first experience with it.

[Ed_G]

Jack,  I already set my router to assign a static IP to the datalogger this morning.   Next time I re-boot the router,  this should happen.  Perhaps I'll go into the datalogger directly with my browser as you suggested and do that...not sure it's necessary in this case.

DeKay,  My router is quite a late model... this year, I believe,  and according to a number of sources I checked,  it's the highest rated one in most catagories.   The Firmware has been updated last month and quite frankly,  I don't know why anyone would want to change it to Tomato firmware.  ASUS is doing a superb job with their own product.   I did install HyperWRT in my old Linksys,  and that certainly was well worth it,  but not in this new unit... at least as far as my needs go.

Incidently,  in the Router section where I can assign static IP addresses to devices,  it does show the MAC addresses of all devices connected,  so I don't have a problem 'losing'  the IP address, static or dynamic,   as is the case in other routers.  This router shows the static IPs and associated MAC addresses too.   This info is how I knew there was a problem with my router connecting to the datalogger in the first place.  No MAC address showed up.

All is still well.

Ed