Thanks wuhu_software,

I'm looking in that folder but I don't see that particular file.  Is that the
same thing as configuration settings, or should I just save the whole folder
that contains everything?

Ron

--- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@...>
wrote:
>
>
> Ron,
>
> Glad to hear you are up and running again.
>
> One important file you might want to back up to a thumb now and then is the
WUHU Configuration.INI file. This file is located in the WUHU program folder and
contains all of your upload information and settings.
>
>
> --- In wuhu_software_group@yahoogroups.com, "ronw72" <1rondee@> wrote:
> >
> >
> >
> > wuhu_software,
> >
> > At first I didn't have the correct drivers installed, I still had a yellow
question mark.
> >
> > I finally got the update drives installed and my heavy weather working after
resetting the outside transmitter and the console.
> >
> > Then it took me awhile to get all of the correct information set for my WUHU
uploader.  I had everything wrong along with a few typo's, duhhhhhhhhhhh.
> >
> > Hopefully I've got everything back up running, I'm getting too old for this
stuff, too many senior moments. HaHa
> >
> > Thanks,
> >
> > Ron
> >
> > --- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@>
wrote:
> > >
> > >
> > > Ron,
> > >
> > > Did you re-install the drivers for the Keyspan?
> > >
> > > What serial port # is assigned to it?
> > >
> > >
> > > --- In wuhu_software_group@yahoogroups.com, "ronw72" <1rondee@> wrote:
> > > >
> > > > Help
> > > >
> > > > My weather station, LaCrosse 2310, with a Keyspan Serial to USB adapter,
is down again.  Ever since I had to do a recovery on my computer, I haven't been
able to get my station up and running.
> > > >
> > > > I can't even get heavy weather to work.  It looks like I am not
receiving any data from the console.  The console is receiving info from the
outside unit, both wired or not wired, but the computer is not receiving any
data at all.
> > > >
> > > > Any help would be appreciated.
> > > >
> > > > Thanks,
> > > >
> > > > Ron
> > > >
> > >
> >
>

You can save the whole folder but the only important file is the:

WUHU Configuration.INI

file.


--- In wuhu_software_group@yahoogroups.com, "ronw72" <1rondee@...> wrote:
>
>
>
> Thanks wuhu_software,
>
> I'm looking in that folder but I don't see that particular file.  Is that the
same thing as configuration settings, or should I just save the whole folder
that contains everything?
>
> Ron
>
> --- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@>
wrote:
> >
> >
> > Ron,
> >
> > Glad to hear you are up and running again.
> >
> > One important file you might want to back up to a thumb now and then is the
WUHU Configuration.INI file. This file is located in the WUHU program folder and
contains all of your upload information and settings.
> >
> >
> > --- In wuhu_software_group@yahoogroups.com, "ronw72" <1rondee@> wrote:
> > >
> > >
> > >
> > > wuhu_software,
> > >
> > > At first I didn't have the correct drivers installed, I still had a yellow
question mark.
> > >
> > > I finally got the update drives installed and my heavy weather working
after resetting the outside transmitter and the console.
> > >
> > > Then it took me awhile to get all of the correct information set for my
WUHU uploader.  I had everything wrong along with a few typo's, duhhhhhhhhhhh.
> > >
> > > Hopefully I've got everything back up running, I'm getting too old for
this stuff, too many senior moments. HaHa
> > >
> > > Thanks,
> > >
> > > Ron
> > >
> > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
<wuhu_software@> wrote:
> > > >
> > > >
> > > > Ron,
> > > >
> > > > Did you re-install the drivers for the Keyspan?
> > > >
> > > > What serial port # is assigned to it?
> > > >
> > > >
> > > > --- In wuhu_software_group@yahoogroups.com, "ronw72" <1rondee@> wrote:
> > > > >
> > > > > Help
> > > > >
> > > > > My weather station, LaCrosse 2310, with a Keyspan Serial to USB
adapter, is down again.  Ever since I had to do a recovery on my computer, I
haven't been able to get my station up and running.
> > > > >
> > > > > I can't even get heavy weather to work.  It looks like I am not
receiving any data from the console.  The console is receiving info from the
outside unit, both wired or not wired, but the computer is not receiving any
data at all.
> > > > >
> > > > > Any help would be appreciated.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Ron
> > > > >
> > > >
> > >
> >
>

--- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@...>
wrote:
>Were do I find the wu txt file? the one thats generated is the log file and it
cant be copyed and pasted
>
> In the setup, did you configure the station type WV32 to and set the file to
monitor to the wu.txt file being generated?
>
> Please send me the wu.txt file in email to wuhu_software at yahoo.com.
>
>
> --- In wuhu_software_group@yahoogroups.com, "davewierstad" <davewierstad@>
wrote:
> >
> >
> >
> > --- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@>
wrote:
> > >I'm using WV32 V 7.0 with WU Heavyweather uploader
> > >
> > > Ok for now, go to setup and un-check the enable uploads until we figure
out what is going on.
> > >
> > > What kind of station is this? Are you using Heavyweather or some other
application?
> > >
> > > The more details the better.
> > >
> > >
> > > --- In wuhu_software_group@yahoogroups.com, "davewierstad" <davewierstad@>
wrote:
> > > >
> > > >
> > > >
> > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
<wuhu_software@> wrote:
> > > > >Thats the bad part all my dials read zero
> > > > >
> > > > > If the data on your screen makes sense, do not worry about it.
> > > > >
> > > > > Awekas has their own data quality checking that sometimes raises false
alarms and sends out emails.
> > > > >
> > > > >
> > > > > --- In wuhu_software_group@yahoogroups.com, "davewierstad"
<davewierstad@> wrote:
> > > > > >
> > > > > > I'm trying to setup Awekas software and it connects to WU ok,but it
says my sensors values our out of range,were in the setup menu do I set the
values like temperature,humidity etc
> > > > > >
> > > > >
> > > >
> > >
> >
>

Search the hard drive for wu.txt.

I am not sure what you have pointed WUHU to in the Setup section, what file did
you point it to?



--- In wuhu_software_group@yahoogroups.com, "davewierstad" <davewierstad@...>
wrote:
>
>
>
> --- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@>
wrote:
> >Were do I find the wu txt file? the one thats generated is the log file and
it cant be copyed and pasted
> >
> > In the setup, did you configure the station type WV32 to and set the file to
monitor to the wu.txt file being generated?
> >
> > Please send me the wu.txt file in email to wuhu_software at yahoo.com.
> >
> >
> > --- In wuhu_software_group@yahoogroups.com, "davewierstad" <davewierstad@>
wrote:
> > >
> > >
> > >
> > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
<wuhu_software@> wrote:
> > > >I'm using WV32 V 7.0 with WU Heavyweather uploader
> > > >
> > > > Ok for now, go to setup and un-check the enable uploads until we figure
out what is going on.
> > > >
> > > > What kind of station is this? Are you using Heavyweather or some other
application?
> > > >
> > > > The more details the better.
> > > >
> > > >
> > > > --- In wuhu_software_group@yahoogroups.com, "davewierstad"
<davewierstad@> wrote:
> > > > >
> > > > >
> > > > >
> > > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
<wuhu_software@> wrote:
> > > > > >Thats the bad part all my dials read zero
> > > > > >
> > > > > > If the data on your screen makes sense, do not worry about it.
> > > > > >
> > > > > > Awekas has their own data quality checking that sometimes raises
false alarms and sends out emails.
> > > > > >
> > > > > >
> > > > > > --- In wuhu_software_group@yahoogroups.com, "davewierstad"
<davewierstad@> wrote:
> > > > > > >
> > > > > > > I'm trying to setup Awekas software and it connects to WU ok,but
it says my sensors values our out of range,were in the setup menu do I set the
values like temperature,humidity etc
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

hmmm. I tried that. My console told me that the storm total was 2.49", but the
most wuhu says is 2.33" no matter how much time I put in.
Edith

--- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@...>
wrote:
>
>
> Edith,
>
> I forgot to mention, you must set the radio button to hours or mins, enter the
values, then either wait for an update from the console or hit the Show button
to update the stats immediately.
>
>
> --- In wuhu_software_group@yahoogroups.com, "Edith" <Edith.Thornburg@> wrote:
> >
> > Changing the numbers in those 2 boxes doesn't seem to change anything...
> > Also, is there somewhere I can see what the wind did during the storm too?
> > Edith
> >
> > --- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@>
wrote:
> > >
> > >
> > > I should have mentioned that the "Delta" column displays the change over
the specified period, and in the case of the rain, the change in rain total. You
can use this to determine the amount of rainfall over the specified period.
> > >
> > >
> > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
<wuhu_software@> wrote:
> > > >
> > > >
> > > > Edith,
> > > >
> > > > In the stats area, at the bottom, you can enter a range of time to have
displayed in the stats area.
> > > >
> > > > For example, to display the stats for the past 3 hours, you can enter 0
to 3 hours. If you hit graph, the graph will show you that range of time. If you
hit the gauges button, this also reflects only that range of time you have
specified.
> > > >
> > > > If you enter 0 to M that means from now to midnight.
> > > >
> > > > If the first field is not zero, say from 1 to 3, then the stats will
reflect from 1 hour ago to 3 hours ago and the stats will not automatically
update when new data is received, to go back to auto-update mode, the first
value (or from value) must be zero (meaning now).
> > > >
> > > > There is no specific function to view the storm total as is available on
some stations like the Davis. I am not sure what criteria they are using for the
beginning or ending of a storm.
> > > >
> > > >
> > > > --- In wuhu_software_group@yahoogroups.com, "Edith" <Edith.Thornburg@>
wrote:
> > > > >
> > > > > I did a very quick/light search, but didn't see anything at a glance.
Is there somewhere I can see storm totals for rainfall, not just last 24 hours?
> > > > > TIA
> > > > > Edith
> > > > >
> > > >
> > >
> >
>

That is interesting... I am wondering how Davis is calculating the storm
total... When does that value reset or does it never reset?


--- In wuhu_software_group@yahoogroups.com, "Edith" <Edith.Thornburg@...> wrote:
>
> hmmm. I tried that. My console told me that the storm total was 2.49", but the
most wuhu says is 2.33" no matter how much time I put in.
> Edith
>
> --- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@>
wrote:
> >
> >
> > Edith,
> >
> > I forgot to mention, you must set the radio button to hours or mins, enter
the values, then either wait for an update from the console or hit the Show
button to update the stats immediately.
> >
> >
> > --- In wuhu_software_group@yahoogroups.com, "Edith" <Edith.Thornburg@>
wrote:
> > >
> > > Changing the numbers in those 2 boxes doesn't seem to change anything...
> > > Also, is there somewhere I can see what the wind did during the storm too?
> > > Edith
> > >
> > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
<wuhu_software@> wrote:
> > > >
> > > >
> > > > I should have mentioned that the "Delta" column displays the change over
the specified period, and in the case of the rain, the change in rain total. You
can use this to determine the amount of rainfall over the specified period.
> > > >
> > > >
> > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
<wuhu_software@> wrote:
> > > > >
> > > > >
> > > > > Edith,
> > > > >
> > > > > In the stats area, at the bottom, you can enter a range of time to
have displayed in the stats area.
> > > > >
> > > > > For example, to display the stats for the past 3 hours, you can enter
0 to 3 hours. If you hit graph, the graph will show you that range of time. If
you hit the gauges button, this also reflects only that range of time you have
specified.
> > > > >
> > > > > If you enter 0 to M that means from now to midnight.
> > > > >
> > > > > If the first field is not zero, say from 1 to 3, then the stats will
reflect from 1 hour ago to 3 hours ago and the stats will not automatically
update when new data is received, to go back to auto-update mode, the first
value (or from value) must be zero (meaning now).
> > > > >
> > > > > There is no specific function to view the storm total as is available
on some stations like the Davis. I am not sure what criteria they are using for
the beginning or ending of a storm.
> > > > >
> > > > >
> > > > > --- In wuhu_software_group@yahoogroups.com, "Edith" <Edith.Thornburg@>
wrote:
> > > > > >
> > > > > > I did a very quick/light search, but didn't see anything at a
glance. Is there somewhere I can see storm totals for rainfall, not just last 24
hours?
> > > > > > TIA
> > > > > > Edith
> > > > > >
> > > > >
> > > >
> > >
> >
>

Edith,

The manual states:

Rain Storm - Rain Storm displays the rain total of the last rain event. It takes
two tips of the rain bucket to begin a storm event and 24 hours without rain to
end a storm event.

That being the case, if you had a tiny amount of rain, say 0.02, then almost 24
hours goes by, and you get more rain, the amount of time of a storm could be
days or more.

By default, WUHU will capture 24 hours of data in memory. You can increase this
amount by hitting Stop, Hit Setup, in General Settings, change the Hours of
Weather Data in Memory field. The minimum is 24 hours, the maximum is 168 hours
(a week of readings, every reading each 5-7 seconds).

Try increasing that value to at least a few days if you want to be able to view
the stats and graph the data beyond 24 hours.



--- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@...>
wrote:
>
>
> That is interesting... I am wondering how Davis is calculating the storm
total... When does that value reset or does it never reset?
>
>
> --- In wuhu_software_group@yahoogroups.com, "Edith" <Edith.Thornburg@> wrote:
> >
> > hmmm. I tried that. My console told me that the storm total was 2.49", but
the most wuhu says is 2.33" no matter how much time I put in.
> > Edith
> >
> > --- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@>
wrote:
> > >
> > >
> > > Edith,
> > >
> > > I forgot to mention, you must set the radio button to hours or mins, enter
the values, then either wait for an update from the console or hit the Show
button to update the stats immediately.
> > >
> > >
> > > --- In wuhu_software_group@yahoogroups.com, "Edith" <Edith.Thornburg@>
wrote:
> > > >
> > > > Changing the numbers in those 2 boxes doesn't seem to change anything...
> > > > Also, is there somewhere I can see what the wind did during the storm
too?
> > > > Edith
> > > >
> > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
<wuhu_software@> wrote:
> > > > >
> > > > >
> > > > > I should have mentioned that the "Delta" column displays the change
over the specified period, and in the case of the rain, the change in rain
total. You can use this to determine the amount of rainfall over the specified
period.
> > > > >
> > > > >
> > > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
<wuhu_software@> wrote:
> > > > > >
> > > > > >
> > > > > > Edith,
> > > > > >
> > > > > > In the stats area, at the bottom, you can enter a range of time to
have displayed in the stats area.
> > > > > >
> > > > > > For example, to display the stats for the past 3 hours, you can
enter 0 to 3 hours. If you hit graph, the graph will show you that range of
time. If you hit the gauges button, this also reflects only that range of time
you have specified.
> > > > > >
> > > > > > If you enter 0 to M that means from now to midnight.
> > > > > >
> > > > > > If the first field is not zero, say from 1 to 3, then the stats will
reflect from 1 hour ago to 3 hours ago and the stats will not automatically
update when new data is received, to go back to auto-update mode, the first
value (or from value) must be zero (meaning now).
> > > > > >
> > > > > > There is no specific function to view the storm total as is
available on some stations like the Davis. I am not sure what criteria they are
using for the beginning or ending of a storm.
> > > > > >
> > > > > >
> > > > > > --- In wuhu_software_group@yahoogroups.com, "Edith"
<Edith.Thornburg@> wrote:
> > > > > > >
> > > > > > > I did a very quick/light search, but didn't see anything at a
glance. Is there somewhere I can see storm totals for rainfall, not just last 24
hours?
> > > > > > > TIA
> > > > > > > Edith
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Here is this error I am getting.
Weather station works fine, just this not sure why I am getting this wind gust.

Thu Dec 02 19:12:45 2010 > Wind gust speed reading of 57.0 mph detected when
wind is only gusting to 0.0 mph (over past 10 minutes). Replaced with average
value that was calculated over the past 10 minutes.

Is it a La Crosse 23XX?

If so, these bad wind readings are typical from that kind of station, that is
why the data is rejected and the log message is created.


--- In wuhu_software_group@yahoogroups.com, "Eddie" <djx_master@...> wrote:
>
> Here is this error I am getting.
> Weather station works fine, just this not sure why I am getting this wind
gust.
>
> Thu Dec 02 19:12:45 2010 > Wind gust speed reading of 57.0 mph detected when
wind is only gusting to 0.0 mph (over past 10 minutes). Replaced with average
value that was calculated over the past 10 minutes.
>

Sorry such a delay in getting back.
This is from this morning:

Fri Dec 03 07:26:26 2010 > PWSWeather Background Upload: Final Fatal Eror (No
more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
Fri Dec 03 07:26:27 2010 > PWSWeather Background Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&windgustmph=2.5&temp\
f=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf=12.5&humidity=74&weathe\
r=&clouds=&softwaretype=WUHU216VWC&action=updateraw
Fri Dec 03 07:27:02 2010 > PWSWeather Live Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-12-03+13%3A26%3A16&winddir=292&windspeedmph=3.5&windgustmph=4.3&temp\
f=21.7&rainin=0.00&dailyrainin=0.00&baromin=30.27&dewptf=13.8&humidity=71&weathe\
r=&clouds=&softwaretype=WUHU216VWC&action=updateraw
Fri Dec 03 07:28:00 2010 > PWSWeather Background Upload: Final Fatal Eror (No
more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
Fri Dec 03 07:28:01 2010 > PWSWeather Background Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&windgustmph=2.5&temp\
f=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf=12.5&humidity=74&weathe\
r=&clouds=&softwaretype=WUHU216VWC&action=updateraw
Fri Dec 03 07:28:34 2010 > PWSWeather Live Upload: Final Fatal Eror (No more
retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
Fri Dec 03 07:29:32 2010 > PWSWeather Background Upload: Final Fatal Eror (No
more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
Fri Dec 03 07:29:33 2010 > PWSWeather Background Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&windgustmph=2.5&temp\
f=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf=12.5&humidity=74&weathe\
r=&clouds=&softwaretype=WUHU216VWC&action=updateraw
Fri Dec 03 07:31:04 2010 > PWSWeather Background Upload: Final Fatal Eror (No
more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
Fri Dec 03 07:31:05 2010 > PWSWeather Background Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&windgustmph=2.5&temp\
f=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf=12.5&humidity=74&weathe\
r=&clouds=&softwaretype=WUHU216VWC&action=updateraw


--- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@...>
wrote:
>
>
> Lets see if we can isolate the problem with your uploads.
>
> I did find an issue with their server returning a new return string indicating
that the upload was successful. Previously, the server responded with "OK"
indicating that it had accepted the upload. I monitored my upload today and
found it responding with "Data Logged and posted in METAR mirror". I have added
this new result code in the software and it will be in the next release,
probably when we figure out what is going on with your station. Even with the
failure to spot the new result code, my station has been uploading to PWSWeather
un-interrupted.
>
> To attempt to debug your poblem, what you need to do is go to the Log screen,
un-check "Only Errors", un-check all check boxes other servers and services
except PWSWeather. Do not check "Show Console Com. Errors" as this will clutter
the log.
>
> Next, wait a few minutes until the next upload to PWSWeather happens. You
should see a couple new entries in the log, what was sent to the PWSWeather
server and the servers response. Select those lines in the log then hit the Copy
Selected button to copy these entries to your Windows clipboard. Next, post a
message here with those entries.
>
>
> --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@> wrote:
> >
> > PWS is NOT getting the data. The connection times out. Their display page of
my data shows old data, however, occasonly data gets through
> > and shows. Then their display page reverts back to the same old data set.
> > I have reviewed firewall and router.
> >
> > --- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@>
wrote:
> > >
> > >
> > > One user reported the following was a router problem. Apparently PWS
weather uses multiple servers, and the one you send to might not be the one that
responds. If the router is does not allow this, the program will not see the
response from their server.
> > >
> > > ---
> > >
> > > Found It!!!
> > >
> > > Yes, the router had updated firmware and change two settings on the
router. UDP and TCP endpoint filtering was set to address restricted instead of
endpoint independent. What this does is not allow communications if the return
(ack) is from a different address than the sendto address. This is why I could
get the data to PWS but it could not ACK my packets.
> > >
> > >
> > > --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@> wrote:
> > > >
> > > > I have been running WUHU for a long time with no trouble.
> > > > Recently, PWS and Hamweather reports have been "stuck" on an older set
of data. I contacted PWS and they claimed the issue was on my end.
> > > > I updated to the latest version of WUHU and now all reports go through
EXCEPT PWS. the following errors repeat in the log:
> > > > Sat Nov 20 10:20:10 2010 > PWSWeather Live Upload: Final Fatal Eror (No
more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> > > > Sat Nov 20 10:20:44 2010 > PWSWeather Background Upload: Final Fatal
Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> > > >
> > > > Any feedback?
> > > >
> > >
> >
>

Installed latest release posted here (152) and getting same thing.

--- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@...> wrote:
>
> Sorry such a delay in getting back.
> This is from this morning:
>
> Fri Dec 03 07:26:26 2010 > PWSWeather Background Upload: Final Fatal Eror (No
more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> Fri Dec 03 07:26:27 2010 > PWSWeather Background Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&windgustmph=2.5&temp\
f=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf=12.5&humidity=74&weathe\
r=&clouds=&softwaretype=WUHU216VWC&action=updateraw
> Fri Dec 03 07:27:02 2010 > PWSWeather Live Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-12-03+13%3A26%3A16&winddir=292&windspeedmph=3.5&windgustmph=4.3&temp\
f=21.7&rainin=0.00&dailyrainin=0.00&baromin=30.27&dewptf=13.8&humidity=71&weathe\
r=&clouds=&softwaretype=WUHU216VWC&action=updateraw
> Fri Dec 03 07:28:00 2010 > PWSWeather Background Upload: Final Fatal Eror (No
more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> Fri Dec 03 07:28:01 2010 > PWSWeather Background Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&windgustmph=2.5&temp\
f=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf=12.5&humidity=74&weathe\
r=&clouds=&softwaretype=WUHU216VWC&action=updateraw
> Fri Dec 03 07:28:34 2010 > PWSWeather Live Upload: Final Fatal Eror (No more
retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> Fri Dec 03 07:29:32 2010 > PWSWeather Background Upload: Final Fatal Eror (No
more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> Fri Dec 03 07:29:33 2010 > PWSWeather Background Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&windgustmph=2.5&temp\
f=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf=12.5&humidity=74&weathe\
r=&clouds=&softwaretype=WUHU216VWC&action=updateraw
> Fri Dec 03 07:31:04 2010 > PWSWeather Background Upload: Final Fatal Eror (No
more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> Fri Dec 03 07:31:05 2010 > PWSWeather Background Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&windgustmph=2.5&temp\
f=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf=12.5&humidity=74&weathe\
r=&clouds=&softwaretype=WUHU216VWC&action=updateraw
>
>
> --- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@>
wrote:
> >
> >
> > Lets see if we can isolate the problem with your uploads.
> >
> > I did find an issue with their server returning a new return string
indicating that the upload was successful. Previously, the server responded with
"OK" indicating that it had accepted the upload. I monitored my upload today and
found it responding with "Data Logged and posted in METAR mirror". I have added
this new result code in the software and it will be in the next release,
probably when we figure out what is going on with your station. Even with the
failure to spot the new result code, my station has been uploading to PWSWeather
un-interrupted.
> >
> > To attempt to debug your poblem, what you need to do is go to the Log
screen, un-check "Only Errors", un-check all check boxes other servers and
services except PWSWeather. Do not check "Show Console Com. Errors" as this will
clutter the log.
> >
> > Next, wait a few minutes until the next upload to PWSWeather happens. You
should see a couple new entries in the log, what was sent to the PWSWeather
server and the servers response. Select those lines in the log then hit the Copy
Selected button to copy these entries to your Windows clipboard. Next, post a
message here with those entries.
> >
> >
> > --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@> wrote:
> > >
> > > PWS is NOT getting the data. The connection times out. Their display page
of my data shows old data, however, occasonly data gets through
> > > and shows. Then their display page reverts back to the same old data set.
> > > I have reviewed firewall and router.
> > >
> > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
<wuhu_software@> wrote:
> > > >
> > > >
> > > > One user reported the following was a router problem. Apparently PWS
weather uses multiple servers, and the one you send to might not be the one that
responds. If the router is does not allow this, the program will not see the
response from their server.
> > > >
> > > > ---
> > > >
> > > > Found It!!!
> > > >
> > > > Yes, the router had updated firmware and change two settings on the
router. UDP and TCP endpoint filtering was set to address restricted instead of
endpoint independent. What this does is not allow communications if the return
(ack) is from a different address than the sendto address. This is why I could
get the data to PWS but it could not ACK my packets.
> > > >
> > > >
> > > > --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@> wrote:
> > > > >
> > > > > I have been running WUHU for a long time with no trouble.
> > > > > Recently, PWS and Hamweather reports have been "stuck" on an older set
of data. I contacted PWS and they claimed the issue was on my end.
> > > > > I updated to the latest version of WUHU and now all reports go through
EXCEPT PWS. the following errors repeat in the log:
> > > > > Sat Nov 20 10:20:10 2010 > PWSWeather Live Upload: Final Fatal Eror
(No more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> > > > > Sat Nov 20 10:20:44 2010 > PWSWeather Background Upload: Final Fatal
Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> > > > >
> > > > > Any feedback?
> > > > >
> > > >
> > >
> >
>

Do you have a 2nd machine that you could connect the station to? I would like to
isolate whether it is that particular computer.

I am not seeing anyone else that is having this issue so perhaps some strange
firewall setting is stopping the response.


--- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@...> wrote:
>
> Installed latest release posted here (152) and getting same thing.
>
> --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@> wrote:
> >
> > Sorry such a delay in getting back.
> > This is from this morning:
> >
> > Fri Dec 03 07:26:26 2010 > PWSWeather Background Upload: Final Fatal Eror
(No more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> > Fri Dec 03 07:26:27 2010 > PWSWeather Background Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&windgustmph=2.5&temp\
f=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf=12.5&humidity=74&weathe\
r=&clouds=&softwaretype=WUHU216VWC&action=updateraw
> > Fri Dec 03 07:27:02 2010 > PWSWeather Live Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-12-03+13%3A26%3A16&winddir=292&windspeedmph=3.5&windgustmph=4.3&temp\
f=21.7&rainin=0.00&dailyrainin=0.00&baromin=30.27&dewptf=13.8&humidity=71&weathe\
r=&clouds=&softwaretype=WUHU216VWC&action=updateraw
> > Fri Dec 03 07:28:00 2010 > PWSWeather Background Upload: Final Fatal Eror
(No more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> > Fri Dec 03 07:28:01 2010 > PWSWeather Background Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&windgustmph=2.5&temp\
f=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf=12.5&humidity=74&weathe\
r=&clouds=&softwaretype=WUHU216VWC&action=updateraw
> > Fri Dec 03 07:28:34 2010 > PWSWeather Live Upload: Final Fatal Eror (No more
retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> > Fri Dec 03 07:29:32 2010 > PWSWeather Background Upload: Final Fatal Eror
(No more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> > Fri Dec 03 07:29:33 2010 > PWSWeather Background Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&windgustmph=2.5&temp\
f=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf=12.5&humidity=74&weathe\
r=&clouds=&softwaretype=WUHU216VWC&action=updateraw
> > Fri Dec 03 07:31:04 2010 > PWSWeather Background Upload: Final Fatal Eror
(No more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> > Fri Dec 03 07:31:05 2010 > PWSWeather Background Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&windgustmph=2.5&temp\
f=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf=12.5&humidity=74&weathe\
r=&clouds=&softwaretype=WUHU216VWC&action=updateraw
> >
> >
> > --- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@>
wrote:
> > >
> > >
> > > Lets see if we can isolate the problem with your uploads.
> > >
> > > I did find an issue with their server returning a new return string
indicating that the upload was successful. Previously, the server responded with
"OK" indicating that it had accepted the upload. I monitored my upload today and
found it responding with "Data Logged and posted in METAR mirror". I have added
this new result code in the software and it will be in the next release,
probably when we figure out what is going on with your station. Even with the
failure to spot the new result code, my station has been uploading to PWSWeather
un-interrupted.
> > >
> > > To attempt to debug your poblem, what you need to do is go to the Log
screen, un-check "Only Errors", un-check all check boxes other servers and
services except PWSWeather. Do not check "Show Console Com. Errors" as this will
clutter the log.
> > >
> > > Next, wait a few minutes until the next upload to PWSWeather happens. You
should see a couple new entries in the log, what was sent to the PWSWeather
server and the servers response. Select those lines in the log then hit the Copy
Selected button to copy these entries to your Windows clipboard. Next, post a
message here with those entries.
> > >
> > >
> > > --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@> wrote:
> > > >
> > > > PWS is NOT getting the data. The connection times out. Their display
page of my data shows old data, however, occasonly data gets through
> > > > and shows. Then their display page reverts back to the same old data
set.
> > > > I have reviewed firewall and router.
> > > >
> > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
<wuhu_software@> wrote:
> > > > >
> > > > >
> > > > > One user reported the following was a router problem. Apparently PWS
weather uses multiple servers, and the one you send to might not be the one that
responds. If the router is does not allow this, the program will not see the
response from their server.
> > > > >
> > > > > ---
> > > > >
> > > > > Found It!!!
> > > > >
> > > > > Yes, the router had updated firmware and change two settings on the
router. UDP and TCP endpoint filtering was set to address restricted instead of
endpoint independent. What this does is not allow communications if the return
(ack) is from a different address than the sendto address. This is why I could
get the data to PWS but it could not ACK my packets.
> > > > >
> > > > >
> > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@> wrote:
> > > > > >
> > > > > > I have been running WUHU for a long time with no trouble.
> > > > > > Recently, PWS and Hamweather reports have been "stuck" on an older
set of data. I contacted PWS and they claimed the issue was on my end.
> > > > > > I updated to the latest version of WUHU and now all reports go
through EXCEPT PWS. the following errors repeat in the log:
> > > > > > Sat Nov 20 10:20:10 2010 > PWSWeather Live Upload: Final Fatal Eror
(No more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> > > > > > Sat Nov 20 10:20:44 2010 > PWSWeather Background Upload: Final Fatal
Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> > > > > >
> > > > > > Any feedback?
> > > > > >
> > > > >
> > > >
> > >
> >
>

Different machine, no firewall, no router.
Also see ping, tracert (2) and path ping below.

Fri Dec 03 11:46:59 2010 > PWSWeather Live Upload: Final Fatal Eror (No more
retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
Fri Dec 03 11:47:50 2010 > PWSWeather Background Upload: Final Fatal Eror (No
more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
Fri Dec 03 11:47:50 2010 > PWSWeather Background Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windgustmph=2.7&tempf\
=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=13.1&humidity=70&weather\
=&clouds=&softwaretype=WUHU216VWC&action=updateraw
Fri Dec 03 11:49:21 2010 > PWSWeather Background Upload: Final Fatal Eror (No
more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
Fri Dec 03 11:49:21 2010 > PWSWeather Background Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windgustmph=2.7&tempf\
=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=13.1&humidity=70&weather\
=&clouds=&softwaretype=WUHU216VWC&action=updateraw
Fri Dec 03 11:50:52 2010 > PWSWeather Background Upload: Final Fatal Eror (No
more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
Fri Dec 03 11:50:52 2010 > PWSWeather Background Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windgustmph=2.7&tempf\
=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=13.1&humidity=70&weather\
=&clouds=&softwaretype=WUHU216VWC&action=updateraw

Pinging pwsweather.com [72.51.35.225] with 32 bytes of data:  Reply from
72.51.35.225: bytes=32 time=223ms TTL=44 Reply from 72.51.35.225: bytes=32
time=202ms TTL=44 Reply from 72.51.35.225: bytes=32 time=195ms TTL=44 Reply from
72.51.35.225: bytes=32 time=210ms TTL=44  Ping statistics for 72.51.35.225:    
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip
times in milli-seconds:     Minimum = 195ms, Maximum = 223ms, Average = 207ms

Tracing route to pwsweather.com [72.51.35.225] over a maximum of 30 hops:    1
<1 ms    <1 ms    <1 ms  bossman.mshome.net [192.168.0.1]    2   108 ms    93 ms
90 ms  10.119.160.1    3   503 ms   468 ms   377 ms  166.181.126.81    4   527
ms   454 ms   461 ms  166.181.126.92    5   528 ms   159 ms   100 ms 
166.181.113.1    6   387 ms   387 ms   389 ms  198.8.15.242    7   309 ms   319
ms   346 ms  198.8.15.252    8     *        *        *     Request timed out.  
9     *        *        *     Request timed out.  10     *        *        *    
Request timed out.  11     *        *        *     Request timed out.  12     *
*        *     Request timed out.  13   356 ms   355 ms   327 ms  198.8.15.1  
14   161 ms   159 ms   139 ms  so-5-0-0.edge2.Atlanta2.Level3.net [4.71.194.17]
15   291 ms   209 ms   261 ms  ae-63-51.ebr3.Atlanta2.Level3.net [4.68.103.30]  
16   400 ms   386 ms   360 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]   17
206 ms   197 ms   198 ms  ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]   18
229 ms   433 ms   518 ms  ae-34-80.car4.LosAngeles1.Level3.net [4.69.144.134]  
19     *        *        *     Request timed out.  20   242 ms   194 ms   204 ms
oc48-po4-0.la-sb600w-dis-2.peer1.net [216.187.88.150]   21   433 ms   506 ms  
198 ms  pws0.pwsweather.com [72.51.35.225]   Trace complete.

2nd trace:
Tracing route to pwsweather.com [72.51.35.225] over a maximum of 30 hops:    1
<1 ms    <1 ms    <1 ms  bossman.mshome.net [192.168.0.1]    2   106 ms    95 ms
110 ms  10.119.160.1    3   102 ms   112 ms   112 ms  166.181.126.81    4   189
ms    98 ms    93 ms  166.181.126.92    5    94 ms    92 ms    93 ms 
166.181.113.1    6   112 ms   112 ms    94 ms  198.8.15.242    7   139 ms   159
ms   136 ms  198.8.15.252    8     *        *        *     Request timed out.  
9     *        *        *     Request timed out.  10     *        *        *    
Request timed out.  11     *        *        *     Request timed out.  12     *
*        *     Request timed out.  13   147 ms   133 ms   132 ms  198.8.15.1  
14   157 ms   139 ms   141 ms  so-5-0-0.edge2.Atlanta2.Level3.net [4.71.194.17]
15   180 ms   140 ms   147 ms  ae-73-52.ebr3.Atlanta2.Level3.net [4.68.103.62]  
16   175 ms   199 ms   194 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]   17
225 ms   218 ms   195 ms  ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]   18
389 ms   223 ms   220 ms  ae-34-80.car4.LosAngeles1.Level3.net [4.69.144.134]  
19     *        *        *     Request timed out.  20   232 ms   197 ms   202 ms
oc48-po4-0.la-sb600w-dis-2.peer1.net [216.187.88.150]   21   221 ms   216 ms  
217 ms  pws0.pwsweather.com [72.51.35.225]   Trace complete.

The first time out series is between U.S. Cellular IP's
second time out is between Level3.net and peer1.net

Path ping
Tracing route to pwsweather.com [72.51.35.225] over a maximum of 30 hops:
0  weatherwatcher.mshome.net [192.168.0.119]
1  bossman.mshome.net [192.168.0.1]
2  10.119.160.1
3  166.181.126.81
4  166.181.126.92
5  166.181.113.1
6  198.8.15.242
7  198.8.15.252
8     *        *        *
Computing statistics for 200 seconds...
		 Source to Here   	 This Node/Link
Hop  RTT    ` Lost/Sent = Pct  	 Lost/Sent = Pct   Address
  0                                           					 weatherwatcher.mshome.net
[192.168.0.119]                                  					 0/ 100 =  0%
1    0ms      0/ 100 =  0%     		 0/ 100 =  0%  	 bossman.mshome.net
[192.168.0.1]                                  					 0/ 100 =  0%
2  ---     	 100/ 100 =100%   	 100/ 100 =100%   10.119.160.1
						 0/ 100 =  0%
3  ---     	 100/ 100 =100%   	 100/ 100 =100%   166.181.126.81
		 				 0/ 100 =  0%
4  ---     	 100/ 100 =100%   	 100/ 100 =100%   166.181.126.92
						 0/ 100 =  0%
5  192ms      0/ 100 =  0%     		 0/ 100 =  0%  	 166.181.113.1
						 0/ 100 =  0%
6  221ms      0/ 100 =  0%     		 0/ 100 =  0%  	 198.8.15.242
						 100/ 100 =100%
7  ---     	 100/ 100 =100%     	 0/ 100 =  0%  	 198.8.15.252
						 0/ 100 =  0%
8  ---     	 100/ 100 =100%     	 0/ 100 =  0%  	 weatherwatcher [0.0.0.0]
Trace complete.

--- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@...>
wrote:
>
>
> Do you have a 2nd machine that you could connect the station to? I would like
to isolate whether it is that particular computer.
>
> I am not seeing anyone else that is having this issue so perhaps some strange
firewall setting is stopping the response.
>
>
> --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@> wrote:
> >
> > Installed latest release posted here (152) and getting same thing.
> >
> > --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@> wrote:
> > >
> > > Sorry such a delay in getting back.
> > > This is from this morning:
> > >
> > > Fri Dec 03 07:26:26 2010 > PWSWeather Background Upload: Final Fatal Eror
(No more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> > > Fri Dec 03 07:26:27 2010 > PWSWeather Background Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&windgustmph=2.5&temp\
f=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf=12.5&humidity=74&weathe\
r=&clouds=&softwaretype=WUHU216VWC&action=updateraw
> > > Fri Dec 03 07:27:02 2010 > PWSWeather Live Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-12-03+13%3A26%3A16&winddir=292&windspeedmph=3.5&windgustmph=4.3&temp\
f=21.7&rainin=0.00&dailyrainin=0.00&baromin=30.27&dewptf=13.8&humidity=71&weathe\
r=&clouds=&softwaretype=WUHU216VWC&action=updateraw
> > > Fri Dec 03 07:28:00 2010 > PWSWeather Background Upload: Final Fatal Eror
(No more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> > > Fri Dec 03 07:28:01 2010 > PWSWeather Background Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&windgustmph=2.5&temp\
f=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf=12.5&humidity=74&weathe\
r=&clouds=&softwaretype=WUHU216VWC&action=updateraw
> > > Fri Dec 03 07:28:34 2010 > PWSWeather Live Upload: Final Fatal Eror (No
more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> > > Fri Dec 03 07:29:32 2010 > PWSWeather Background Upload: Final Fatal Eror
(No more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> > > Fri Dec 03 07:29:33 2010 > PWSWeather Background Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&windgustmph=2.5&temp\
f=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf=12.5&humidity=74&weathe\
r=&clouds=&softwaretype=WUHU216VWC&action=updateraw
> > > Fri Dec 03 07:31:04 2010 > PWSWeather Background Upload: Final Fatal Eror
(No more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> > > Fri Dec 03 07:31:05 2010 > PWSWeather Background Upload: Sending
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=******&d\
ateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&windgustmph=2.5&temp\
f=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf=12.5&humidity=74&weathe\
r=&clouds=&softwaretype=WUHU216VWC&action=updateraw
> > >
> > >
> > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
<wuhu_software@> wrote:
> > > >
> > > >
> > > > Lets see if we can isolate the problem with your uploads.
> > > >
> > > > I did find an issue with their server returning a new return string
indicating that the upload was successful. Previously, the server responded with
"OK" indicating that it had accepted the upload. I monitored my upload today and
found it responding with "Data Logged and posted in METAR mirror". I have added
this new result code in the software and it will be in the next release,
probably when we figure out what is going on with your station. Even with the
failure to spot the new result code, my station has been uploading to PWSWeather
un-interrupted.
> > > >
> > > > To attempt to debug your poblem, what you need to do is go to the Log
screen, un-check "Only Errors", un-check all check boxes other servers and
services except PWSWeather. Do not check "Show Console Com. Errors" as this will
clutter the log.
> > > >
> > > > Next, wait a few minutes until the next upload to PWSWeather happens.
You should see a couple new entries in the log, what was sent to the PWSWeather
server and the servers response. Select those lines in the log then hit the Copy
Selected button to copy these entries to your Windows clipboard. Next, post a
message here with those entries.
> > > >
> > > >
> > > > --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@> wrote:
> > > > >
> > > > > PWS is NOT getting the data. The connection times out. Their display
page of my data shows old data, however, occasonly data gets through
> > > > > and shows. Then their display page reverts back to the same old data
set.
> > > > > I have reviewed firewall and router.
> > > > >
> > > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
<wuhu_software@> wrote:
> > > > > >
> > > > > >
> > > > > > One user reported the following was a router problem. Apparently PWS
weather uses multiple servers, and the one you send to might not be the one that
responds. If the router is does not allow this, the program will not see the
response from their server.
> > > > > >
> > > > > > ---
> > > > > >
> > > > > > Found It!!!
> > > > > >
> > > > > > Yes, the router had updated firmware and change two settings on the
router. UDP and TCP endpoint filtering was set to address restricted instead of
endpoint independent. What this does is not allow communications if the return
(ack) is from a different address than the sendto address. This is why I could
get the data to PWS but it could not ACK my packets.
> > > > > >
> > > > > >
> > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@>
wrote:
> > > > > > >
> > > > > > > I have been running WUHU for a long time with no trouble.
> > > > > > > Recently, PWS and Hamweather reports have been "stuck" on an older
set of data. I contacted PWS and they claimed the issue was on my end.
> > > > > > > I updated to the latest version of WUHU and now all reports go
through EXCEPT PWS. the following errors repeat in the log:
> > > > > > > Sat Nov 20 10:20:10 2010 > PWSWeather Live Upload: Final Fatal
Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
ERROR_INTERNET_TIMEOUT.
> > > > > > > Sat Nov 20 10:20:44 2010 > PWSWeather Background Upload: Final
Fatal Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
(12002), ERROR_INTERNET_TIMEOUT.
> > > > > > >
> > > > > > > Any feedback?
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

One thing I should have mentioned, when you post the captured traffic, do not
paste your passwords for the world to see here. They will be in the sent http://
request. Overwrite the passwords with *****.

Thanks.


--- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@...>
wrote:
>
>
> Here is something else we might try:
> Download and install the following:
> EffeTech HTTP Sniffer v4.1 <http://www.effetech.com/download/>
> During the install, make sure you read the instructions and answer Yes
> to install the WinPCAP, that is a low-level network driver than can
> intercept network packets.
> After install, under the programs Sniff menu, press Start.
> This will capture all http:// traffic on the machine.
> After you capture your attempted upload to PWSWeather, copy and paste
> the header and the response to the request (if any).
>
> --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> <wuhu_software@> wrote:
> >
> >
> > It is interesting that you have a 192.168.0.X address. Can you chance
> > that to a 192.168.1.X address?
> > I am also concerned about the Comodo firewall being used. You might
> try
> > removing it completely to see if that makes a difference.
> > Finally, I found this note in a tips and tricks for XP. It might not
> > hurt to check these settings. I am using the InternetOpenURL() so this
> > may or may not be an issue for you.
> > ---
> > 232. Increasing number of connections per http server Folks, HTTP
> > Protocol limits number of maximum connections to a HTTP server to 2.
> > Following table explains restrictions placed by various HTTP
> PROTOCOLS.
> > This is the as per the RFC specifications.
> > 1. HTTP 1.0 conforming server 4 simultaneous connections 2. HTTP 1.1
> > conforming server 2 simputaneous connections Limitation caused by this
> > is visible whenever your applications make calls like HttpSendRequest
> > and InternetOpenURL which take longer to complete as they wait for
> > previous connections to be freed up before their requests are sent.
> > You can configure WinInet to exceed this limit by creating and setting
> > the registry entries. Open registry (by going to START-RUN and
> entering
> > regedit) and navigate to:
> >
> >
> [HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Intern\
> \
> > et Settings]
> > and look for values of "MaxConnectionsPerServer" and
> > "MaxConnectionsPer1_0Server ".
> > If you don't see then add two key by the names
> "MaxConnectionsPerServer"
> > and "MaxConnectionsPer1_0Server " respectively. Default values are as
> > MaxConnectionsPerServer = 2 MaxConnectionsPer1_0Server = 4 Changes its
> > value to a number you want.
> > --- In wuhu_software_group@yahoogroups.com, "Wolf" wolf9sbu@ wrote:
> > >
> > > Different machine, no firewall, no router.
> > > Also see ping, tracert (2) and path ping below.
> > >
> > > Fri Dec 03 11:46:59 2010 > PWSWeather Live Upload: Final Fatal Eror
> > (No more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
> > ERROR_INTERNET_TIMEOUT.
> > > Fri Dec 03 11:47:50 2010 > PWSWeather Background Upload: Final Fatal
> > Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > (12002), ERROR_INTERNET_TIMEOUT.
> > > Fri Dec 03 11:47:50 2010 > PWSWeather Background Upload: Sending
> >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> >
> ******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> \
> >
> ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> \
> >
> 13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> \
> > aw
> > > Fri Dec 03 11:49:21 2010 > PWSWeather Background Upload: Final Fatal
> > Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > (12002), ERROR_INTERNET_TIMEOUT.
> > > Fri Dec 03 11:49:21 2010 > PWSWeather Background Upload: Sending
> >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> >
> ******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> \
> >
> ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> \
> >
> 13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> \
> > aw
> > > Fri Dec 03 11:50:52 2010 > PWSWeather Background Upload: Final Fatal
> > Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > (12002), ERROR_INTERNET_TIMEOUT.
> > > Fri Dec 03 11:50:52 2010 > PWSWeather Background Upload: Sending
> >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> >
> ******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> \
> >
> ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> \
> >
> 13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> \
> > aw
> > >
> > > Pinging pwsweather.com [72.51.35.225] with 32 bytes of data:  Reply
> > from 72.51.35.225: bytes=32 time=223ms TTL=44 Reply from 72.51.35.225:
> > bytes=32 time=202ms TTL=44 Reply from 72.51.35.225: bytes=32
> time=195ms
> > TTL=44 Reply from 72.51.35.225: bytes=32 time=210ms TTL=44  Ping
> > statistics for 72.51.35.225:     Packets: Sent = 4, Received = 4, Lost
> =
> > 0 (0% loss), Approximate round trip times in milli-seconds:
> Minimum
> > = 195ms, Maximum = 223ms, Average = 207ms
> > >
> > > Tracing route to pwsweather.com [72.51.35.225] over a maximum of 30
> > hops:    1    <1 ms    <1 ms    <1 ms  bossman.mshome.net
> [192.168.0.1]
> > 2   108 ms    93 ms    90 ms  10.119.160.1    3   503 ms   468 ms
> 377
> > ms  166.181.126.81    4   527 ms   454 ms   461 ms  166.181.126.92
> 5
> > 528 ms   159 ms   100 ms  166.181.113.1    6   387 ms   387 ms   389
> ms
> > 198.8.15.242    7   309 ms   319 ms   346 ms  198.8.15.252    8     *
> > *        *     Request timed out.   9     *        *        *
> > Request timed out.  10     *        *        *     Request timed out.
> > 11     *        *        *     Request timed out.  12     *        *
> > *     Request timed out.  13   356 ms   355 ms   327 ms  198.8.15.1
> 14
> > 161 ms   159 ms   139 ms  so-5-0-0.edge2.Atlanta2.Level3.net
> > [4.71.194.17]   15   291 ms   209 ms   261 ms
> > ae-63-51.ebr3.Atlanta2.Level3.net [4.68.103.30]   16   400 ms   386 ms
> > 360 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]   17   206 ms
> 197
> > ms   198 ms  ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]   18
> 229
> > ms   433 ms   518 ms  ae-34-80.car4.LosAngeles1.Level3.net
> > [4.69.144.134]   19     *        *        *     Request timed out.  20
> > 242 ms   194 ms   204 ms  oc48-po4-0.la-sb600w-dis-2.peer1.net
> > [216.187.88.150]   21   433 ms   506 ms   198 ms  pws0.pwsweather.com
> > [72.51.35.225]   Trace complete.
> > >
> > > 2nd trace:
> > > Tracing route to pwsweather.com [72.51.35.225] over a maximum of 30
> > hops:    1    <1 ms    <1 ms    <1 ms  bossman.mshome.net
> [192.168.0.1]
> > 2   106 ms    95 ms   110 ms  10.119.160.1    3   102 ms   112 ms
> 112
> > ms  166.181.126.81    4   189 ms    98 ms    93 ms  166.181.126.92
> 5
> > 94 ms    92 ms    93 ms  166.181.113.1    6   112 ms   112 ms    94 ms
> > 198.8.15.242    7   139 ms   159 ms   136 ms  198.8.15.252    8     *
> > *        *     Request timed out.   9     *        *        *
> > Request timed out.  10     *        *        *     Request timed out.
> > 11     *        *        *     Request timed out.  12     *        *
> > *     Request timed out.  13   147 ms   133 ms   132 ms  198.8.15.1
> 14
> > 157 ms   139 ms   141 ms  so-5-0-0.edge2.Atlanta2.Level3.net
> > [4.71.194.17]   15   180 ms   140 ms   147 ms
> > ae-73-52.ebr3.Atlanta2.Level3.net [4.68.103.62]   16   175 ms   199 ms
> > 194 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]   17   225 ms
> 218
> > ms   195 ms  ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]   18
> 389
> > ms   223 ms   220 ms  ae-34-80.car4.LosAngeles1.Level3.net
> > [4.69.144.134]   19     *        *        *     Request timed out.  20
> > 232 ms   197 ms   202 ms  oc48-po4-0.la-sb600w-dis-2.peer1.net
> > [216.187.88.150]   21   221 ms   216 ms   217 ms  pws0.pwsweather.com
> > [72.51.35.225]   Trace complete.
> > >
> > > The first time out series is between U.S. Cellular IP's
> > > second time out is between Level3.net and peer1.net
> > >
> > > Path ping
> > > Tracing route to pwsweather.com [72.51.35.225] over a maximum of 30
> > hops:
> > > 0  weatherwatcher.mshome.net [192.168.0.119]
> > > 1  bossman.mshome.net [192.168.0.1]
> > > 2  10.119.160.1
> > > 3  166.181.126.81
> > > 4  166.181.126.92
> > > 5  166.181.113.1
> > > 6  198.8.15.242
> > > 7  198.8.15.252
> > > 8     *        *        *
> > > Computing statistics for 200 seconds...
> > >   Source to Here     This Node/Link
> > > Hop  RTT    ` Lost/Sent = Pct    Lost/Sent = Pct   Address
> > >  0
> > weatherwatcher.mshome.net [192.168.0.119]
> > 0/ 100 =  0%
> > > 1    0ms      0/ 100 =  0%        0/ 100 =  0%    bossman.mshome.net
> > [192.168.0.1]                                        0/ 100 =  0%
> > > 2  ---       100/ 100 =100%     100/ 100 =100%   10.119.160.1
> > >       0/ 100 =  0%
> > > 3  ---       100/ 100 =100%     100/ 100 =100%   166.181.126.81
> > >        0/ 100 =  0%
> > > 4  ---       100/ 100 =100%     100/ 100 =100%   166.181.126.92
> > >       0/ 100 =  0%
> > > 5  192ms      0/ 100 =  0%        0/ 100 =  0%    166.181.113.1
> > >       0/ 100 =  0%
> > > 6  221ms      0/ 100 =  0%        0/ 100 =  0%    198.8.15.242
> > >       100/ 100 =100%
> > > 7  ---       100/ 100 =100%       0/ 100 =  0%    198.8.15.252
> > >       0/ 100 =  0%
> > > 8  ---       100/ 100 =100%       0/ 100 =  0%    weatherwatcher
> > [0.0.0.0]
> > > Trace complete.
> > >
> > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> > wuhu_software@ wrote:
> > > >
> > > >
> > > > Do you have a 2nd machine that you could connect the station to? I
> > would like to isolate whether it is that particular computer.
> > > >
> > > > I am not seeing anyone else that is having this issue so perhaps
> > some strange firewall setting is stopping the response.
> > > >
> > > >
> > > > --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@>
> > wrote:
> > > > >
> > > > > Installed latest release posted here (152) and getting same
> thing.
> > > > >
> > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@>
> > wrote:
> > > > > >
> > > > > > Sorry such a delay in getting back.
> > > > > > This is from this morning:
> > > > > >
> > > > > > Fri Dec 03 07:26:26 2010 > PWSWeather Background Upload: Final
> > Fatal Eror (No more retries) InternetOpenUrl() returned error
> 0x00002ee2
> > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > Fri Dec 03 07:26:27 2010 > PWSWeather Background Upload:
> Sending
> >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> >
> ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> \
> >
> gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> \
> >
> =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> \
> > raw
> > > > > > Fri Dec 03 07:27:02 2010 > PWSWeather Live Upload: Sending
> >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> >
> ******&dateutc=2010-12-03+13%3A26%3A16&winddir=292&windspeedmph=3.5&wind\
> \
> >
> gustmph=4.3&tempf=21.7&rainin=0.00&dailyrainin=0.00&baromin=30.27&dewptf\
> \
> >
> =13.8&humidity=71&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> \
> > raw
> > > > > > Fri Dec 03 07:28:00 2010 > PWSWeather Background Upload: Final
> > Fatal Eror (No more retries) InternetOpenUrl() returned error
> 0x00002ee2
> > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > Fri Dec 03 07:28:01 2010 > PWSWeather Background Upload:
> Sending
> >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> >
> ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> \
> >
> gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> \
> >
> =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> \
> > raw
> > > > > > Fri Dec 03 07:28:34 2010 > PWSWeather Live Upload: Final Fatal
> > Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > Fri Dec 03 07:29:32 2010 > PWSWeather Background Upload: Final
> > Fatal Eror (No more retries) InternetOpenUrl() returned error
> 0x00002ee2
> > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > Fri Dec 03 07:29:33 2010 > PWSWeather Background Upload:
> Sending
> >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> >
> ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> \
> >
> gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> \
> >
> =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> \
> > raw
> > > > > > Fri Dec 03 07:31:04 2010 > PWSWeather Background Upload: Final
> > Fatal Eror (No more retries) InternetOpenUrl() returned error
> 0x00002ee2
> > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > Fri Dec 03 07:31:05 2010 > PWSWeather Background Upload:
> Sending
> >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> >
> ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> \
> >
> gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> \
> >
> =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> \
> > raw
> > > > > >
> > > > > >
> > > > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> > <wuhu_software@> wrote:
> > > > > > >
> > > > > > >
> > > > > > > Lets see if we can isolate the problem with your uploads.
> > > > > > >
> > > > > > > I did find an issue with their server returning a new return
> > string indicating that the upload was successful. Previously, the
> server
> > responded with "OK" indicating that it had accepted the upload. I
> > monitored my upload today and found it responding with "Data Logged
> and
> > posted in METAR mirror". I have added this new result code in the
> > software and it will be in the next release, probably when we figure
> out
> > what is going on with your station. Even with the failure to spot the
> > new result code, my station has been uploading to PWSWeather
> > un-interrupted.
> > > > > > >
> > > > > > > To attempt to debug your poblem, what you need to do is go
> to
> > the Log screen, un-check "Only Errors", un-check all check boxes other
> > servers and services except PWSWeather. Do not check "Show Console
> Com.
> > Errors" as this will clutter the log.
> > > > > > >
> > > > > > > Next, wait a few minutes until the next upload to PWSWeather
> > happens. You should see a couple new entries in the log, what was sent
> > to the PWSWeather server and the servers response. Select those lines
> in
> > the log then hit the Copy Selected button to copy these entries to
> your
> > Windows clipboard. Next, post a message here with those entries.
> > > > > > >
> > > > > > >
> > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf"
> <wolf9sbu@>
> > wrote:
> > > > > > > >
> > > > > > > > PWS is NOT getting the data. The connection times out.
> Their
> > display page of my data shows old data, however, occasonly data gets
> > through
> > > > > > > > and shows. Then their display page reverts back to the
> same
> > old data set.
> > > > > > > > I have reviewed firewall and router.
> > > > > > > >
> > > > > > > > --- In wuhu_software_group@yahoogroups.com,
> "wuhu_software"
> > <wuhu_software@> wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > One user reported the following was a router problem.
> > Apparently PWS weather uses multiple servers, and the one you send to
> > might not be the one that responds. If the router is does not allow
> > this, the program will not see the response from their server.
> > > > > > > > >
> > > > > > > > > ---
> > > > > > > > >
> > > > > > > > > Found It!!!
> > > > > > > > >
> > > > > > > > > Yes, the router had updated firmware and change two
> > settings on the router. UDP and TCP endpoint filtering was set to
> > address restricted instead of endpoint independent. What this does is
> > not allow communications if the return (ack) is from a different
> address
> > than the sendto address. This is why I could get the data to PWS but
> it
> > could not ACK my packets.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf"
> > <wolf9sbu@> wrote:
> > > > > > > > > >
> > > > > > > > > > I have been running WUHU for a long time with no
> > trouble.
> > > > > > > > > > Recently, PWS and Hamweather reports have been "stuck"
> > on an older set of data. I contacted PWS and they claimed the issue
> was
> > on my end.
> > > > > > > > > > I updated to the latest version of WUHU and now all
> > reports go through EXCEPT PWS. the following errors repeat in the log:
> > > > > > > > > > Sat Nov 20 10:20:10 2010 > PWSWeather Live Upload:
> Final
> > Fatal Eror (No more retries) InternetOpenUrl() returned error
> 0x00002ee2
> > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > > Sat Nov 20 10:20:44 2010 > PWSWeather Background
> Upload:
> > Final Fatal Eror (No more retries) InternetOpenUrl() returned error
> > 0x00002ee2 (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > >
> > > > > > > > > > Any feedback?
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

According to "Web of Trust" plugin for Firefox, (www.mywot.com/)
http://www.effetech.com/download/ "has a poor reputation."
So... I'm not going there and recommending folks to go there isn't cool.
Thanks for all your effort however,
I'm all done with this on my end. As was mentioned by a few early in this
string, they just shut of PWS upload and didn't be bothered.
I joined the forum to try to fix it and I've jumped through enough hoops. Every
thing else I do on the Internet works including FTP. web sites, forums, email...
is working along with WUHU uploads to everything EXCEPT PWS. Comodo doesn't stop
anything else I want to do. I imagine there are quit a few who just shut it off
and never bothered joining the forum to figure it out so you won't get "Ya I had
that problem" from many of the folks that did cause their not here. I don't
check Yahoo often unless there is something of interest to me. I'm done being
interested in this issue and I'll just uncheck PWS from logging and remove all
references from my web pages. When an occasional post goes through to them as it
does now, that's all fine for whoever is interested.
Since everything else is working so smoothly, at this point, in my humble
opinion, it's a PWS issue that they can figure out.
Again, thanks for your efforts and I will continue to provide data to all who
are willing to receive it without me jumping through hoops to get it to them.
Happy Days


--- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@...>
wrote:
>
>
> Here is something else we might try:
> Download and install the following:
> EffeTech HTTP Sniffer v4.1 <http://www.effetech.com/download/>
> During the install, make sure you read the instructions and answer Yes
> to install the WinPCAP, that is a low-level network driver than can
> intercept network packets.
> After install, under the programs Sniff menu, press Start.
> This will capture all http:// traffic on the machine.
> After you capture your attempted upload to PWSWeather, copy and paste
> the header and the response to the request (if any).
>
> --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> <wuhu_software@> wrote:
> >
> >
> > It is interesting that you have a 192.168.0.X address. Can you chance
> > that to a 192.168.1.X address?
> > I am also concerned about the Comodo firewall being used. You might
> try
> > removing it completely to see if that makes a difference.
> > Finally, I found this note in a tips and tricks for XP. It might not
> > hurt to check these settings. I am using the InternetOpenURL() so this
> > may or may not be an issue for you.
> > ---
> > 232. Increasing number of connections per http server Folks, HTTP
> > Protocol limits number of maximum connections to a HTTP server to 2.
> > Following table explains restrictions placed by various HTTP
> PROTOCOLS.
> > This is the as per the RFC specifications.
> > 1. HTTP 1.0 conforming server 4 simultaneous connections 2. HTTP 1.1
> > conforming server 2 simputaneous connections Limitation caused by this
> > is visible whenever your applications make calls like HttpSendRequest
> > and InternetOpenURL which take longer to complete as they wait for
> > previous connections to be freed up before their requests are sent.
> > You can configure WinInet to exceed this limit by creating and setting
> > the registry entries. Open registry (by going to START-RUN and
> entering
> > regedit) and navigate to:
> >
> >
> [HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Intern\
> \
> > et Settings]
> > and look for values of "MaxConnectionsPerServer" and
> > "MaxConnectionsPer1_0Server ".
> > If you don't see then add two key by the names
> "MaxConnectionsPerServer"
> > and "MaxConnectionsPer1_0Server " respectively. Default values are as
> > MaxConnectionsPerServer = 2 MaxConnectionsPer1_0Server = 4 Changes its
> > value to a number you want.
> > --- In wuhu_software_group@yahoogroups.com, "Wolf" wolf9sbu@ wrote:
> > >
> > > Different machine, no firewall, no router.
> > > Also see ping, tracert (2) and path ping below.
> > >
> > > Fri Dec 03 11:46:59 2010 > PWSWeather Live Upload: Final Fatal Eror
> > (No more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
> > ERROR_INTERNET_TIMEOUT.
> > > Fri Dec 03 11:47:50 2010 > PWSWeather Background Upload: Final Fatal
> > Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > (12002), ERROR_INTERNET_TIMEOUT.
> > > Fri Dec 03 11:47:50 2010 > PWSWeather Background Upload: Sending
> >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> >
> ******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> \
> >
> ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> \
> >
> 13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> \
> > aw
> > > Fri Dec 03 11:49:21 2010 > PWSWeather Background Upload: Final Fatal
> > Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > (12002), ERROR_INTERNET_TIMEOUT.
> > > Fri Dec 03 11:49:21 2010 > PWSWeather Background Upload: Sending
> >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> >
> ******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> \
> >
> ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> \
> >
> 13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> \
> > aw
> > > Fri Dec 03 11:50:52 2010 > PWSWeather Background Upload: Final Fatal
> > Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > (12002), ERROR_INTERNET_TIMEOUT.
> > > Fri Dec 03 11:50:52 2010 > PWSWeather Background Upload: Sending
> >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> >
> ******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> \
> >
> ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> \
> >
> 13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> \
> > aw
> > >
> > > Pinging pwsweather.com [72.51.35.225] with 32 bytes of data:  Reply
> > from 72.51.35.225: bytes=32 time=223ms TTL=44 Reply from 72.51.35.225:
> > bytes=32 time=202ms TTL=44 Reply from 72.51.35.225: bytes=32
> time=195ms
> > TTL=44 Reply from 72.51.35.225: bytes=32 time=210ms TTL=44  Ping
> > statistics for 72.51.35.225:     Packets: Sent = 4, Received = 4, Lost
> =
> > 0 (0% loss), Approximate round trip times in milli-seconds:
> Minimum
> > = 195ms, Maximum = 223ms, Average = 207ms
> > >
> > > Tracing route to pwsweather.com [72.51.35.225] over a maximum of 30
> > hops:    1    <1 ms    <1 ms    <1 ms  bossman.mshome.net
> [192.168.0.1]
> > 2   108 ms    93 ms    90 ms  10.119.160.1    3   503 ms   468 ms
> 377
> > ms  166.181.126.81    4   527 ms   454 ms   461 ms  166.181.126.92
> 5
> > 528 ms   159 ms   100 ms  166.181.113.1    6   387 ms   387 ms   389
> ms
> > 198.8.15.242    7   309 ms   319 ms   346 ms  198.8.15.252    8     *
> > *        *     Request timed out.   9     *        *        *
> > Request timed out.  10     *        *        *     Request timed out.
> > 11     *        *        *     Request timed out.  12     *        *
> > *     Request timed out.  13   356 ms   355 ms   327 ms  198.8.15.1
> 14
> > 161 ms   159 ms   139 ms  so-5-0-0.edge2.Atlanta2.Level3.net
> > [4.71.194.17]   15   291 ms   209 ms   261 ms
> > ae-63-51.ebr3.Atlanta2.Level3.net [4.68.103.30]   16   400 ms   386 ms
> > 360 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]   17   206 ms
> 197
> > ms   198 ms  ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]   18
> 229
> > ms   433 ms   518 ms  ae-34-80.car4.LosAngeles1.Level3.net
> > [4.69.144.134]   19     *        *        *     Request timed out.  20
> > 242 ms   194 ms   204 ms  oc48-po4-0.la-sb600w-dis-2.peer1.net
> > [216.187.88.150]   21   433 ms   506 ms   198 ms  pws0.pwsweather.com
> > [72.51.35.225]   Trace complete.
> > >
> > > 2nd trace:
> > > Tracing route to pwsweather.com [72.51.35.225] over a maximum of 30
> > hops:    1    <1 ms    <1 ms    <1 ms  bossman.mshome.net
> [192.168.0.1]
> > 2   106 ms    95 ms   110 ms  10.119.160.1    3   102 ms   112 ms
> 112
> > ms  166.181.126.81    4   189 ms    98 ms    93 ms  166.181.126.92
> 5
> > 94 ms    92 ms    93 ms  166.181.113.1    6   112 ms   112 ms    94 ms
> > 198.8.15.242    7   139 ms   159 ms   136 ms  198.8.15.252    8     *
> > *        *     Request timed out.   9     *        *        *
> > Request timed out.  10     *        *        *     Request timed out.
> > 11     *        *        *     Request timed out.  12     *        *
> > *     Request timed out.  13   147 ms   133 ms   132 ms  198.8.15.1
> 14
> > 157 ms   139 ms   141 ms  so-5-0-0.edge2.Atlanta2.Level3.net
> > [4.71.194.17]   15   180 ms   140 ms   147 ms
> > ae-73-52.ebr3.Atlanta2.Level3.net [4.68.103.62]   16   175 ms   199 ms
> > 194 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]   17   225 ms
> 218
> > ms   195 ms  ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]   18
> 389
> > ms   223 ms   220 ms  ae-34-80.car4.LosAngeles1.Level3.net
> > [4.69.144.134]   19     *        *        *     Request timed out.  20
> > 232 ms   197 ms   202 ms  oc48-po4-0.la-sb600w-dis-2.peer1.net
> > [216.187.88.150]   21   221 ms   216 ms   217 ms  pws0.pwsweather.com
> > [72.51.35.225]   Trace complete.
> > >
> > > The first time out series is between U.S. Cellular IP's
> > > second time out is between Level3.net and peer1.net
> > >
> > > Path ping
> > > Tracing route to pwsweather.com [72.51.35.225] over a maximum of 30
> > hops:
> > > 0  weatherwatcher.mshome.net [192.168.0.119]
> > > 1  bossman.mshome.net [192.168.0.1]
> > > 2  10.119.160.1
> > > 3  166.181.126.81
> > > 4  166.181.126.92
> > > 5  166.181.113.1
> > > 6  198.8.15.242
> > > 7  198.8.15.252
> > > 8     *        *        *
> > > Computing statistics for 200 seconds...
> > >   Source to Here     This Node/Link
> > > Hop  RTT    ` Lost/Sent = Pct    Lost/Sent = Pct   Address
> > >  0
> > weatherwatcher.mshome.net [192.168.0.119]
> > 0/ 100 =  0%
> > > 1    0ms      0/ 100 =  0%        0/ 100 =  0%    bossman.mshome.net
> > [192.168.0.1]                                        0/ 100 =  0%
> > > 2  ---       100/ 100 =100%     100/ 100 =100%   10.119.160.1
> > >       0/ 100 =  0%
> > > 3  ---       100/ 100 =100%     100/ 100 =100%   166.181.126.81
> > >        0/ 100 =  0%
> > > 4  ---       100/ 100 =100%     100/ 100 =100%   166.181.126.92
> > >       0/ 100 =  0%
> > > 5  192ms      0/ 100 =  0%        0/ 100 =  0%    166.181.113.1
> > >       0/ 100 =  0%
> > > 6  221ms      0/ 100 =  0%        0/ 100 =  0%    198.8.15.242
> > >       100/ 100 =100%
> > > 7  ---       100/ 100 =100%       0/ 100 =  0%    198.8.15.252
> > >       0/ 100 =  0%
> > > 8  ---       100/ 100 =100%       0/ 100 =  0%    weatherwatcher
> > [0.0.0.0]
> > > Trace complete.
> > >
> > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> > wuhu_software@ wrote:
> > > >
> > > >
> > > > Do you have a 2nd machine that you could connect the station to? I
> > would like to isolate whether it is that particular computer.
> > > >
> > > > I am not seeing anyone else that is having this issue so perhaps
> > some strange firewall setting is stopping the response.
> > > >
> > > >
> > > > --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@>
> > wrote:
> > > > >
> > > > > Installed latest release posted here (152) and getting same
> thing.
> > > > >
> > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@>
> > wrote:
> > > > > >
> > > > > > Sorry such a delay in getting back.
> > > > > > This is from this morning:
> > > > > >
> > > > > > Fri Dec 03 07:26:26 2010 > PWSWeather Background Upload: Final
> > Fatal Eror (No more retries) InternetOpenUrl() returned error
> 0x00002ee2
> > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > Fri Dec 03 07:26:27 2010 > PWSWeather Background Upload:
> Sending
> >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> >
> ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> \
> >
> gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> \
> >
> =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> \
> > raw
> > > > > > Fri Dec 03 07:27:02 2010 > PWSWeather Live Upload: Sending
> >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> >
> ******&dateutc=2010-12-03+13%3A26%3A16&winddir=292&windspeedmph=3.5&wind\
> \
> >
> gustmph=4.3&tempf=21.7&rainin=0.00&dailyrainin=0.00&baromin=30.27&dewptf\
> \
> >
> =13.8&humidity=71&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> \
> > raw
> > > > > > Fri Dec 03 07:28:00 2010 > PWSWeather Background Upload: Final
> > Fatal Eror (No more retries) InternetOpenUrl() returned error
> 0x00002ee2
> > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > Fri Dec 03 07:28:01 2010 > PWSWeather Background Upload:
> Sending
> >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> >
> ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> \
> >
> gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> \
> >
> =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> \
> > raw
> > > > > > Fri Dec 03 07:28:34 2010 > PWSWeather Live Upload: Final Fatal
> > Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > Fri Dec 03 07:29:32 2010 > PWSWeather Background Upload: Final
> > Fatal Eror (No more retries) InternetOpenUrl() returned error
> 0x00002ee2
> > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > Fri Dec 03 07:29:33 2010 > PWSWeather Background Upload:
> Sending
> >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> >
> ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> \
> >
> gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> \
> >
> =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> \
> > raw
> > > > > > Fri Dec 03 07:31:04 2010 > PWSWeather Background Upload: Final
> > Fatal Eror (No more retries) InternetOpenUrl() returned error
> 0x00002ee2
> > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > Fri Dec 03 07:31:05 2010 > PWSWeather Background Upload:
> Sending
> >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> >
> ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> \
> >
> gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> \
> >
> =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> \
> > raw
> > > > > >
> > > > > >
> > > > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> > <wuhu_software@> wrote:
> > > > > > >
> > > > > > >
> > > > > > > Lets see if we can isolate the problem with your uploads.
> > > > > > >
> > > > > > > I did find an issue with their server returning a new return
> > string indicating that the upload was successful. Previously, the
> server
> > responded with "OK" indicating that it had accepted the upload. I
> > monitored my upload today and found it responding with "Data Logged
> and
> > posted in METAR mirror". I have added this new result code in the
> > software and it will be in the next release, probably when we figure
> out
> > what is going on with your station. Even with the failure to spot the
> > new result code, my station has been uploading to PWSWeather
> > un-interrupted.
> > > > > > >
> > > > > > > To attempt to debug your poblem, what you need to do is go
> to
> > the Log screen, un-check "Only Errors", un-check all check boxes other
> > servers and services except PWSWeather. Do not check "Show Console
> Com.
> > Errors" as this will clutter the log.
> > > > > > >
> > > > > > > Next, wait a few minutes until the next upload to PWSWeather
> > happens. You should see a couple new entries in the log, what was sent
> > to the PWSWeather server and the servers response. Select those lines
> in
> > the log then hit the Copy Selected button to copy these entries to
> your
> > Windows clipboard. Next, post a message here with those entries.
> > > > > > >
> > > > > > >
> > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf"
> <wolf9sbu@>
> > wrote:
> > > > > > > >
> > > > > > > > PWS is NOT getting the data. The connection times out.
> Their
> > display page of my data shows old data, however, occasonly data gets
> > through
> > > > > > > > and shows. Then their display page reverts back to the
> same
> > old data set.
> > > > > > > > I have reviewed firewall and router.
> > > > > > > >
> > > > > > > > --- In wuhu_software_group@yahoogroups.com,
> "wuhu_software"
> > <wuhu_software@> wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > One user reported the following was a router problem.
> > Apparently PWS weather uses multiple servers, and the one you send to
> > might not be the one that responds. If the router is does not allow
> > this, the program will not see the response from their server.
> > > > > > > > >
> > > > > > > > > ---
> > > > > > > > >
> > > > > > > > > Found It!!!
> > > > > > > > >
> > > > > > > > > Yes, the router had updated firmware and change two
> > settings on the router. UDP and TCP endpoint filtering was set to
> > address restricted instead of endpoint independent. What this does is
> > not allow communications if the return (ack) is from a different
> address
> > than the sendto address. This is why I could get the data to PWS but
> it
> > could not ACK my packets.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf"
> > <wolf9sbu@> wrote:
> > > > > > > > > >
> > > > > > > > > > I have been running WUHU for a long time with no
> > trouble.
> > > > > > > > > > Recently, PWS and Hamweather reports have been "stuck"
> > on an older set of data. I contacted PWS and they claimed the issue
> was
> > on my end.
> > > > > > > > > > I updated to the latest version of WUHU and now all
> > reports go through EXCEPT PWS. the following errors repeat in the log:
> > > > > > > > > > Sat Nov 20 10:20:10 2010 > PWSWeather Live Upload:
> Final
> > Fatal Eror (No more retries) InternetOpenUrl() returned error
> 0x00002ee2
> > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > > Sat Nov 20 10:20:44 2010 > PWSWeather Background
> Upload:
> > Final Fatal Eror (No more retries) InternetOpenUrl() returned error
> > 0x00002ee2 (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > >
> > > > > > > > > > Any feedback?
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

No problem.

I did install that effetech software and did not see a problem.

Are they questionable because of spyware or something?

I did not notice anything.

Thanks.


--- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@...> wrote:
>
> According to "Web of Trust" plugin for Firefox, (www.mywot.com/)
http://www.effetech.com/download/ "has a poor reputation."
> So... I'm not going there and recommending folks to go there isn't cool.
> Thanks for all your effort however,
> I'm all done with this on my end. As was mentioned by a few early in this
string, they just shut of PWS upload and didn't be bothered.
> I joined the forum to try to fix it and I've jumped through enough hoops.
Every thing else I do on the Internet works including FTP. web sites, forums,
email... is working along with WUHU uploads to everything EXCEPT PWS. Comodo
doesn't stop anything else I want to do. I imagine there are quit a few who just
shut it off and never bothered joining the forum to figure it out so you won't
get "Ya I had that problem" from many of the folks that did cause their not
here. I don't check Yahoo often unless there is something of interest to me. I'm
done being interested in this issue and I'll just uncheck PWS from logging and
remove all references from my web pages. When an occasional post goes through to
them as it does now, that's all fine for whoever is interested.
> Since everything else is working so smoothly, at this point, in my humble
opinion, it's a PWS issue that they can figure out.
> Again, thanks for your efforts and I will continue to provide data to all who
are willing to receive it without me jumping through hoops to get it to them.
> Happy Days
>
>
> --- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@>
wrote:
> >
> >
> > Here is something else we might try:
> > Download and install the following:
> > EffeTech HTTP Sniffer v4.1 <http://www.effetech.com/download/>
> > During the install, make sure you read the instructions and answer Yes
> > to install the WinPCAP, that is a low-level network driver than can
> > intercept network packets.
> > After install, under the programs Sniff menu, press Start.
> > This will capture all http:// traffic on the machine.
> > After you capture your attempted upload to PWSWeather, copy and paste
> > the header and the response to the request (if any).
> >
> > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> > <wuhu_software@> wrote:
> > >
> > >
> > > It is interesting that you have a 192.168.0.X address. Can you chance
> > > that to a 192.168.1.X address?
> > > I am also concerned about the Comodo firewall being used. You might
> > try
> > > removing it completely to see if that makes a difference.
> > > Finally, I found this note in a tips and tricks for XP. It might not
> > > hurt to check these settings. I am using the InternetOpenURL() so this
> > > may or may not be an issue for you.
> > > ---
> > > 232. Increasing number of connections per http server Folks, HTTP
> > > Protocol limits number of maximum connections to a HTTP server to 2.
> > > Following table explains restrictions placed by various HTTP
> > PROTOCOLS.
> > > This is the as per the RFC specifications.
> > > 1. HTTP 1.0 conforming server 4 simultaneous connections 2. HTTP 1.1
> > > conforming server 2 simputaneous connections Limitation caused by this
> > > is visible whenever your applications make calls like HttpSendRequest
> > > and InternetOpenURL which take longer to complete as they wait for
> > > previous connections to be freed up before their requests are sent.
> > > You can configure WinInet to exceed this limit by creating and setting
> > > the registry entries. Open registry (by going to START-RUN and
> > entering
> > > regedit) and navigate to:
> > >
> > >
> > [HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Intern\
> > \
> > > et Settings]
> > > and look for values of "MaxConnectionsPerServer" and
> > > "MaxConnectionsPer1_0Server ".
> > > If you don't see then add two key by the names
> > "MaxConnectionsPerServer"
> > > and "MaxConnectionsPer1_0Server " respectively. Default values are as
> > > MaxConnectionsPerServer = 2 MaxConnectionsPer1_0Server = 4 Changes its
> > > value to a number you want.
> > > --- In wuhu_software_group@yahoogroups.com, "Wolf" wolf9sbu@ wrote:
> > > >
> > > > Different machine, no firewall, no router.
> > > > Also see ping, tracert (2) and path ping below.
> > > >
> > > > Fri Dec 03 11:46:59 2010 > PWSWeather Live Upload: Final Fatal Eror
> > > (No more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
> > > ERROR_INTERNET_TIMEOUT.
> > > > Fri Dec 03 11:47:50 2010 > PWSWeather Background Upload: Final Fatal
> > > Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > Fri Dec 03 11:47:50 2010 > PWSWeather Background Upload: Sending
> > >
> > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > \
> > >
> > ******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> > \
> > >
> > ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> > \
> > >
> > 13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> > \
> > > aw
> > > > Fri Dec 03 11:49:21 2010 > PWSWeather Background Upload: Final Fatal
> > > Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > Fri Dec 03 11:49:21 2010 > PWSWeather Background Upload: Sending
> > >
> > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > \
> > >
> > ******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> > \
> > >
> > ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> > \
> > >
> > 13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> > \
> > > aw
> > > > Fri Dec 03 11:50:52 2010 > PWSWeather Background Upload: Final Fatal
> > > Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > Fri Dec 03 11:50:52 2010 > PWSWeather Background Upload: Sending
> > >
> > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > \
> > >
> > ******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> > \
> > >
> > ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> > \
> > >
> > 13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> > \
> > > aw
> > > >
> > > > Pinging pwsweather.com [72.51.35.225] with 32 bytes of data:  Reply
> > > from 72.51.35.225: bytes=32 time=223ms TTL=44 Reply from 72.51.35.225:
> > > bytes=32 time=202ms TTL=44 Reply from 72.51.35.225: bytes=32
> > time=195ms
> > > TTL=44 Reply from 72.51.35.225: bytes=32 time=210ms TTL=44  Ping
> > > statistics for 72.51.35.225:     Packets: Sent = 4, Received = 4, Lost
> > =
> > > 0 (0% loss), Approximate round trip times in milli-seconds:
> > Minimum
> > > = 195ms, Maximum = 223ms, Average = 207ms
> > > >
> > > > Tracing route to pwsweather.com [72.51.35.225] over a maximum of 30
> > > hops:    1    <1 ms    <1 ms    <1 ms  bossman.mshome.net
> > [192.168.0.1]
> > > 2   108 ms    93 ms    90 ms  10.119.160.1    3   503 ms   468 ms
> > 377
> > > ms  166.181.126.81    4   527 ms   454 ms   461 ms  166.181.126.92
> > 5
> > > 528 ms   159 ms   100 ms  166.181.113.1    6   387 ms   387 ms   389
> > ms
> > > 198.8.15.242    7   309 ms   319 ms   346 ms  198.8.15.252    8     *
> > > *        *     Request timed out.   9     *        *        *
> > > Request timed out.  10     *        *        *     Request timed out.
> > > 11     *        *        *     Request timed out.  12     *        *
> > > *     Request timed out.  13   356 ms   355 ms   327 ms  198.8.15.1
> > 14
> > > 161 ms   159 ms   139 ms  so-5-0-0.edge2.Atlanta2.Level3.net
> > > [4.71.194.17]   15   291 ms   209 ms   261 ms
> > > ae-63-51.ebr3.Atlanta2.Level3.net [4.68.103.30]   16   400 ms   386 ms
> > > 360 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]   17   206 ms
> > 197
> > > ms   198 ms  ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]   18
> > 229
> > > ms   433 ms   518 ms  ae-34-80.car4.LosAngeles1.Level3.net
> > > [4.69.144.134]   19     *        *        *     Request timed out.  20
> > > 242 ms   194 ms   204 ms  oc48-po4-0.la-sb600w-dis-2.peer1.net
> > > [216.187.88.150]   21   433 ms   506 ms   198 ms  pws0.pwsweather.com
> > > [72.51.35.225]   Trace complete.
> > > >
> > > > 2nd trace:
> > > > Tracing route to pwsweather.com [72.51.35.225] over a maximum of 30
> > > hops:    1    <1 ms    <1 ms    <1 ms  bossman.mshome.net
> > [192.168.0.1]
> > > 2   106 ms    95 ms   110 ms  10.119.160.1    3   102 ms   112 ms
> > 112
> > > ms  166.181.126.81    4   189 ms    98 ms    93 ms  166.181.126.92
> > 5
> > > 94 ms    92 ms    93 ms  166.181.113.1    6   112 ms   112 ms    94 ms
> > > 198.8.15.242    7   139 ms   159 ms   136 ms  198.8.15.252    8     *
> > > *        *     Request timed out.   9     *        *        *
> > > Request timed out.  10     *        *        *     Request timed out.
> > > 11     *        *        *     Request timed out.  12     *        *
> > > *     Request timed out.  13   147 ms   133 ms   132 ms  198.8.15.1
> > 14
> > > 157 ms   139 ms   141 ms  so-5-0-0.edge2.Atlanta2.Level3.net
> > > [4.71.194.17]   15   180 ms   140 ms   147 ms
> > > ae-73-52.ebr3.Atlanta2.Level3.net [4.68.103.62]   16   175 ms   199 ms
> > > 194 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]   17   225 ms
> > 218
> > > ms   195 ms  ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]   18
> > 389
> > > ms   223 ms   220 ms  ae-34-80.car4.LosAngeles1.Level3.net
> > > [4.69.144.134]   19     *        *        *     Request timed out.  20
> > > 232 ms   197 ms   202 ms  oc48-po4-0.la-sb600w-dis-2.peer1.net
> > > [216.187.88.150]   21   221 ms   216 ms   217 ms  pws0.pwsweather.com
> > > [72.51.35.225]   Trace complete.
> > > >
> > > > The first time out series is between U.S. Cellular IP's
> > > > second time out is between Level3.net and peer1.net
> > > >
> > > > Path ping
> > > > Tracing route to pwsweather.com [72.51.35.225] over a maximum of 30
> > > hops:
> > > > 0  weatherwatcher.mshome.net [192.168.0.119]
> > > > 1  bossman.mshome.net [192.168.0.1]
> > > > 2  10.119.160.1
> > > > 3  166.181.126.81
> > > > 4  166.181.126.92
> > > > 5  166.181.113.1
> > > > 6  198.8.15.242
> > > > 7  198.8.15.252
> > > > 8     *        *        *
> > > > Computing statistics for 200 seconds...
> > > >   Source to Here     This Node/Link
> > > > Hop  RTT    ` Lost/Sent = Pct    Lost/Sent = Pct   Address
> > > >  0
> > > weatherwatcher.mshome.net [192.168.0.119]
> > > 0/ 100 =  0%
> > > > 1    0ms      0/ 100 =  0%        0/ 100 =  0%    bossman.mshome.net
> > > [192.168.0.1]                                        0/ 100 =  0%
> > > > 2  ---       100/ 100 =100%     100/ 100 =100%   10.119.160.1
> > > >       0/ 100 =  0%
> > > > 3  ---       100/ 100 =100%     100/ 100 =100%   166.181.126.81
> > > >        0/ 100 =  0%
> > > > 4  ---       100/ 100 =100%     100/ 100 =100%   166.181.126.92
> > > >       0/ 100 =  0%
> > > > 5  192ms      0/ 100 =  0%        0/ 100 =  0%    166.181.113.1
> > > >       0/ 100 =  0%
> > > > 6  221ms      0/ 100 =  0%        0/ 100 =  0%    198.8.15.242
> > > >       100/ 100 =100%
> > > > 7  ---       100/ 100 =100%       0/ 100 =  0%    198.8.15.252
> > > >       0/ 100 =  0%
> > > > 8  ---       100/ 100 =100%       0/ 100 =  0%    weatherwatcher
> > > [0.0.0.0]
> > > > Trace complete.
> > > >
> > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> > > wuhu_software@ wrote:
> > > > >
> > > > >
> > > > > Do you have a 2nd machine that you could connect the station to? I
> > > would like to isolate whether it is that particular computer.
> > > > >
> > > > > I am not seeing anyone else that is having this issue so perhaps
> > > some strange firewall setting is stopping the response.
> > > > >
> > > > >
> > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@>
> > > wrote:
> > > > > >
> > > > > > Installed latest release posted here (152) and getting same
> > thing.
> > > > > >
> > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@>
> > > wrote:
> > > > > > >
> > > > > > > Sorry such a delay in getting back.
> > > > > > > This is from this morning:
> > > > > > >
> > > > > > > Fri Dec 03 07:26:26 2010 > PWSWeather Background Upload: Final
> > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > 0x00002ee2
> > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > Fri Dec 03 07:26:27 2010 > PWSWeather Background Upload:
> > Sending
> > >
> > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > \
> > >
> > ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> > \
> > >
> > gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> > \
> > >
> > =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> > \
> > > raw
> > > > > > > Fri Dec 03 07:27:02 2010 > PWSWeather Live Upload: Sending
> > >
> > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > \
> > >
> > ******&dateutc=2010-12-03+13%3A26%3A16&winddir=292&windspeedmph=3.5&wind\
> > \
> > >
> > gustmph=4.3&tempf=21.7&rainin=0.00&dailyrainin=0.00&baromin=30.27&dewptf\
> > \
> > >
> > =13.8&humidity=71&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> > \
> > > raw
> > > > > > > Fri Dec 03 07:28:00 2010 > PWSWeather Background Upload: Final
> > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > 0x00002ee2
> > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > Fri Dec 03 07:28:01 2010 > PWSWeather Background Upload:
> > Sending
> > >
> > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > \
> > >
> > ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> > \
> > >
> > gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> > \
> > >
> > =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> > \
> > > raw
> > > > > > > Fri Dec 03 07:28:34 2010 > PWSWeather Live Upload: Final Fatal
> > > Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > Fri Dec 03 07:29:32 2010 > PWSWeather Background Upload: Final
> > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > 0x00002ee2
> > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > Fri Dec 03 07:29:33 2010 > PWSWeather Background Upload:
> > Sending
> > >
> > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > \
> > >
> > ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> > \
> > >
> > gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> > \
> > >
> > =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> > \
> > > raw
> > > > > > > Fri Dec 03 07:31:04 2010 > PWSWeather Background Upload: Final
> > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > 0x00002ee2
> > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > Fri Dec 03 07:31:05 2010 > PWSWeather Background Upload:
> > Sending
> > >
> > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > \
> > >
> > ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> > \
> > >
> > gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> > \
> > >
> > =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> > \
> > > raw
> > > > > > >
> > > > > > >
> > > > > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> > > <wuhu_software@> wrote:
> > > > > > > >
> > > > > > > >
> > > > > > > > Lets see if we can isolate the problem with your uploads.
> > > > > > > >
> > > > > > > > I did find an issue with their server returning a new return
> > > string indicating that the upload was successful. Previously, the
> > server
> > > responded with "OK" indicating that it had accepted the upload. I
> > > monitored my upload today and found it responding with "Data Logged
> > and
> > > posted in METAR mirror". I have added this new result code in the
> > > software and it will be in the next release, probably when we figure
> > out
> > > what is going on with your station. Even with the failure to spot the
> > > new result code, my station has been uploading to PWSWeather
> > > un-interrupted.
> > > > > > > >
> > > > > > > > To attempt to debug your poblem, what you need to do is go
> > to
> > > the Log screen, un-check "Only Errors", un-check all check boxes other
> > > servers and services except PWSWeather. Do not check "Show Console
> > Com.
> > > Errors" as this will clutter the log.
> > > > > > > >
> > > > > > > > Next, wait a few minutes until the next upload to PWSWeather
> > > happens. You should see a couple new entries in the log, what was sent
> > > to the PWSWeather server and the servers response. Select those lines
> > in
> > > the log then hit the Copy Selected button to copy these entries to
> > your
> > > Windows clipboard. Next, post a message here with those entries.
> > > > > > > >
> > > > > > > >
> > > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf"
> > <wolf9sbu@>
> > > wrote:
> > > > > > > > >
> > > > > > > > > PWS is NOT getting the data. The connection times out.
> > Their
> > > display page of my data shows old data, however, occasonly data gets
> > > through
> > > > > > > > > and shows. Then their display page reverts back to the
> > same
> > > old data set.
> > > > > > > > > I have reviewed firewall and router.
> > > > > > > > >
> > > > > > > > > --- In wuhu_software_group@yahoogroups.com,
> > "wuhu_software"
> > > <wuhu_software@> wrote:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > One user reported the following was a router problem.
> > > Apparently PWS weather uses multiple servers, and the one you send to
> > > might not be the one that responds. If the router is does not allow
> > > this, the program will not see the response from their server.
> > > > > > > > > >
> > > > > > > > > > ---
> > > > > > > > > >
> > > > > > > > > > Found It!!!
> > > > > > > > > >
> > > > > > > > > > Yes, the router had updated firmware and change two
> > > settings on the router. UDP and TCP endpoint filtering was set to
> > > address restricted instead of endpoint independent. What this does is
> > > not allow communications if the return (ack) is from a different
> > address
> > > than the sendto address. This is why I could get the data to PWS but
> > it
> > > could not ACK my packets.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf"
> > > <wolf9sbu@> wrote:
> > > > > > > > > > >
> > > > > > > > > > > I have been running WUHU for a long time with no
> > > trouble.
> > > > > > > > > > > Recently, PWS and Hamweather reports have been "stuck"
> > > on an older set of data. I contacted PWS and they claimed the issue
> > was
> > > on my end.
> > > > > > > > > > > I updated to the latest version of WUHU and now all
> > > reports go through EXCEPT PWS. the following errors repeat in the log:
> > > > > > > > > > > Sat Nov 20 10:20:10 2010 > PWSWeather Live Upload:
> > Final
> > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > 0x00002ee2
> > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > > > Sat Nov 20 10:20:44 2010 > PWSWeather Background
> > Upload:
> > > Final Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > 0x00002ee2 (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > > >
> > > > > > > > > > > Any feedback?
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

based on complaints against them. Usually it is spy ware or unwanted emailing


--- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@...>
wrote:
>
>
> No problem.
>
> I did install that effetech software and did not see a problem.
>
> Are they questionable because of spyware or something?
>
> I did not notice anything.
>
> Thanks.
>
>
> --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@> wrote:
> >
> > According to "Web of Trust" plugin for Firefox, (www.mywot.com/)
http://www.effetech.com/download/ "has a poor reputation."
> > So... I'm not going there and recommending folks to go there isn't cool.
> > Thanks for all your effort however,
> > I'm all done with this on my end. As was mentioned by a few early in this
string, they just shut of PWS upload and didn't be bothered.
> > I joined the forum to try to fix it and I've jumped through enough hoops.
Every thing else I do on the Internet works including FTP. web sites, forums,
email... is working along with WUHU uploads to everything EXCEPT PWS. Comodo
doesn't stop anything else I want to do. I imagine there are quit a few who just
shut it off and never bothered joining the forum to figure it out so you won't
get "Ya I had that problem" from many of the folks that did cause their not
here. I don't check Yahoo often unless there is something of interest to me. I'm
done being interested in this issue and I'll just uncheck PWS from logging and
remove all references from my web pages. When an occasional post goes through to
them as it does now, that's all fine for whoever is interested.
> > Since everything else is working so smoothly, at this point, in my humble
opinion, it's a PWS issue that they can figure out.
> > Again, thanks for your efforts and I will continue to provide data to all
who are willing to receive it without me jumping through hoops to get it to
them.
> > Happy Days
> >
> >
> > --- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@>
wrote:
> > >
> > >
> > > Here is something else we might try:
> > > Download and install the following:
> > > EffeTech HTTP Sniffer v4.1 <http://www.effetech.com/download/>
> > > During the install, make sure you read the instructions and answer Yes
> > > to install the WinPCAP, that is a low-level network driver than can
> > > intercept network packets.
> > > After install, under the programs Sniff menu, press Start.
> > > This will capture all http:// traffic on the machine.
> > > After you capture your attempted upload to PWSWeather, copy and paste
> > > the header and the response to the request (if any).
> > >
> > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> > > <wuhu_software@> wrote:
> > > >
> > > >
> > > > It is interesting that you have a 192.168.0.X address. Can you chance
> > > > that to a 192.168.1.X address?
> > > > I am also concerned about the Comodo firewall being used. You might
> > > try
> > > > removing it completely to see if that makes a difference.
> > > > Finally, I found this note in a tips and tricks for XP. It might not
> > > > hurt to check these settings. I am using the InternetOpenURL() so this
> > > > may or may not be an issue for you.
> > > > ---
> > > > 232. Increasing number of connections per http server Folks, HTTP
> > > > Protocol limits number of maximum connections to a HTTP server to 2.
> > > > Following table explains restrictions placed by various HTTP
> > > PROTOCOLS.
> > > > This is the as per the RFC specifications.
> > > > 1. HTTP 1.0 conforming server 4 simultaneous connections 2. HTTP 1.1
> > > > conforming server 2 simputaneous connections Limitation caused by this
> > > > is visible whenever your applications make calls like HttpSendRequest
> > > > and InternetOpenURL which take longer to complete as they wait for
> > > > previous connections to be freed up before their requests are sent.
> > > > You can configure WinInet to exceed this limit by creating and setting
> > > > the registry entries. Open registry (by going to START-RUN and
> > > entering
> > > > regedit) and navigate to:
> > > >
> > > >
> > > [HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Intern\
> > > \
> > > > et Settings]
> > > > and look for values of "MaxConnectionsPerServer" and
> > > > "MaxConnectionsPer1_0Server ".
> > > > If you don't see then add two key by the names
> > > "MaxConnectionsPerServer"
> > > > and "MaxConnectionsPer1_0Server " respectively. Default values are as
> > > > MaxConnectionsPerServer = 2 MaxConnectionsPer1_0Server = 4 Changes its
> > > > value to a number you want.
> > > > --- In wuhu_software_group@yahoogroups.com, "Wolf" wolf9sbu@ wrote:
> > > > >
> > > > > Different machine, no firewall, no router.
> > > > > Also see ping, tracert (2) and path ping below.
> > > > >
> > > > > Fri Dec 03 11:46:59 2010 > PWSWeather Live Upload: Final Fatal Eror
> > > > (No more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
> > > > ERROR_INTERNET_TIMEOUT.
> > > > > Fri Dec 03 11:47:50 2010 > PWSWeather Background Upload: Final Fatal
> > > > Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > Fri Dec 03 11:47:50 2010 > PWSWeather Background Upload: Sending
> > > >
> > > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > > \
> > > >
> > > ******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> > > \
> > > >
> > > ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> > > \
> > > >
> > > 13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> > > \
> > > > aw
> > > > > Fri Dec 03 11:49:21 2010 > PWSWeather Background Upload: Final Fatal
> > > > Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > Fri Dec 03 11:49:21 2010 > PWSWeather Background Upload: Sending
> > > >
> > > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > > \
> > > >
> > > ******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> > > \
> > > >
> > > ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> > > \
> > > >
> > > 13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> > > \
> > > > aw
> > > > > Fri Dec 03 11:50:52 2010 > PWSWeather Background Upload: Final Fatal
> > > > Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > Fri Dec 03 11:50:52 2010 > PWSWeather Background Upload: Sending
> > > >
> > > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > > \
> > > >
> > > ******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> > > \
> > > >
> > > ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> > > \
> > > >
> > > 13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> > > \
> > > > aw
> > > > >
> > > > > Pinging pwsweather.com [72.51.35.225] with 32 bytes of data:  Reply
> > > > from 72.51.35.225: bytes=32 time=223ms TTL=44 Reply from 72.51.35.225:
> > > > bytes=32 time=202ms TTL=44 Reply from 72.51.35.225: bytes=32
> > > time=195ms
> > > > TTL=44 Reply from 72.51.35.225: bytes=32 time=210ms TTL=44  Ping
> > > > statistics for 72.51.35.225:     Packets: Sent = 4, Received = 4, Lost
> > > =
> > > > 0 (0% loss), Approximate round trip times in milli-seconds:
> > > Minimum
> > > > = 195ms, Maximum = 223ms, Average = 207ms
> > > > >
> > > > > Tracing route to pwsweather.com [72.51.35.225] over a maximum of 30
> > > > hops:    1    <1 ms    <1 ms    <1 ms  bossman.mshome.net
> > > [192.168.0.1]
> > > > 2   108 ms    93 ms    90 ms  10.119.160.1    3   503 ms   468 ms
> > > 377
> > > > ms  166.181.126.81    4   527 ms   454 ms   461 ms  166.181.126.92
> > > 5
> > > > 528 ms   159 ms   100 ms  166.181.113.1    6   387 ms   387 ms   389
> > > ms
> > > > 198.8.15.242    7   309 ms   319 ms   346 ms  198.8.15.252    8     *
> > > > *        *     Request timed out.   9     *        *        *
> > > > Request timed out.  10     *        *        *     Request timed out.
> > > > 11     *        *        *     Request timed out.  12     *        *
> > > > *     Request timed out.  13   356 ms   355 ms   327 ms  198.8.15.1
> > > 14
> > > > 161 ms   159 ms   139 ms  so-5-0-0.edge2.Atlanta2.Level3.net
> > > > [4.71.194.17]   15   291 ms   209 ms   261 ms
> > > > ae-63-51.ebr3.Atlanta2.Level3.net [4.68.103.30]   16   400 ms   386 ms
> > > > 360 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]   17   206 ms
> > > 197
> > > > ms   198 ms  ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]   18
> > > 229
> > > > ms   433 ms   518 ms  ae-34-80.car4.LosAngeles1.Level3.net
> > > > [4.69.144.134]   19     *        *        *     Request timed out.  20
> > > > 242 ms   194 ms   204 ms  oc48-po4-0.la-sb600w-dis-2.peer1.net
> > > > [216.187.88.150]   21   433 ms   506 ms   198 ms  pws0.pwsweather.com
> > > > [72.51.35.225]   Trace complete.
> > > > >
> > > > > 2nd trace:
> > > > > Tracing route to pwsweather.com [72.51.35.225] over a maximum of 30
> > > > hops:    1    <1 ms    <1 ms    <1 ms  bossman.mshome.net
> > > [192.168.0.1]
> > > > 2   106 ms    95 ms   110 ms  10.119.160.1    3   102 ms   112 ms
> > > 112
> > > > ms  166.181.126.81    4   189 ms    98 ms    93 ms  166.181.126.92
> > > 5
> > > > 94 ms    92 ms    93 ms  166.181.113.1    6   112 ms   112 ms    94 ms
> > > > 198.8.15.242    7   139 ms   159 ms   136 ms  198.8.15.252    8     *
> > > > *        *     Request timed out.   9     *        *        *
> > > > Request timed out.  10     *        *        *     Request timed out.
> > > > 11     *        *        *     Request timed out.  12     *        *
> > > > *     Request timed out.  13   147 ms   133 ms   132 ms  198.8.15.1
> > > 14
> > > > 157 ms   139 ms   141 ms  so-5-0-0.edge2.Atlanta2.Level3.net
> > > > [4.71.194.17]   15   180 ms   140 ms   147 ms
> > > > ae-73-52.ebr3.Atlanta2.Level3.net [4.68.103.62]   16   175 ms   199 ms
> > > > 194 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]   17   225 ms
> > > 218
> > > > ms   195 ms  ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]   18
> > > 389
> > > > ms   223 ms   220 ms  ae-34-80.car4.LosAngeles1.Level3.net
> > > > [4.69.144.134]   19     *        *        *     Request timed out.  20
> > > > 232 ms   197 ms   202 ms  oc48-po4-0.la-sb600w-dis-2.peer1.net
> > > > [216.187.88.150]   21   221 ms   216 ms   217 ms  pws0.pwsweather.com
> > > > [72.51.35.225]   Trace complete.
> > > > >
> > > > > The first time out series is between U.S. Cellular IP's
> > > > > second time out is between Level3.net and peer1.net
> > > > >
> > > > > Path ping
> > > > > Tracing route to pwsweather.com [72.51.35.225] over a maximum of 30
> > > > hops:
> > > > > 0  weatherwatcher.mshome.net [192.168.0.119]
> > > > > 1  bossman.mshome.net [192.168.0.1]
> > > > > 2  10.119.160.1
> > > > > 3  166.181.126.81
> > > > > 4  166.181.126.92
> > > > > 5  166.181.113.1
> > > > > 6  198.8.15.242
> > > > > 7  198.8.15.252
> > > > > 8     *        *        *
> > > > > Computing statistics for 200 seconds...
> > > > >   Source to Here     This Node/Link
> > > > > Hop  RTT    ` Lost/Sent = Pct    Lost/Sent = Pct   Address
> > > > >  0
> > > > weatherwatcher.mshome.net [192.168.0.119]
> > > > 0/ 100 =  0%
> > > > > 1    0ms      0/ 100 =  0%        0/ 100 =  0%    bossman.mshome.net
> > > > [192.168.0.1]                                        0/ 100 =  0%
> > > > > 2  ---       100/ 100 =100%     100/ 100 =100%   10.119.160.1
> > > > >       0/ 100 =  0%
> > > > > 3  ---       100/ 100 =100%     100/ 100 =100%   166.181.126.81
> > > > >        0/ 100 =  0%
> > > > > 4  ---       100/ 100 =100%     100/ 100 =100%   166.181.126.92
> > > > >       0/ 100 =  0%
> > > > > 5  192ms      0/ 100 =  0%        0/ 100 =  0%    166.181.113.1
> > > > >       0/ 100 =  0%
> > > > > 6  221ms      0/ 100 =  0%        0/ 100 =  0%    198.8.15.242
> > > > >       100/ 100 =100%
> > > > > 7  ---       100/ 100 =100%       0/ 100 =  0%    198.8.15.252
> > > > >       0/ 100 =  0%
> > > > > 8  ---       100/ 100 =100%       0/ 100 =  0%    weatherwatcher
> > > > [0.0.0.0]
> > > > > Trace complete.
> > > > >
> > > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> > > > wuhu_software@ wrote:
> > > > > >
> > > > > >
> > > > > > Do you have a 2nd machine that you could connect the station to? I
> > > > would like to isolate whether it is that particular computer.
> > > > > >
> > > > > > I am not seeing anyone else that is having this issue so perhaps
> > > > some strange firewall setting is stopping the response.
> > > > > >
> > > > > >
> > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@>
> > > > wrote:
> > > > > > >
> > > > > > > Installed latest release posted here (152) and getting same
> > > thing.
> > > > > > >
> > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@>
> > > > wrote:
> > > > > > > >
> > > > > > > > Sorry such a delay in getting back.
> > > > > > > > This is from this morning:
> > > > > > > >
> > > > > > > > Fri Dec 03 07:26:26 2010 > PWSWeather Background Upload: Final
> > > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > 0x00002ee2
> > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > Fri Dec 03 07:26:27 2010 > PWSWeather Background Upload:
> > > Sending
> > > >
> > > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > > \
> > > >
> > > ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> > > \
> > > >
> > > gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> > > \
> > > >
> > > =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> > > \
> > > > raw
> > > > > > > > Fri Dec 03 07:27:02 2010 > PWSWeather Live Upload: Sending
> > > >
> > > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > > \
> > > >
> > > ******&dateutc=2010-12-03+13%3A26%3A16&winddir=292&windspeedmph=3.5&wind\
> > > \
> > > >
> > > gustmph=4.3&tempf=21.7&rainin=0.00&dailyrainin=0.00&baromin=30.27&dewptf\
> > > \
> > > >
> > > =13.8&humidity=71&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> > > \
> > > > raw
> > > > > > > > Fri Dec 03 07:28:00 2010 > PWSWeather Background Upload: Final
> > > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > 0x00002ee2
> > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > Fri Dec 03 07:28:01 2010 > PWSWeather Background Upload:
> > > Sending
> > > >
> > > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > > \
> > > >
> > > ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> > > \
> > > >
> > > gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> > > \
> > > >
> > > =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> > > \
> > > > raw
> > > > > > > > Fri Dec 03 07:28:34 2010 > PWSWeather Live Upload: Final Fatal
> > > > Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > Fri Dec 03 07:29:32 2010 > PWSWeather Background Upload: Final
> > > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > 0x00002ee2
> > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > Fri Dec 03 07:29:33 2010 > PWSWeather Background Upload:
> > > Sending
> > > >
> > > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > > \
> > > >
> > > ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> > > \
> > > >
> > > gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> > > \
> > > >
> > > =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> > > \
> > > > raw
> > > > > > > > Fri Dec 03 07:31:04 2010 > PWSWeather Background Upload: Final
> > > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > 0x00002ee2
> > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > Fri Dec 03 07:31:05 2010 > PWSWeather Background Upload:
> > > Sending
> > > >
> > > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > > \
> > > >
> > > ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> > > \
> > > >
> > > gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> > > \
> > > >
> > > =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> > > \
> > > > raw
> > > > > > > >
> > > > > > > >
> > > > > > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> > > > <wuhu_software@> wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Lets see if we can isolate the problem with your uploads.
> > > > > > > > >
> > > > > > > > > I did find an issue with their server returning a new return
> > > > string indicating that the upload was successful. Previously, the
> > > server
> > > > responded with "OK" indicating that it had accepted the upload. I
> > > > monitored my upload today and found it responding with "Data Logged
> > > and
> > > > posted in METAR mirror". I have added this new result code in the
> > > > software and it will be in the next release, probably when we figure
> > > out
> > > > what is going on with your station. Even with the failure to spot the
> > > > new result code, my station has been uploading to PWSWeather
> > > > un-interrupted.
> > > > > > > > >
> > > > > > > > > To attempt to debug your poblem, what you need to do is go
> > > to
> > > > the Log screen, un-check "Only Errors", un-check all check boxes other
> > > > servers and services except PWSWeather. Do not check "Show Console
> > > Com.
> > > > Errors" as this will clutter the log.
> > > > > > > > >
> > > > > > > > > Next, wait a few minutes until the next upload to PWSWeather
> > > > happens. You should see a couple new entries in the log, what was sent
> > > > to the PWSWeather server and the servers response. Select those lines
> > > in
> > > > the log then hit the Copy Selected button to copy these entries to
> > > your
> > > > Windows clipboard. Next, post a message here with those entries.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf"
> > > <wolf9sbu@>
> > > > wrote:
> > > > > > > > > >
> > > > > > > > > > PWS is NOT getting the data. The connection times out.
> > > Their
> > > > display page of my data shows old data, however, occasonly data gets
> > > > through
> > > > > > > > > > and shows. Then their display page reverts back to the
> > > same
> > > > old data set.
> > > > > > > > > > I have reviewed firewall and router.
> > > > > > > > > >
> > > > > > > > > > --- In wuhu_software_group@yahoogroups.com,
> > > "wuhu_software"
> > > > <wuhu_software@> wrote:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > One user reported the following was a router problem.
> > > > Apparently PWS weather uses multiple servers, and the one you send to
> > > > might not be the one that responds. If the router is does not allow
> > > > this, the program will not see the response from their server.
> > > > > > > > > > >
> > > > > > > > > > > ---
> > > > > > > > > > >
> > > > > > > > > > > Found It!!!
> > > > > > > > > > >
> > > > > > > > > > > Yes, the router had updated firmware and change two
> > > > settings on the router. UDP and TCP endpoint filtering was set to
> > > > address restricted instead of endpoint independent. What this does is
> > > > not allow communications if the return (ack) is from a different
> > > address
> > > > than the sendto address. This is why I could get the data to PWS but
> > > it
> > > > could not ACK my packets.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf"
> > > > <wolf9sbu@> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > I have been running WUHU for a long time with no
> > > > trouble.
> > > > > > > > > > > > Recently, PWS and Hamweather reports have been "stuck"
> > > > on an older set of data. I contacted PWS and they claimed the issue
> > > was
> > > > on my end.
> > > > > > > > > > > > I updated to the latest version of WUHU and now all
> > > > reports go through EXCEPT PWS. the following errors repeat in the log:
> > > > > > > > > > > > Sat Nov 20 10:20:10 2010 > PWSWeather Live Upload:
> > > Final
> > > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > 0x00002ee2
> > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > > > > Sat Nov 20 10:20:44 2010 > PWSWeather Background
> > > Upload:
> > > > Final Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > > 0x00002ee2 (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > > > >
> > > > > > > > > > > > Any feedback?
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

No worries, I removed it and went with the Fiddle program. It looks just as good
if not better and it is freeware.

Thanks for the alert though... I should be more careful about grabbing shiny
things and installing them.


--- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@...> wrote:
>
> based on complaints against them. Usually it is spy ware or unwanted emailing
>
>
> --- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@>
wrote:
> >
> >
> > No problem.
> >
> > I did install that effetech software and did not see a problem.
> >
> > Are they questionable because of spyware or something?
> >
> > I did not notice anything.
> >
> > Thanks.
> >
> >
> > --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@> wrote:
> > >
> > > According to "Web of Trust" plugin for Firefox, (www.mywot.com/)
http://www.effetech.com/download/ "has a poor reputation."
> > > So... I'm not going there and recommending folks to go there isn't cool.
> > > Thanks for all your effort however,
> > > I'm all done with this on my end. As was mentioned by a few early in this
string, they just shut of PWS upload and didn't be bothered.
> > > I joined the forum to try to fix it and I've jumped through enough hoops.
Every thing else I do on the Internet works including FTP. web sites, forums,
email... is working along with WUHU uploads to everything EXCEPT PWS. Comodo
doesn't stop anything else I want to do. I imagine there are quit a few who just
shut it off and never bothered joining the forum to figure it out so you won't
get "Ya I had that problem" from many of the folks that did cause their not
here. I don't check Yahoo often unless there is something of interest to me. I'm
done being interested in this issue and I'll just uncheck PWS from logging and
remove all references from my web pages. When an occasional post goes through to
them as it does now, that's all fine for whoever is interested.
> > > Since everything else is working so smoothly, at this point, in my humble
opinion, it's a PWS issue that they can figure out.
> > > Again, thanks for your efforts and I will continue to provide data to all
who are willing to receive it without me jumping through hoops to get it to
them.
> > > Happy Days
> > >
> > >
> > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
<wuhu_software@> wrote:
> > > >
> > > >
> > > > Here is something else we might try:
> > > > Download and install the following:
> > > > EffeTech HTTP Sniffer v4.1 <http://www.effetech.com/download/>
> > > > During the install, make sure you read the instructions and answer Yes
> > > > to install the WinPCAP, that is a low-level network driver than can
> > > > intercept network packets.
> > > > After install, under the programs Sniff menu, press Start.
> > > > This will capture all http:// traffic on the machine.
> > > > After you capture your attempted upload to PWSWeather, copy and paste
> > > > the header and the response to the request (if any).
> > > >
> > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> > > > <wuhu_software@> wrote:
> > > > >
> > > > >
> > > > > It is interesting that you have a 192.168.0.X address. Can you chance
> > > > > that to a 192.168.1.X address?
> > > > > I am also concerned about the Comodo firewall being used. You might
> > > > try
> > > > > removing it completely to see if that makes a difference.
> > > > > Finally, I found this note in a tips and tricks for XP. It might not
> > > > > hurt to check these settings. I am using the InternetOpenURL() so this
> > > > > may or may not be an issue for you.
> > > > > ---
> > > > > 232. Increasing number of connections per http server Folks, HTTP
> > > > > Protocol limits number of maximum connections to a HTTP server to 2.
> > > > > Following table explains restrictions placed by various HTTP
> > > > PROTOCOLS.
> > > > > This is the as per the RFC specifications.
> > > > > 1. HTTP 1.0 conforming server 4 simultaneous connections 2. HTTP 1.1
> > > > > conforming server 2 simputaneous connections Limitation caused by this
> > > > > is visible whenever your applications make calls like HttpSendRequest
> > > > > and InternetOpenURL which take longer to complete as they wait for
> > > > > previous connections to be freed up before their requests are sent.
> > > > > You can configure WinInet to exceed this limit by creating and setting
> > > > > the registry entries. Open registry (by going to START-RUN and
> > > > entering
> > > > > regedit) and navigate to:
> > > > >
> > > > >
> > > >
[HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Intern\
> > > > \
> > > > > et Settings]
> > > > > and look for values of "MaxConnectionsPerServer" and
> > > > > "MaxConnectionsPer1_0Server ".
> > > > > If you don't see then add two key by the names
> > > > "MaxConnectionsPerServer"
> > > > > and "MaxConnectionsPer1_0Server " respectively. Default values are as
> > > > > MaxConnectionsPerServer = 2 MaxConnectionsPer1_0Server = 4 Changes its
> > > > > value to a number you want.
> > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf" wolf9sbu@ wrote:
> > > > > >
> > > > > > Different machine, no firewall, no router.
> > > > > > Also see ping, tracert (2) and path ping below.
> > > > > >
> > > > > > Fri Dec 03 11:46:59 2010 > PWSWeather Live Upload: Final Fatal Eror
> > > > > (No more retries) InternetOpenUrl() returned error 0x00002ee2 (12002),
> > > > > ERROR_INTERNET_TIMEOUT.
> > > > > > Fri Dec 03 11:47:50 2010 > PWSWeather Background Upload: Final Fatal
> > > > > Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > Fri Dec 03 11:47:50 2010 > PWSWeather Background Upload: Sending
> > > > >
> > > >
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > > > \
> > > > >
> > > >
******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> > > > \
> > > > >
> > > >
ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> > > > \
> > > > >
> > > >
13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> > > > \
> > > > > aw
> > > > > > Fri Dec 03 11:49:21 2010 > PWSWeather Background Upload: Final Fatal
> > > > > Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > Fri Dec 03 11:49:21 2010 > PWSWeather Background Upload: Sending
> > > > >
> > > >
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > > > \
> > > > >
> > > >
******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> > > > \
> > > > >
> > > >
ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> > > > \
> > > > >
> > > >
13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> > > > \
> > > > > aw
> > > > > > Fri Dec 03 11:50:52 2010 > PWSWeather Background Upload: Final Fatal
> > > > > Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > Fri Dec 03 11:50:52 2010 > PWSWeather Background Upload: Sending
> > > > >
> > > >
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > > > \
> > > > >
> > > >
******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> > > > \
> > > > >
> > > >
ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> > > > \
> > > > >
> > > >
13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> > > > \
> > > > > aw
> > > > > >
> > > > > > Pinging pwsweather.com [72.51.35.225] with 32 bytes of data:  Reply
> > > > > from 72.51.35.225: bytes=32 time=223ms TTL=44 Reply from 72.51.35.225:
> > > > > bytes=32 time=202ms TTL=44 Reply from 72.51.35.225: bytes=32
> > > > time=195ms
> > > > > TTL=44 Reply from 72.51.35.225: bytes=32 time=210ms TTL=44  Ping
> > > > > statistics for 72.51.35.225:     Packets: Sent = 4, Received = 4, Lost
> > > > =
> > > > > 0 (0% loss), Approximate round trip times in milli-seconds:
> > > > Minimum
> > > > > = 195ms, Maximum = 223ms, Average = 207ms
> > > > > >
> > > > > > Tracing route to pwsweather.com [72.51.35.225] over a maximum of 30
> > > > > hops:    1    <1 ms    <1 ms    <1 ms  bossman.mshome.net
> > > > [192.168.0.1]
> > > > > 2   108 ms    93 ms    90 ms  10.119.160.1    3   503 ms   468 ms
> > > > 377
> > > > > ms  166.181.126.81    4   527 ms   454 ms   461 ms  166.181.126.92
> > > > 5
> > > > > 528 ms   159 ms   100 ms  166.181.113.1    6   387 ms   387 ms   389
> > > > ms
> > > > > 198.8.15.242    7   309 ms   319 ms   346 ms  198.8.15.252    8     *
> > > > > *        *     Request timed out.   9     *        *        *
> > > > > Request timed out.  10     *        *        *     Request timed out.
> > > > > 11     *        *        *     Request timed out.  12     *        *
> > > > > *     Request timed out.  13   356 ms   355 ms   327 ms  198.8.15.1
> > > > 14
> > > > > 161 ms   159 ms   139 ms  so-5-0-0.edge2.Atlanta2.Level3.net
> > > > > [4.71.194.17]   15   291 ms   209 ms   261 ms
> > > > > ae-63-51.ebr3.Atlanta2.Level3.net [4.68.103.30]   16   400 ms   386 ms
> > > > > 360 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]   17   206 ms
> > > > 197
> > > > > ms   198 ms  ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]   18
> > > > 229
> > > > > ms   433 ms   518 ms  ae-34-80.car4.LosAngeles1.Level3.net
> > > > > [4.69.144.134]   19     *        *        *     Request timed out.  20
> > > > > 242 ms   194 ms   204 ms  oc48-po4-0.la-sb600w-dis-2.peer1.net
> > > > > [216.187.88.150]   21   433 ms   506 ms   198 ms  pws0.pwsweather.com
> > > > > [72.51.35.225]   Trace complete.
> > > > > >
> > > > > > 2nd trace:
> > > > > > Tracing route to pwsweather.com [72.51.35.225] over a maximum of 30
> > > > > hops:    1    <1 ms    <1 ms    <1 ms  bossman.mshome.net
> > > > [192.168.0.1]
> > > > > 2   106 ms    95 ms   110 ms  10.119.160.1    3   102 ms   112 ms
> > > > 112
> > > > > ms  166.181.126.81    4   189 ms    98 ms    93 ms  166.181.126.92
> > > > 5
> > > > > 94 ms    92 ms    93 ms  166.181.113.1    6   112 ms   112 ms    94 ms
> > > > > 198.8.15.242    7   139 ms   159 ms   136 ms  198.8.15.252    8     *
> > > > > *        *     Request timed out.   9     *        *        *
> > > > > Request timed out.  10     *        *        *     Request timed out.
> > > > > 11     *        *        *     Request timed out.  12     *        *
> > > > > *     Request timed out.  13   147 ms   133 ms   132 ms  198.8.15.1
> > > > 14
> > > > > 157 ms   139 ms   141 ms  so-5-0-0.edge2.Atlanta2.Level3.net
> > > > > [4.71.194.17]   15   180 ms   140 ms   147 ms
> > > > > ae-73-52.ebr3.Atlanta2.Level3.net [4.68.103.62]   16   175 ms   199 ms
> > > > > 194 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]   17   225 ms
> > > > 218
> > > > > ms   195 ms  ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]   18
> > > > 389
> > > > > ms   223 ms   220 ms  ae-34-80.car4.LosAngeles1.Level3.net
> > > > > [4.69.144.134]   19     *        *        *     Request timed out.  20
> > > > > 232 ms   197 ms   202 ms  oc48-po4-0.la-sb600w-dis-2.peer1.net
> > > > > [216.187.88.150]   21   221 ms   216 ms   217 ms  pws0.pwsweather.com
> > > > > [72.51.35.225]   Trace complete.
> > > > > >
> > > > > > The first time out series is between U.S. Cellular IP's
> > > > > > second time out is between Level3.net and peer1.net
> > > > > >
> > > > > > Path ping
> > > > > > Tracing route to pwsweather.com [72.51.35.225] over a maximum of 30
> > > > > hops:
> > > > > > 0  weatherwatcher.mshome.net [192.168.0.119]
> > > > > > 1  bossman.mshome.net [192.168.0.1]
> > > > > > 2  10.119.160.1
> > > > > > 3  166.181.126.81
> > > > > > 4  166.181.126.92
> > > > > > 5  166.181.113.1
> > > > > > 6  198.8.15.242
> > > > > > 7  198.8.15.252
> > > > > > 8     *        *        *
> > > > > > Computing statistics for 200 seconds...
> > > > > >   Source to Here     This Node/Link
> > > > > > Hop  RTT    ` Lost/Sent = Pct    Lost/Sent = Pct   Address
> > > > > >  0
> > > > > weatherwatcher.mshome.net [192.168.0.119]
> > > > > 0/ 100 =  0%
> > > > > > 1    0ms      0/ 100 =  0%        0/ 100 =  0%    bossman.mshome.net
> > > > > [192.168.0.1]                                        0/ 100 =  0%
> > > > > > 2  ---       100/ 100 =100%     100/ 100 =100%   10.119.160.1
> > > > > >       0/ 100 =  0%
> > > > > > 3  ---       100/ 100 =100%     100/ 100 =100%   166.181.126.81
> > > > > >        0/ 100 =  0%
> > > > > > 4  ---       100/ 100 =100%     100/ 100 =100%   166.181.126.92
> > > > > >       0/ 100 =  0%
> > > > > > 5  192ms      0/ 100 =  0%        0/ 100 =  0%    166.181.113.1
> > > > > >       0/ 100 =  0%
> > > > > > 6  221ms      0/ 100 =  0%        0/ 100 =  0%    198.8.15.242
> > > > > >       100/ 100 =100%
> > > > > > 7  ---       100/ 100 =100%       0/ 100 =  0%    198.8.15.252
> > > > > >       0/ 100 =  0%
> > > > > > 8  ---       100/ 100 =100%       0/ 100 =  0%    weatherwatcher
> > > > > [0.0.0.0]
> > > > > > Trace complete.
> > > > > >
> > > > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> > > > > wuhu_software@ wrote:
> > > > > > >
> > > > > > >
> > > > > > > Do you have a 2nd machine that you could connect the station to? I
> > > > > would like to isolate whether it is that particular computer.
> > > > > > >
> > > > > > > I am not seeing anyone else that is having this issue so perhaps
> > > > > some strange firewall setting is stopping the response.
> > > > > > >
> > > > > > >
> > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@>
> > > > > wrote:
> > > > > > > >
> > > > > > > > Installed latest release posted here (152) and getting same
> > > > thing.
> > > > > > > >
> > > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@>
> > > > > wrote:
> > > > > > > > >
> > > > > > > > > Sorry such a delay in getting back.
> > > > > > > > > This is from this morning:
> > > > > > > > >
> > > > > > > > > Fri Dec 03 07:26:26 2010 > PWSWeather Background Upload: Final
> > > > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > > 0x00002ee2
> > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > Fri Dec 03 07:26:27 2010 > PWSWeather Background Upload:
> > > > Sending
> > > > >
> > > >
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > > > \
> > > > >
> > > >
******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> > > > \
> > > > >
> > > >
gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> > > > \
> > > > >
> > > >
=12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> > > > \
> > > > > raw
> > > > > > > > > Fri Dec 03 07:27:02 2010 > PWSWeather Live Upload: Sending
> > > > >
> > > >
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > > > \
> > > > >
> > > >
******&dateutc=2010-12-03+13%3A26%3A16&winddir=292&windspeedmph=3.5&wind\
> > > > \
> > > > >
> > > >
gustmph=4.3&tempf=21.7&rainin=0.00&dailyrainin=0.00&baromin=30.27&dewptf\
> > > > \
> > > > >
> > > >
=13.8&humidity=71&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> > > > \
> > > > > raw
> > > > > > > > > Fri Dec 03 07:28:00 2010 > PWSWeather Background Upload: Final
> > > > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > > 0x00002ee2
> > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > Fri Dec 03 07:28:01 2010 > PWSWeather Background Upload:
> > > > Sending
> > > > >
> > > >
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > > > \
> > > > >
> > > >
******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> > > > \
> > > > >
> > > >
gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> > > > \
> > > > >
> > > >
=12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> > > > \
> > > > > raw
> > > > > > > > > Fri Dec 03 07:28:34 2010 > PWSWeather Live Upload: Final Fatal
> > > > > Eror (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > Fri Dec 03 07:29:32 2010 > PWSWeather Background Upload: Final
> > > > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > > 0x00002ee2
> > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > Fri Dec 03 07:29:33 2010 > PWSWeather Background Upload:
> > > > Sending
> > > > >
> > > >
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > > > \
> > > > >
> > > >
******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> > > > \
> > > > >
> > > >
gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> > > > \
> > > > >
> > > >
=12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> > > > \
> > > > > raw
> > > > > > > > > Fri Dec 03 07:31:04 2010 > PWSWeather Background Upload: Final
> > > > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > > 0x00002ee2
> > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > Fri Dec 03 07:31:05 2010 > PWSWeather Background Upload:
> > > > Sending
> > > > >
> > > >
URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > > > \
> > > > >
> > > >
******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> > > > \
> > > > >
> > > >
gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> > > > \
> > > > >
> > > >
=12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> > > > \
> > > > > raw
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> > > > > <wuhu_software@> wrote:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Lets see if we can isolate the problem with your uploads.
> > > > > > > > > >
> > > > > > > > > > I did find an issue with their server returning a new return
> > > > > string indicating that the upload was successful. Previously, the
> > > > server
> > > > > responded with "OK" indicating that it had accepted the upload. I
> > > > > monitored my upload today and found it responding with "Data Logged
> > > > and
> > > > > posted in METAR mirror". I have added this new result code in the
> > > > > software and it will be in the next release, probably when we figure
> > > > out
> > > > > what is going on with your station. Even with the failure to spot the
> > > > > new result code, my station has been uploading to PWSWeather
> > > > > un-interrupted.
> > > > > > > > > >
> > > > > > > > > > To attempt to debug your poblem, what you need to do is go
> > > > to
> > > > > the Log screen, un-check "Only Errors", un-check all check boxes other
> > > > > servers and services except PWSWeather. Do not check "Show Console
> > > > Com.
> > > > > Errors" as this will clutter the log.
> > > > > > > > > >
> > > > > > > > > > Next, wait a few minutes until the next upload to PWSWeather
> > > > > happens. You should see a couple new entries in the log, what was sent
> > > > > to the PWSWeather server and the servers response. Select those lines
> > > > in
> > > > > the log then hit the Copy Selected button to copy these entries to
> > > > your
> > > > > Windows clipboard. Next, post a message here with those entries.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf"
> > > > <wolf9sbu@>
> > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > PWS is NOT getting the data. The connection times out.
> > > > Their
> > > > > display page of my data shows old data, however, occasonly data gets
> > > > > through
> > > > > > > > > > > and shows. Then their display page reverts back to the
> > > > same
> > > > > old data set.
> > > > > > > > > > > I have reviewed firewall and router.
> > > > > > > > > > >
> > > > > > > > > > > --- In wuhu_software_group@yahoogroups.com,
> > > > "wuhu_software"
> > > > > <wuhu_software@> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > One user reported the following was a router problem.
> > > > > Apparently PWS weather uses multiple servers, and the one you send to
> > > > > might not be the one that responds. If the router is does not allow
> > > > > this, the program will not see the response from their server.
> > > > > > > > > > > >
> > > > > > > > > > > > ---
> > > > > > > > > > > >
> > > > > > > > > > > > Found It!!!
> > > > > > > > > > > >
> > > > > > > > > > > > Yes, the router had updated firmware and change two
> > > > > settings on the router. UDP and TCP endpoint filtering was set to
> > > > > address restricted instead of endpoint independent. What this does is
> > > > > not allow communications if the return (ack) is from a different
> > > > address
> > > > > than the sendto address. This is why I could get the data to PWS but
> > > > it
> > > > > could not ACK my packets.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf"
> > > > > <wolf9sbu@> wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > I have been running WUHU for a long time with no
> > > > > trouble.
> > > > > > > > > > > > > Recently, PWS and Hamweather reports have been "stuck"
> > > > > on an older set of data. I contacted PWS and they claimed the issue
> > > > was
> > > > > on my end.
> > > > > > > > > > > > > I updated to the latest version of WUHU and now all
> > > > > reports go through EXCEPT PWS. the following errors repeat in the log:
> > > > > > > > > > > > > Sat Nov 20 10:20:10 2010 > PWSWeather Live Upload:
> > > > Final
> > > > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > > 0x00002ee2
> > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > > > > > Sat Nov 20 10:20:44 2010 > PWSWeather Background
> > > > Upload:
> > > > > Final Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > > > 0x00002ee2 (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Any feedback?
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Got fiddler running but it's not catching traffic.
Not even when I shut down and restart Firefox

--- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@...>
wrote:
>
>
> By the way, here is an alternative freeware that will capture http://
> traffic for future reference:
> Fiddler2 <http://www.fiddler2.com/fiddler2/>
> What is Fiddler?
> Fiddler is a Web Debugging Proxy which logs all HTTP(S) traffic between
> your computer and the Internet. Fiddler allows you to inspect all
> HTTP(S) traffic, set breakpoints, and "fiddle" with incoming or outgoing
> data. Fiddler includes a powerful event-based scripting subsystem, and
> can be extended using any .NET language.
>
> Fiddler is freeware and can debug traffic from virtually any
> application, including Internet Explorer, Mozilla Firefox, Opera, and
> thousands more.
>
>
>
>
> --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> <wuhu_software@> wrote:
> >
> >
> > No problem.
> >
> > I did install that effetech software and did not see a problem.
> >
> > Are they questionable because of spyware or something?
> >
> > I did not notice anything.
> >
> > Thanks.
> >
> >
> > --- In wuhu_software_group@yahoogroups.com, "Wolf" wolf9sbu@ wrote:
> > >
> > > According to "Web of Trust" plugin for Firefox, (www.mywot.com/)
> http://www.effetech.com/download/ "has a poor reputation."
> > > So... I'm not going there and recommending folks to go there isn't
> cool.
> > > Thanks for all your effort however,
> > > I'm all done with this on my end. As was mentioned by a few early in
> this string, they just shut of PWS upload and didn't be bothered.
> > > I joined the forum to try to fix it and I've jumped through enough
> hoops. Every thing else I do on the Internet works including FTP. web
> sites, forums, email... is working along with WUHU uploads to everything
> EXCEPT PWS. Comodo doesn't stop anything else I want to do. I imagine
> there are quit a few who just shut it off and never bothered joining the
> forum to figure it out so you won't get "Ya I had that problem" from
> many of the folks that did cause their not here. I don't check Yahoo
> often unless there is something of interest to me. I'm done being
> interested in this issue and I'll just uncheck PWS from logging and
> remove all references from my web pages. When an occasional post goes
> through to them as it does now, that's all fine for whoever is
> interested.
> > > Since everything else is working so smoothly, at this point, in my
> humble opinion, it's a PWS issue that they can figure out.
> > > Again, thanks for your efforts and I will continue to provide data
> to all who are willing to receive it without me jumping through hoops to
> get it to them.
> > > Happy Days
> > >
> > >
> > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> <wuhu_software@> wrote:
> > > >
> > > >
> > > > Here is something else we might try:
> > > > Download and install the following:
> > > > EffeTech HTTP Sniffer v4.1 <http://www.effetech.com/download/>
> > > > During the install, make sure you read the instructions and answer
> Yes
> > > > to install the WinPCAP, that is a low-level network driver than
> can
> > > > intercept network packets.
> > > > After install, under the programs Sniff menu, press Start.
> > > > This will capture all http:// traffic on the machine.
> > > > After you capture your attempted upload to PWSWeather, copy and
> paste
> > > > the header and the response to the request (if any).
> > > >
> > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> > > > <wuhu_software@> wrote:
> > > > >
> > > > >
> > > > > It is interesting that you have a 192.168.0.X address. Can you
> chance
> > > > > that to a 192.168.1.X address?
> > > > > I am also concerned about the Comodo firewall being used. You
> might
> > > > try
> > > > > removing it completely to see if that makes a difference.
> > > > > Finally, I found this note in a tips and tricks for XP. It might
> not
> > > > > hurt to check these settings. I am using the InternetOpenURL()
> so this
> > > > > may or may not be an issue for you.
> > > > > ---
> > > > > 232. Increasing number of connections per http server Folks,
> HTTP
> > > > > Protocol limits number of maximum connections to a HTTP server
> to 2.
> > > > > Following table explains restrictions placed by various HTTP
> > > > PROTOCOLS.
> > > > > This is the as per the RFC specifications.
> > > > > 1. HTTP 1.0 conforming server 4 simultaneous connections 2. HTTP
> 1.1
> > > > > conforming server 2 simputaneous connections Limitation caused
> by this
> > > > > is visible whenever your applications make calls like
> HttpSendRequest
> > > > > and InternetOpenURL which take longer to complete as they wait
> for
> > > > > previous connections to be freed up before their requests are
> sent.
> > > > > You can configure WinInet to exceed this limit by creating and
> setting
> > > > > the registry entries. Open registry (by going to START-RUN and
> > > > entering
> > > > > regedit) and navigate to:
> > > > >
> > > > >
> > > >
> [HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Intern\
> \
> > > > \
> > > > > et Settings]
> > > > > and look for values of "MaxConnectionsPerServer" and
> > > > > "MaxConnectionsPer1_0Server ".
> > > > > If you don't see then add two key by the names
> > > > "MaxConnectionsPerServer"
> > > > > and "MaxConnectionsPer1_0Server " respectively. Default values
> are as
> > > > > MaxConnectionsPerServer = 2 MaxConnectionsPer1_0Server = 4
> Changes its
> > > > > value to a number you want.
> > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf" wolf9sbu@
> wrote:
> > > > > >
> > > > > > Different machine, no firewall, no router.
> > > > > > Also see ping, tracert (2) and path ping below.
> > > > > >
> > > > > > Fri Dec 03 11:46:59 2010 > PWSWeather Live Upload: Final Fatal
> Eror
> > > > > (No more retries) InternetOpenUrl() returned error 0x00002ee2
> (12002),
> > > > > ERROR_INTERNET_TIMEOUT.
> > > > > > Fri Dec 03 11:47:50 2010 > PWSWeather Background Upload: Final
> Fatal
> > > > > Eror (No more retries) InternetOpenUrl() returned error
> 0x00002ee2
> > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > Fri Dec 03 11:47:50 2010 > PWSWeather Background Upload:
> Sending
> > > > >
> > > >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> > > > \
> > > > >
> > > >
> ******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> \
> > > > \
> > > > >
> > > >
> ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> \
> > > > \
> > > > >
> > > >
> 13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> \
> > > > \
> > > > > aw
> > > > > > Fri Dec 03 11:49:21 2010 > PWSWeather Background Upload: Final
> Fatal
> > > > > Eror (No more retries) InternetOpenUrl() returned error
> 0x00002ee2
> > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > Fri Dec 03 11:49:21 2010 > PWSWeather Background Upload:
> Sending
> > > > >
> > > >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> > > > \
> > > > >
> > > >
> ******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> \
> > > > \
> > > > >
> > > >
> ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> \
> > > > \
> > > > >
> > > >
> 13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> \
> > > > \
> > > > > aw
> > > > > > Fri Dec 03 11:50:52 2010 > PWSWeather Background Upload: Final
> Fatal
> > > > > Eror (No more retries) InternetOpenUrl() returned error
> 0x00002ee2
> > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > Fri Dec 03 11:50:52 2010 > PWSWeather Background Upload:
> Sending
> > > > >
> > > >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> > > > \
> > > > >
> > > >
> ******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> \
> > > > \
> > > > >
> > > >
> ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> \
> > > > \
> > > > >
> > > >
> 13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> \
> > > > \
> > > > > aw
> > > > > >
> > > > > > Pinging pwsweather.com [72.51.35.225] with 32 bytes of data:
> Reply
> > > > > from 72.51.35.225: bytes=32 time=223ms TTL=44 Reply from
> 72.51.35.225:
> > > > > bytes=32 time=202ms TTL=44 Reply from 72.51.35.225: bytes=32
> > > > time=195ms
> > > > > TTL=44 Reply from 72.51.35.225: bytes=32 time=210ms TTL=44  Ping
> > > > > statistics for 72.51.35.225:     Packets: Sent = 4, Received =
> 4, Lost
> > > > =
> > > > > 0 (0% loss), Approximate round trip times in milli-seconds:
> > > > Minimum
> > > > > = 195ms, Maximum = 223ms, Average = 207ms
> > > > > >
> > > > > > Tracing route to pwsweather.com [72.51.35.225] over a maximum
> of 30
> > > > > hops:    1    <1 ms    <1 ms    <1 ms  bossman.mshome.net
> > > > [192.168.0.1]
> > > > > 2   108 ms    93 ms    90 ms  10.119.160.1    3   503 ms   468
> ms
> > > > 377
> > > > > ms  166.181.126.81    4   527 ms   454 ms   461 ms
> 166.181.126.92
> > > > 5
> > > > > 528 ms   159 ms   100 ms  166.181.113.1    6   387 ms   387 ms
> 389
> > > > ms
> > > > > 198.8.15.242    7   309 ms   319 ms   346 ms  198.8.15.252    8
> *
> > > > > *        *     Request timed out.   9     *        *        *
> > > > > Request timed out.  10     *        *        *     Request timed
> out.
> > > > > 11     *        *        *     Request timed out.  12     *
> *
> > > > > *     Request timed out.  13   356 ms   355 ms   327 ms
> 198.8.15.1
> > > > 14
> > > > > 161 ms   159 ms   139 ms  so-5-0-0.edge2.Atlanta2.Level3.net
> > > > > [4.71.194.17]   15   291 ms   209 ms   261 ms
> > > > > ae-63-51.ebr3.Atlanta2.Level3.net [4.68.103.30]   16   400 ms
> 386 ms
> > > > > 360 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]   17   206
> ms
> > > > 197
> > > > > ms   198 ms  ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]
> 18
> > > > 229
> > > > > ms   433 ms   518 ms  ae-34-80.car4.LosAngeles1.Level3.net
> > > > > [4.69.144.134]   19     *        *        *     Request timed
> out.  20
> > > > > 242 ms   194 ms   204 ms  oc48-po4-0.la-sb600w-dis-2.peer1.net
> > > > > [216.187.88.150]   21   433 ms   506 ms   198 ms
> pws0.pwsweather.com
> > > > > [72.51.35.225]   Trace complete.
> > > > > >
> > > > > > 2nd trace:
> > > > > > Tracing route to pwsweather.com [72.51.35.225] over a maximum
> of 30
> > > > > hops:    1    <1 ms    <1 ms    <1 ms  bossman.mshome.net
> > > > [192.168.0.1]
> > > > > 2   106 ms    95 ms   110 ms  10.119.160.1    3   102 ms   112
> ms
> > > > 112
> > > > > ms  166.181.126.81    4   189 ms    98 ms    93 ms
> 166.181.126.92
> > > > 5
> > > > > 94 ms    92 ms    93 ms  166.181.113.1    6   112 ms   112 ms
> 94 ms
> > > > > 198.8.15.242    7   139 ms   159 ms   136 ms  198.8.15.252    8
> *
> > > > > *        *     Request timed out.   9     *        *        *
> > > > > Request timed out.  10     *        *        *     Request timed
> out.
> > > > > 11     *        *        *     Request timed out.  12     *
> *
> > > > > *     Request timed out.  13   147 ms   133 ms   132 ms
> 198.8.15.1
> > > > 14
> > > > > 157 ms   139 ms   141 ms  so-5-0-0.edge2.Atlanta2.Level3.net
> > > > > [4.71.194.17]   15   180 ms   140 ms   147 ms
> > > > > ae-73-52.ebr3.Atlanta2.Level3.net [4.68.103.62]   16   175 ms
> 199 ms
> > > > > 194 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]   17   225
> ms
> > > > 218
> > > > > ms   195 ms  ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]
> 18
> > > > 389
> > > > > ms   223 ms   220 ms  ae-34-80.car4.LosAngeles1.Level3.net
> > > > > [4.69.144.134]   19     *        *        *     Request timed
> out.  20
> > > > > 232 ms   197 ms   202 ms  oc48-po4-0.la-sb600w-dis-2.peer1.net
> > > > > [216.187.88.150]   21   221 ms   216 ms   217 ms
> pws0.pwsweather.com
> > > > > [72.51.35.225]   Trace complete.
> > > > > >
> > > > > > The first time out series is between U.S. Cellular IP's
> > > > > > second time out is between Level3.net and peer1.net
> > > > > >
> > > > > > Path ping
> > > > > > Tracing route to pwsweather.com [72.51.35.225] over a maximum
> of 30
> > > > > hops:
> > > > > > 0  weatherwatcher.mshome.net [192.168.0.119]
> > > > > > 1  bossman.mshome.net [192.168.0.1]
> > > > > > 2  10.119.160.1
> > > > > > 3  166.181.126.81
> > > > > > 4  166.181.126.92
> > > > > > 5  166.181.113.1
> > > > > > 6  198.8.15.242
> > > > > > 7  198.8.15.252
> > > > > > 8     *        *        *
> > > > > > Computing statistics for 200 seconds...
> > > > > >   Source to Here     This Node/Link
> > > > > > Hop  RTT    ` Lost/Sent = Pct    Lost/Sent = Pct   Address
> > > > > >  0
> > > > > weatherwatcher.mshome.net [192.168.0.119]
> > > > > 0/ 100 =  0%
> > > > > > 1    0ms      0/ 100 =  0%        0/ 100 =  0%
> bossman.mshome.net
> > > > > [192.168.0.1]                                        0/ 100 =
> 0%
> > > > > > 2  ---       100/ 100 =100%     100/ 100 =100%   10.119.160.1
> > > > > >       0/ 100 =  0%
> > > > > > 3  ---       100/ 100 =100%     100/ 100 =100%
> 166.181.126.81
> > > > > >        0/ 100 =  0%
> > > > > > 4  ---       100/ 100 =100%     100/ 100 =100%
> 166.181.126.92
> > > > > >       0/ 100 =  0%
> > > > > > 5  192ms      0/ 100 =  0%        0/ 100 =  0%
> 166.181.113.1
> > > > > >       0/ 100 =  0%
> > > > > > 6  221ms      0/ 100 =  0%        0/ 100 =  0%    198.8.15.242
> > > > > >       100/ 100 =100%
> > > > > > 7  ---       100/ 100 =100%       0/ 100 =  0%    198.8.15.252
> > > > > >       0/ 100 =  0%
> > > > > > 8  ---       100/ 100 =100%       0/ 100 =  0%
> weatherwatcher
> > > > > [0.0.0.0]
> > > > > > Trace complete.
> > > > > >
> > > > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> > > > > wuhu_software@ wrote:
> > > > > > >
> > > > > > >
> > > > > > > Do you have a 2nd machine that you could connect the station
> to? I
> > > > > would like to isolate whether it is that particular computer.
> > > > > > >
> > > > > > > I am not seeing anyone else that is having this issue so
> perhaps
> > > > > some strange firewall setting is stopping the response.
> > > > > > >
> > > > > > >
> > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf"
> <wolf9sbu@>
> > > > > wrote:
> > > > > > > >
> > > > > > > > Installed latest release posted here (152) and getting
> same
> > > > thing.
> > > > > > > >
> > > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf"
> <wolf9sbu@>
> > > > > wrote:
> > > > > > > > >
> > > > > > > > > Sorry such a delay in getting back.
> > > > > > > > > This is from this morning:
> > > > > > > > >
> > > > > > > > > Fri Dec 03 07:26:26 2010 > PWSWeather Background Upload:
> Final
> > > > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > > 0x00002ee2
> > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > Fri Dec 03 07:26:27 2010 > PWSWeather Background Upload:
> > > > Sending
> > > > >
> > > >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> > > > \
> > > > >
> > > >
> ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> \
> > > > \
> > > > >
> > > >
> gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> \
> > > > \
> > > > >
> > > >
> =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> \
> > > > \
> > > > > raw
> > > > > > > > > Fri Dec 03 07:27:02 2010 > PWSWeather Live Upload:
> Sending
> > > > >
> > > >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> > > > \
> > > > >
> > > >
> ******&dateutc=2010-12-03+13%3A26%3A16&winddir=292&windspeedmph=3.5&wind\
> \
> > > > \
> > > > >
> > > >
> gustmph=4.3&tempf=21.7&rainin=0.00&dailyrainin=0.00&baromin=30.27&dewptf\
> \
> > > > \
> > > > >
> > > >
> =13.8&humidity=71&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> \
> > > > \
> > > > > raw
> > > > > > > > > Fri Dec 03 07:28:00 2010 > PWSWeather Background Upload:
> Final
> > > > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > > 0x00002ee2
> > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > Fri Dec 03 07:28:01 2010 > PWSWeather Background Upload:
> > > > Sending
> > > > >
> > > >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> > > > \
> > > > >
> > > >
> ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> \
> > > > \
> > > > >
> > > >
> gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> \
> > > > \
> > > > >
> > > >
> =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> \
> > > > \
> > > > > raw
> > > > > > > > > Fri Dec 03 07:28:34 2010 > PWSWeather Live Upload: Final
> Fatal
> > > > > Eror (No more retries) InternetOpenUrl() returned error
> 0x00002ee2
> > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > Fri Dec 03 07:29:32 2010 > PWSWeather Background Upload:
> Final
> > > > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > > 0x00002ee2
> > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > Fri Dec 03 07:29:33 2010 > PWSWeather Background Upload:
> > > > Sending
> > > > >
> > > >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> > > > \
> > > > >
> > > >
> ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> \
> > > > \
> > > > >
> > > >
> gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> \
> > > > \
> > > > >
> > > >
> =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> \
> > > > \
> > > > > raw
> > > > > > > > > Fri Dec 03 07:31:04 2010 > PWSWeather Background Upload:
> Final
> > > > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > > 0x00002ee2
> > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > Fri Dec 03 07:31:05 2010 > PWSWeather Background Upload:
> > > > Sending
> > > > >
> > > >
> URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> \
> > > > \
> > > > >
> > > >
> ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> \
> > > > \
> > > > >
> > > >
> gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> \
> > > > \
> > > > >
> > > >
> =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> \
> > > > \
> > > > > raw
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --- In wuhu_software_group@yahoogroups.com,
> "wuhu_software"
> > > > > <wuhu_software@> wrote:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Lets see if we can isolate the problem with your
> uploads.
> > > > > > > > > >
> > > > > > > > > > I did find an issue with their server returning a new
> return
> > > > > string indicating that the upload was successful. Previously,
> the
> > > > server
> > > > > responded with "OK" indicating that it had accepted the upload.
> I
> > > > > monitored my upload today and found it responding with "Data
> Logged
> > > > and
> > > > > posted in METAR mirror". I have added this new result code in
> the
> > > > > software and it will be in the next release, probably when we
> figure
> > > > out
> > > > > what is going on with your station. Even with the failure to
> spot the
> > > > > new result code, my station has been uploading to PWSWeather
> > > > > un-interrupted.
> > > > > > > > > >
> > > > > > > > > > To attempt to debug your poblem, what you need to do
> is go
> > > > to
> > > > > the Log screen, un-check "Only Errors", un-check all check boxes
> other
> > > > > servers and services except PWSWeather. Do not check "Show
> Console
> > > > Com.
> > > > > Errors" as this will clutter the log.
> > > > > > > > > >
> > > > > > > > > > Next, wait a few minutes until the next upload to
> PWSWeather
> > > > > happens. You should see a couple new entries in the log, what
> was sent
> > > > > to the PWSWeather server and the servers response. Select those
> lines
> > > > in
> > > > > the log then hit the Copy Selected button to copy these entries
> to
> > > > your
> > > > > Windows clipboard. Next, post a message here with those entries.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf"
> > > > <wolf9sbu@>
> > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > PWS is NOT getting the data. The connection times
> out.
> > > > Their
> > > > > display page of my data shows old data, however, occasonly data
> gets
> > > > > through
> > > > > > > > > > > and shows. Then their display page reverts back to
> the
> > > > same
> > > > > old data set.
> > > > > > > > > > > I have reviewed firewall and router.
> > > > > > > > > > >
> > > > > > > > > > > --- In wuhu_software_group@yahoogroups.com,
> > > > "wuhu_software"
> > > > > <wuhu_software@> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > One user reported the following was a router
> problem.
> > > > > Apparently PWS weather uses multiple servers, and the one you
> send to
> > > > > might not be the one that responds. If the router is does not
> allow
> > > > > this, the program will not see the response from their server.
> > > > > > > > > > > >
> > > > > > > > > > > > ---
> > > > > > > > > > > >
> > > > > > > > > > > > Found It!!!
> > > > > > > > > > > >
> > > > > > > > > > > > Yes, the router had updated firmware and change
> two
> > > > > settings on the router. UDP and TCP endpoint filtering was set
> to
> > > > > address restricted instead of endpoint independent. What this
> does is
> > > > > not allow communications if the return (ack) is from a different
> > > > address
> > > > > than the sendto address. This is why I could get the data to PWS
> but
> > > > it
> > > > > could not ACK my packets.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf"
> > > > > <wolf9sbu@> wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > I have been running WUHU for a long time with no
> > > > > trouble.
> > > > > > > > > > > > > Recently, PWS and Hamweather reports have been
> "stuck"
> > > > > on an older set of data. I contacted PWS and they claimed the
> issue
> > > > was
> > > > > on my end.
> > > > > > > > > > > > > I updated to the latest version of WUHU and now
> all
> > > > > reports go through EXCEPT PWS. the following errors repeat in
> the log:
> > > > > > > > > > > > > Sat Nov 20 10:20:10 2010 > PWSWeather Live
> Upload:
> > > > Final
> > > > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > > 0x00002ee2
> > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > > > > > Sat Nov 20 10:20:44 2010 > PWSWeather Background
> > > > Upload:
> > > > > Final Fatal Eror (No more retries) InternetOpenUrl() returned
> error
> > > > > 0x00002ee2 (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Any feedback?
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Thats weird. Under the file menu does Capture Traffic have a check next to it?

After installing, it just started capturing.

I am running XP64.


--- In wuhu_software_group@yahoogroups.com, "Wolf" <wolf9sbu@...> wrote:
>
> Got fiddler running but it's not catching traffic.
> Not even when I shut down and restart Firefox
>
> --- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@>
wrote:
> >
> >
> > By the way, here is an alternative freeware that will capture http://
> > traffic for future reference:
> > Fiddler2 <http://www.fiddler2.com/fiddler2/>
> > What is Fiddler?
> > Fiddler is a Web Debugging Proxy which logs all HTTP(S) traffic between
> > your computer and the Internet. Fiddler allows you to inspect all
> > HTTP(S) traffic, set breakpoints, and "fiddle" with incoming or outgoing
> > data. Fiddler includes a powerful event-based scripting subsystem, and
> > can be extended using any .NET language.
> >
> > Fiddler is freeware and can debug traffic from virtually any
> > application, including Internet Explorer, Mozilla Firefox, Opera, and
> > thousands more.
> >
> >
> >
> >
> > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> > <wuhu_software@> wrote:
> > >
> > >
> > > No problem.
> > >
> > > I did install that effetech software and did not see a problem.
> > >
> > > Are they questionable because of spyware or something?
> > >
> > > I did not notice anything.
> > >
> > > Thanks.
> > >
> > >
> > > --- In wuhu_software_group@yahoogroups.com, "Wolf" wolf9sbu@ wrote:
> > > >
> > > > According to "Web of Trust" plugin for Firefox, (www.mywot.com/)
> > http://www.effetech.com/download/ "has a poor reputation."
> > > > So... I'm not going there and recommending folks to go there isn't
> > cool.
> > > > Thanks for all your effort however,
> > > > I'm all done with this on my end. As was mentioned by a few early in
> > this string, they just shut of PWS upload and didn't be bothered.
> > > > I joined the forum to try to fix it and I've jumped through enough
> > hoops. Every thing else I do on the Internet works including FTP. web
> > sites, forums, email... is working along with WUHU uploads to everything
> > EXCEPT PWS. Comodo doesn't stop anything else I want to do. I imagine
> > there are quit a few who just shut it off and never bothered joining the
> > forum to figure it out so you won't get "Ya I had that problem" from
> > many of the folks that did cause their not here. I don't check Yahoo
> > often unless there is something of interest to me. I'm done being
> > interested in this issue and I'll just uncheck PWS from logging and
> > remove all references from my web pages. When an occasional post goes
> > through to them as it does now, that's all fine for whoever is
> > interested.
> > > > Since everything else is working so smoothly, at this point, in my
> > humble opinion, it's a PWS issue that they can figure out.
> > > > Again, thanks for your efforts and I will continue to provide data
> > to all who are willing to receive it without me jumping through hoops to
> > get it to them.
> > > > Happy Days
> > > >
> > > >
> > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> > <wuhu_software@> wrote:
> > > > >
> > > > >
> > > > > Here is something else we might try:
> > > > > Download and install the following:
> > > > > EffeTech HTTP Sniffer v4.1 <http://www.effetech.com/download/>
> > > > > During the install, make sure you read the instructions and answer
> > Yes
> > > > > to install the WinPCAP, that is a low-level network driver than
> > can
> > > > > intercept network packets.
> > > > > After install, under the programs Sniff menu, press Start.
> > > > > This will capture all http:// traffic on the machine.
> > > > > After you capture your attempted upload to PWSWeather, copy and
> > paste
> > > > > the header and the response to the request (if any).
> > > > >
> > > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> > > > > <wuhu_software@> wrote:
> > > > > >
> > > > > >
> > > > > > It is interesting that you have a 192.168.0.X address. Can you
> > chance
> > > > > > that to a 192.168.1.X address?
> > > > > > I am also concerned about the Comodo firewall being used. You
> > might
> > > > > try
> > > > > > removing it completely to see if that makes a difference.
> > > > > > Finally, I found this note in a tips and tricks for XP. It might
> > not
> > > > > > hurt to check these settings. I am using the InternetOpenURL()
> > so this
> > > > > > may or may not be an issue for you.
> > > > > > ---
> > > > > > 232. Increasing number of connections per http server Folks,
> > HTTP
> > > > > > Protocol limits number of maximum connections to a HTTP server
> > to 2.
> > > > > > Following table explains restrictions placed by various HTTP
> > > > > PROTOCOLS.
> > > > > > This is the as per the RFC specifications.
> > > > > > 1. HTTP 1.0 conforming server 4 simultaneous connections 2. HTTP
> > 1.1
> > > > > > conforming server 2 simputaneous connections Limitation caused
> > by this
> > > > > > is visible whenever your applications make calls like
> > HttpSendRequest
> > > > > > and InternetOpenURL which take longer to complete as they wait
> > for
> > > > > > previous connections to be freed up before their requests are
> > sent.
> > > > > > You can configure WinInet to exceed this limit by creating and
> > setting
> > > > > > the registry entries. Open registry (by going to START-RUN and
> > > > > entering
> > > > > > regedit) and navigate to:
> > > > > >
> > > > > >
> > > > >
> > [HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Intern\
> > \
> > > > > \
> > > > > > et Settings]
> > > > > > and look for values of "MaxConnectionsPerServer" and
> > > > > > "MaxConnectionsPer1_0Server ".
> > > > > > If you don't see then add two key by the names
> > > > > "MaxConnectionsPerServer"
> > > > > > and "MaxConnectionsPer1_0Server " respectively. Default values
> > are as
> > > > > > MaxConnectionsPerServer = 2 MaxConnectionsPer1_0Server = 4
> > Changes its
> > > > > > value to a number you want.
> > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf" wolf9sbu@
> > wrote:
> > > > > > >
> > > > > > > Different machine, no firewall, no router.
> > > > > > > Also see ping, tracert (2) and path ping below.
> > > > > > >
> > > > > > > Fri Dec 03 11:46:59 2010 > PWSWeather Live Upload: Final Fatal
> > Eror
> > > > > > (No more retries) InternetOpenUrl() returned error 0x00002ee2
> > (12002),
> > > > > > ERROR_INTERNET_TIMEOUT.
> > > > > > > Fri Dec 03 11:47:50 2010 > PWSWeather Background Upload: Final
> > Fatal
> > > > > > Eror (No more retries) InternetOpenUrl() returned error
> > 0x00002ee2
> > > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > Fri Dec 03 11:47:50 2010 > PWSWeather Background Upload:
> > Sending
> > > > > >
> > > > >
> > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > \
> > > > > \
> > > > > >
> > > > >
> > ******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> > \
> > > > > \
> > > > > >
> > > > >
> > ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> > \
> > > > > \
> > > > > >
> > > > >
> > 13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> > \
> > > > > \
> > > > > > aw
> > > > > > > Fri Dec 03 11:49:21 2010 > PWSWeather Background Upload: Final
> > Fatal
> > > > > > Eror (No more retries) InternetOpenUrl() returned error
> > 0x00002ee2
> > > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > Fri Dec 03 11:49:21 2010 > PWSWeather Background Upload:
> > Sending
> > > > > >
> > > > >
> > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > \
> > > > > \
> > > > > >
> > > > >
> > ******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> > \
> > > > > \
> > > > > >
> > > > >
> > ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> > \
> > > > > \
> > > > > >
> > > > >
> > 13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> > \
> > > > > \
> > > > > > aw
> > > > > > > Fri Dec 03 11:50:52 2010 > PWSWeather Background Upload: Final
> > Fatal
> > > > > > Eror (No more retries) InternetOpenUrl() returned error
> > 0x00002ee2
> > > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > Fri Dec 03 11:50:52 2010 > PWSWeather Background Upload:
> > Sending
> > > > > >
> > > > >
> > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > \
> > > > > \
> > > > > >
> > > > >
> > ******&dateutc=2010-12-03+14%3A03%3A07&winddir=22&windspeedmph=2.5&windg\
> > \
> > > > > \
> > > > > >
> > > > >
> > ustmph=2.7&tempf=21.4&rainin=0.00&dailyrainin=0.00&baromin=29.41&dewptf=\
> > \
> > > > > \
> > > > > >
> > > > >
> > 13.1&humidity=70&weather=&clouds=&softwaretype=WUHU216VWC&action=updater\
> > \
> > > > > \
> > > > > > aw
> > > > > > >
> > > > > > > Pinging pwsweather.com [72.51.35.225] with 32 bytes of data:
> > Reply
> > > > > > from 72.51.35.225: bytes=32 time=223ms TTL=44 Reply from
> > 72.51.35.225:
> > > > > > bytes=32 time=202ms TTL=44 Reply from 72.51.35.225: bytes=32
> > > > > time=195ms
> > > > > > TTL=44 Reply from 72.51.35.225: bytes=32 time=210ms TTL=44  Ping
> > > > > > statistics for 72.51.35.225:     Packets: Sent = 4, Received =
> > 4, Lost
> > > > > =
> > > > > > 0 (0% loss), Approximate round trip times in milli-seconds:
> > > > > Minimum
> > > > > > = 195ms, Maximum = 223ms, Average = 207ms
> > > > > > >
> > > > > > > Tracing route to pwsweather.com [72.51.35.225] over a maximum
> > of 30
> > > > > > hops:    1    <1 ms    <1 ms    <1 ms  bossman.mshome.net
> > > > > [192.168.0.1]
> > > > > > 2   108 ms    93 ms    90 ms  10.119.160.1    3   503 ms   468
> > ms
> > > > > 377
> > > > > > ms  166.181.126.81    4   527 ms   454 ms   461 ms
> > 166.181.126.92
> > > > > 5
> > > > > > 528 ms   159 ms   100 ms  166.181.113.1    6   387 ms   387 ms
> > 389
> > > > > ms
> > > > > > 198.8.15.242    7   309 ms   319 ms   346 ms  198.8.15.252    8
> > *
> > > > > > *        *     Request timed out.   9     *        *        *
> > > > > > Request timed out.  10     *        *        *     Request timed
> > out.
> > > > > > 11     *        *        *     Request timed out.  12     *
> > *
> > > > > > *     Request timed out.  13   356 ms   355 ms   327 ms
> > 198.8.15.1
> > > > > 14
> > > > > > 161 ms   159 ms   139 ms  so-5-0-0.edge2.Atlanta2.Level3.net
> > > > > > [4.71.194.17]   15   291 ms   209 ms   261 ms
> > > > > > ae-63-51.ebr3.Atlanta2.Level3.net [4.68.103.30]   16   400 ms
> > 386 ms
> > > > > > 360 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]   17   206
> > ms
> > > > > 197
> > > > > > ms   198 ms  ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]
> > 18
> > > > > 229
> > > > > > ms   433 ms   518 ms  ae-34-80.car4.LosAngeles1.Level3.net
> > > > > > [4.69.144.134]   19     *        *        *     Request timed
> > out.  20
> > > > > > 242 ms   194 ms   204 ms  oc48-po4-0.la-sb600w-dis-2.peer1.net
> > > > > > [216.187.88.150]   21   433 ms   506 ms   198 ms
> > pws0.pwsweather.com
> > > > > > [72.51.35.225]   Trace complete.
> > > > > > >
> > > > > > > 2nd trace:
> > > > > > > Tracing route to pwsweather.com [72.51.35.225] over a maximum
> > of 30
> > > > > > hops:    1    <1 ms    <1 ms    <1 ms  bossman.mshome.net
> > > > > [192.168.0.1]
> > > > > > 2   106 ms    95 ms   110 ms  10.119.160.1    3   102 ms   112
> > ms
> > > > > 112
> > > > > > ms  166.181.126.81    4   189 ms    98 ms    93 ms
> > 166.181.126.92
> > > > > 5
> > > > > > 94 ms    92 ms    93 ms  166.181.113.1    6   112 ms   112 ms
> > 94 ms
> > > > > > 198.8.15.242    7   139 ms   159 ms   136 ms  198.8.15.252    8
> > *
> > > > > > *        *     Request timed out.   9     *        *        *
> > > > > > Request timed out.  10     *        *        *     Request timed
> > out.
> > > > > > 11     *        *        *     Request timed out.  12     *
> > *
> > > > > > *     Request timed out.  13   147 ms   133 ms   132 ms
> > 198.8.15.1
> > > > > 14
> > > > > > 157 ms   139 ms   141 ms  so-5-0-0.edge2.Atlanta2.Level3.net
> > > > > > [4.71.194.17]   15   180 ms   140 ms   147 ms
> > > > > > ae-73-52.ebr3.Atlanta2.Level3.net [4.68.103.62]   16   175 ms
> > 199 ms
> > > > > > 194 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]   17   225
> > ms
> > > > > 218
> > > > > > ms   195 ms  ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]
> > 18
> > > > > 389
> > > > > > ms   223 ms   220 ms  ae-34-80.car4.LosAngeles1.Level3.net
> > > > > > [4.69.144.134]   19     *        *        *     Request timed
> > out.  20
> > > > > > 232 ms   197 ms   202 ms  oc48-po4-0.la-sb600w-dis-2.peer1.net
> > > > > > [216.187.88.150]   21   221 ms   216 ms   217 ms
> > pws0.pwsweather.com
> > > > > > [72.51.35.225]   Trace complete.
> > > > > > >
> > > > > > > The first time out series is between U.S. Cellular IP's
> > > > > > > second time out is between Level3.net and peer1.net
> > > > > > >
> > > > > > > Path ping
> > > > > > > Tracing route to pwsweather.com [72.51.35.225] over a maximum
> > of 30
> > > > > > hops:
> > > > > > > 0  weatherwatcher.mshome.net [192.168.0.119]
> > > > > > > 1  bossman.mshome.net [192.168.0.1]
> > > > > > > 2  10.119.160.1
> > > > > > > 3  166.181.126.81
> > > > > > > 4  166.181.126.92
> > > > > > > 5  166.181.113.1
> > > > > > > 6  198.8.15.242
> > > > > > > 7  198.8.15.252
> > > > > > > 8     *        *        *
> > > > > > > Computing statistics for 200 seconds...
> > > > > > >   Source to Here     This Node/Link
> > > > > > > Hop  RTT    ` Lost/Sent = Pct    Lost/Sent = Pct   Address
> > > > > > >  0
> > > > > > weatherwatcher.mshome.net [192.168.0.119]
> > > > > > 0/ 100 =  0%
> > > > > > > 1    0ms      0/ 100 =  0%        0/ 100 =  0%
> > bossman.mshome.net
> > > > > > [192.168.0.1]                                        0/ 100 =
> > 0%
> > > > > > > 2  ---       100/ 100 =100%     100/ 100 =100%   10.119.160.1
> > > > > > >       0/ 100 =  0%
> > > > > > > 3  ---       100/ 100 =100%     100/ 100 =100%
> > 166.181.126.81
> > > > > > >        0/ 100 =  0%
> > > > > > > 4  ---       100/ 100 =100%     100/ 100 =100%
> > 166.181.126.92
> > > > > > >       0/ 100 =  0%
> > > > > > > 5  192ms      0/ 100 =  0%        0/ 100 =  0%
> > 166.181.113.1
> > > > > > >       0/ 100 =  0%
> > > > > > > 6  221ms      0/ 100 =  0%        0/ 100 =  0%    198.8.15.242
> > > > > > >       100/ 100 =100%
> > > > > > > 7  ---       100/ 100 =100%       0/ 100 =  0%    198.8.15.252
> > > > > > >       0/ 100 =  0%
> > > > > > > 8  ---       100/ 100 =100%       0/ 100 =  0%
> > weatherwatcher
> > > > > > [0.0.0.0]
> > > > > > > Trace complete.
> > > > > > >
> > > > > > > --- In wuhu_software_group@yahoogroups.com, "wuhu_software"
> > > > > > wuhu_software@ wrote:
> > > > > > > >
> > > > > > > >
> > > > > > > > Do you have a 2nd machine that you could connect the station
> > to? I
> > > > > > would like to isolate whether it is that particular computer.
> > > > > > > >
> > > > > > > > I am not seeing anyone else that is having this issue so
> > perhaps
> > > > > > some strange firewall setting is stopping the response.
> > > > > > > >
> > > > > > > >
> > > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf"
> > <wolf9sbu@>
> > > > > > wrote:
> > > > > > > > >
> > > > > > > > > Installed latest release posted here (152) and getting
> > same
> > > > > thing.
> > > > > > > > >
> > > > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf"
> > <wolf9sbu@>
> > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > Sorry such a delay in getting back.
> > > > > > > > > > This is from this morning:
> > > > > > > > > >
> > > > > > > > > > Fri Dec 03 07:26:26 2010 > PWSWeather Background Upload:
> > Final
> > > > > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > > > 0x00002ee2
> > > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > > Fri Dec 03 07:26:27 2010 > PWSWeather Background Upload:
> > > > > Sending
> > > > > >
> > > > >
> > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > \
> > > > > \
> > > > > >
> > > > >
> > ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> > \
> > > > > \
> > > > > >
> > > > >
> > gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> > \
> > > > > \
> > > > > >
> > > > >
> > =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> > \
> > > > > \
> > > > > > raw
> > > > > > > > > > Fri Dec 03 07:27:02 2010 > PWSWeather Live Upload:
> > Sending
> > > > > >
> > > > >
> > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > \
> > > > > \
> > > > > >
> > > > >
> > ******&dateutc=2010-12-03+13%3A26%3A16&winddir=292&windspeedmph=3.5&wind\
> > \
> > > > > \
> > > > > >
> > > > >
> > gustmph=4.3&tempf=21.7&rainin=0.00&dailyrainin=0.00&baromin=30.27&dewptf\
> > \
> > > > > \
> > > > > >
> > > > >
> > =13.8&humidity=71&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> > \
> > > > > \
> > > > > > raw
> > > > > > > > > > Fri Dec 03 07:28:00 2010 > PWSWeather Background Upload:
> > Final
> > > > > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > > > 0x00002ee2
> > > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > > Fri Dec 03 07:28:01 2010 > PWSWeather Background Upload:
> > > > > Sending
> > > > > >
> > > > >
> > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > \
> > > > > \
> > > > > >
> > > > >
> > ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> > \
> > > > > \
> > > > > >
> > > > >
> > gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> > \
> > > > > \
> > > > > >
> > > > >
> > =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> > \
> > > > > \
> > > > > > raw
> > > > > > > > > > Fri Dec 03 07:28:34 2010 > PWSWeather Live Upload: Final
> > Fatal
> > > > > > Eror (No more retries) InternetOpenUrl() returned error
> > 0x00002ee2
> > > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > > Fri Dec 03 07:29:32 2010 > PWSWeather Background Upload:
> > Final
> > > > > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > > > 0x00002ee2
> > > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > > Fri Dec 03 07:29:33 2010 > PWSWeather Background Upload:
> > > > > Sending
> > > > > >
> > > > >
> > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > \
> > > > > \
> > > > > >
> > > > >
> > ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> > \
> > > > > \
> > > > > >
> > > > >
> > gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> > \
> > > > > \
> > > > > >
> > > > >
> > =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> > \
> > > > > \
> > > > > > raw
> > > > > > > > > > Fri Dec 03 07:31:04 2010 > PWSWeather Background Upload:
> > Final
> > > > > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > > > 0x00002ee2
> > > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > > Fri Dec 03 07:31:05 2010 > PWSWeather Background Upload:
> > > > > Sending
> > > > > >
> > > > >
> > URL:http://www.pwsweather.com/pwsupdate/pwsupdate.php?ID=W9SBU&PASSWORD=\
> > \
> > > > > \
> > > > > >
> > > > >
> > ******&dateutc=2010-11-24+04%3A20%3A13&winddir=315&windspeedmph=1.6&wind\
> > \
> > > > > \
> > > > > >
> > > > >
> > gustmph=2.5&tempf=19.4&rainin=0.00&dailyrainin=0.00&baromin=30.36&dewptf\
> > \
> > > > > \
> > > > > >
> > > > >
> > =12.5&humidity=74&weather=&clouds=&softwaretype=WUHU216VWC&action=update\
> > \
> > > > > \
> > > > > > raw
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --- In wuhu_software_group@yahoogroups.com,
> > "wuhu_software"
> > > > > > <wuhu_software@> wrote:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Lets see if we can isolate the problem with your
> > uploads.
> > > > > > > > > > >
> > > > > > > > > > > I did find an issue with their server returning a new
> > return
> > > > > > string indicating that the upload was successful. Previously,
> > the
> > > > > server
> > > > > > responded with "OK" indicating that it had accepted the upload.
> > I
> > > > > > monitored my upload today and found it responding with "Data
> > Logged
> > > > > and
> > > > > > posted in METAR mirror". I have added this new result code in
> > the
> > > > > > software and it will be in the next release, probably when we
> > figure
> > > > > out
> > > > > > what is going on with your station. Even with the failure to
> > spot the
> > > > > > new result code, my station has been uploading to PWSWeather
> > > > > > un-interrupted.
> > > > > > > > > > >
> > > > > > > > > > > To attempt to debug your poblem, what you need to do
> > is go
> > > > > to
> > > > > > the Log screen, un-check "Only Errors", un-check all check boxes
> > other
> > > > > > servers and services except PWSWeather. Do not check "Show
> > Console
> > > > > Com.
> > > > > > Errors" as this will clutter the log.
> > > > > > > > > > >
> > > > > > > > > > > Next, wait a few minutes until the next upload to
> > PWSWeather
> > > > > > happens. You should see a couple new entries in the log, what
> > was sent
> > > > > > to the PWSWeather server and the servers response. Select those
> > lines
> > > > > in
> > > > > > the log then hit the Copy Selected button to copy these entries
> > to
> > > > > your
> > > > > > Windows clipboard. Next, post a message here with those entries.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf"
> > > > > <wolf9sbu@>
> > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > PWS is NOT getting the data. The connection times
> > out.
> > > > > Their
> > > > > > display page of my data shows old data, however, occasonly data
> > gets
> > > > > > through
> > > > > > > > > > > > and shows. Then their display page reverts back to
> > the
> > > > > same
> > > > > > old data set.
> > > > > > > > > > > > I have reviewed firewall and router.
> > > > > > > > > > > >
> > > > > > > > > > > > --- In wuhu_software_group@yahoogroups.com,
> > > > > "wuhu_software"
> > > > > > <wuhu_software@> wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > One user reported the following was a router
> > problem.
> > > > > > Apparently PWS weather uses multiple servers, and the one you
> > send to
> > > > > > might not be the one that responds. If the router is does not
> > allow
> > > > > > this, the program will not see the response from their server.
> > > > > > > > > > > > >
> > > > > > > > > > > > > ---
> > > > > > > > > > > > >
> > > > > > > > > > > > > Found It!!!
> > > > > > > > > > > > >
> > > > > > > > > > > > > Yes, the router had updated firmware and change
> > two
> > > > > > settings on the router. UDP and TCP endpoint filtering was set
> > to
> > > > > > address restricted instead of endpoint independent. What this
> > does is
> > > > > > not allow communications if the return (ack) is from a different
> > > > > address
> > > > > > than the sendto address. This is why I could get the data to PWS
> > but
> > > > > it
> > > > > > could not ACK my packets.
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > --- In wuhu_software_group@yahoogroups.com, "Wolf"
> > > > > > <wolf9sbu@> wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I have been running WUHU for a long time with no
> > > > > > trouble.
> > > > > > > > > > > > > > Recently, PWS and Hamweather reports have been
> > "stuck"
> > > > > > on an older set of data. I contacted PWS and they claimed the
> > issue
> > > > > was
> > > > > > on my end.
> > > > > > > > > > > > > > I updated to the latest version of WUHU and now
> > all
> > > > > > reports go through EXCEPT PWS. the following errors repeat in
> > the log:
> > > > > > > > > > > > > > Sat Nov 20 10:20:10 2010 > PWSWeather Live
> > Upload:
> > > > > Final
> > > > > > Fatal Eror (No more retries) InternetOpenUrl() returned error
> > > > > 0x00002ee2
> > > > > > (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > > > > > > Sat Nov 20 10:20:44 2010 > PWSWeather Background
> > > > > Upload:
> > > > > > Final Fatal Eror (No more retries) InternetOpenUrl() returned
> > error
> > > > > > 0x00002ee2 (12002), ERROR_INTERNET_TIMEOUT.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Any feedback?
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

----- Original Message -----

From: H. Smith

To: wuhu_software_group@yahoogroups.com

Sent: Tuesday, November 30, 2010 4:02 AM

Subject: Re: [wuhu_software_group] Re: B152 Release.

 

I do need to clean up on the webspace... Next release... Thanks. --- On Mon, 11/29/10, Don Lafferty <don@...> wrote: From: Don Lafferty <don@...> Subject: Re: [wuhu_software_group] Re: B152 Release. To: wuhu_software_group@yahoogroups.com Date: Monday, November 29, 2010, 8:53 PM   Excellent at usual Heath! Here's a question for you.  You always release the zip with the same name which makes it hard to determine what version it really is.  Have you thought about possibly putting the build into the name? Don On Mon, Nov 29, 2010 at 5:40 PM, wuhu_software <wuhu_software@...> wrote:   I forgot to mention, there appears to have been a bug in the software that was creating the yearly section of the WUHU Extremes.INI. Since this feature is not a year old yet, what you can do is copy all lines in the [Alltime Extremes] section and paste them over the lines in the [2010] section. Always use notepad to do this manually entry and always completely exit WUHU before doing so. Thanks. --- In wuhu_software_group@yahoogroups.com, "wuhu_software" <wuhu_software@...> wrote: > > > All, > > Here are the new features from the latest release. > > --- > > 105) Added support for Weekly extremes in the WUHU Extremes.INI file. > > 106) Added a method to retrieve values from the WUHU Extremes.INI file > for use in template processing. > > There are 3 different types of sections in this file: > > 1) All time extremes. This section is denoted by [AllTime Extremes] and > never changes. > > 2) Yearly extremes. This section is denoted by the Year number in > brackets like [2010] for example. > > 3) Weekly extremes. This section is denoted by the Year and the week > number in the form of [2010_week_48] where 2010 is the year and the week > is 48 out of a possible 53. > > Normally to use these variables, you would use a replacement string like > this: > > Yearly High Temperature: %[2010]Outdoor Temperature High% > > This works however as the year changes, you would need to recode the > [2010] to [2011]. > > To simplify the task, there are 6 new replacement strings that you can > use to simplify the template to automatically change based on the > current time of the year: > > %Year%, %Month%, %Week%", %LastYear%, %LastMonth%, LastWeek% > > So to code the above example to automatically change with the year, you > would write: > > Yearly High Temperature: %[%Year%]Outdoor Temperature High% > > Weekly sections require both the Year and the Week number. To do this, > you would code: > > Weekly High Temperature: %[%Year%_week_%Week%]Outdoor Temperature High% > > Note that you cannot really make use of the %LastMonth% until you have > accumulated a couple months of data in the extremes file. These sections > were not created in previous version; you will just have to wait to make > use of them. > > If someone was looking for a useful utility to code, you could scan > through the history files and create these sections automatically so > that they are available now based on your historical data. I doubt I > will have time to do so. > > More examples: > > Weekly High Temperature: %[%Year%_week_%Week%]Outdoor Temperature High% > @%[%Year%_week_%Week%]Outdoor Temperature High DateTime% > > Monthly High Temperature: %[%Year%_%Month%]Outdoor Temperature High% > @%[%Year%_%Month%]Outdoor Temperature High DateTime% > > Year High Temperature: %[%Year%]Outdoor Temperature High% > @%[%Year%]Outdoor Temperature High DateTime% > > AllTime High Temperature: %[AllTime Extremes]Outdoor Temperature High% > @%[AllTime Extremes]Outdoor Temperature High DateTime% > > 107) Added the ability to swap the vertical axis on the charts. To do > this, double click the chart, select the Swap Axis button. > > --- > > Software Download: > > WUHU216_32.zip > <http://home.comcast.net/~wuhu_software/files/WUHU216_32.zip> > -- The day Microsoft starts making vacuum cleaners is the day they start making something that doesn't suck.

I have been uploading to PWS since I started running WUHU.

I have had zero problems.  Never the first hint in the error log.  Info looks
solid there.  I hasn't even burped.

http://www.pwsweather.com/obs/DOMBY.html

Don't think it is the software.

I have a La Crosse 2812 U-IT weather station. WUHU does not recognize the
currdat.lst file & will not read the data.

Hear is a copy of the file. Can anyone tell me why this file is not working?


[header]
programm_name=HeavyWeather PRO WS 2800
programm_version=1.0
file_format_version=1.0

[time]
last_actualisation="3500448191"

[weather_picture]
comment=-1=not valid, 0=rain, 1=cloud, 2=sun
number=0

[weather_tendency]
comment1=-1=not valid, 0=no change of air pressure
comment2=1=air pressure rising,  2=air pressure falling
number=2

[storm_alarm]
comment=-1=not valid, 0=storm alarm not active, 1=storm alarm active
number=-1

[indoor_temperature]
deg_C="20.3"
deg_F="68.6"

[outdoor_temperature]
deg_C="2.8"
deg_F="37.1"

[indoor_humidity]
percent="50"

[outdoor_humidity]
percent="77"

[dewpoint]
deg_C="-0.8"
deg_F="30.5"

[windchill]
deg_C="2.8"
deg_F="37.1"

[wind_speed]
mps="0.0"
kmh="0.0"
mph="0.0"
knt="0.0"
bft="0"

[wind_direction]
deg="337.5"
name="NNW"

[rain_total]
mm="67.1"
inch="2.64"

[rain_24h]
mm="0.0"
inch="0.00"

[rain_1h]
mm="0.0"
inch="0.00"

[pressure_absolute]
hpa="---"
inHg="---"

[pressure_relative]
hpa="989.8"
inHg="29.23"