site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
4477
Share Topic
Posting?
Post a:
Post a:
Links: ·Members Help Page ·Site FAQ ·Site bugs FAQ
page: 1 · 2 · 3
AuthorAll Replies


pende_tim
Premium
join:2004-01-04
Andover, NJ
Reviews:
·ProLog
·Verizon Online DSL
·voip.ms

[bug] Line Monitor Dynamic IP Not Updating

Don't know if anyone else has noticed this but I am not seeing dynamic IP address updates on my line monitoirs.

I am using DYNDNS to keep track of my IP address as I don't have static IPs. I noticed that since the "great unpleasant darkness" of a few weeks ago the dynamic IP is not updating when the IP changes. If I manually enter the IP address, it will track the ping times just fine.

I deleted the existing monitor and recreated it a few hours ago and the details are still not showing an new IP address.

Is this a bug or a feature that has not been enabled again yet?

Tim
--
The difference between genius and stupidity is that genius has its limits.


mjf
wish I was blue
Premium,Mod
join:2000-08-05
New Orleans, LA
kudos:2

I noticed it as well.



NetFixer
From my cold dead hands
Premium
join:2004-06-24
The Boro
Reviews:
·Comcast Business..
·Vonage
·Cingular Wireless
·Comcast

reply to pende_tim
I noticed it as well for my backup connection that does not have a static IP.

It seemed to be working for about a week after the line monitoring came back on-line, but that was because it had been automatically converted to a static IP moniter (using the last known IP address).

As soon as that connection had an IP address change, it stopped working. I reset it to use a DynDNS hostname, but it has been several days, and it still does not work.
--
We can never have enough of nature.
We need to witness our own limits transgressed, and some life pasturing freely where we never wander.


rpm15000

join:2005-06-01
Menlo Park, CA

reply to pende_tim
Broken here too. No line monitoring with Dynamic DNS.



JimThePCGuy
Formerly known as schja01.
Premium,MVM
join:2000-04-27
Morton Grove, IL

Ditto here too.
Might be a victim of the outage?



GeekJedi
RF is Good For You
Premium
join:2001-06-21
Mukwonago, WI

reply to pende_tim
I'm glad you posted this. I was hoping I wasn't the only one with the problem!!



mjf
wish I was blue
Premium,Mod
join:2000-08-05
New Orleans, LA
kudos:2

reply to pende_tim
DYNSITE has updated my dynamic IP address twice now. So it appears to be working now.



GeekJedi
RF is Good For You
Premium
join:2001-06-21
Mukwonago, WI

How long should it take for the monitor to start working on a dynamic IP? I tried mine again and got nothing.



NetFixer
From my cold dead hands
Premium
join:2004-06-24
The Boro
Reviews:
·Comcast Business..
·Vonage
·Cingular Wireless
·Comcast

reply to mjf

said by mjf:

DYNSITE has updated my dynamic IP address twice now. So it appears to be working now.

The built-in DDNS client in my Netopia router has never stopped working with the DynDNS service. The problem is that the DSLR monitors no longer seem to be able to work with a DynDNS hostname. I have reset it to stop using the "static IP" status that it got after the site restore, and several days later after it was obvious that did not work, I deleted that monitor and created a new one (which still does not work).

Here is proof that the DynDNS hostname is resolving and that it is pingable:

C:\>nslookup windcrest.dyndns-office.com
Server:  dcs-srv.dcs-net
Address:  192.168.9.2
 
Non-authoritative answer:
Name:    windcrest.dyndns-office.com
Address:  98.87.57.78
 
C:\>ping windcrest.dyndns-office.com
 
Pinging windcrest.dyndns-office.com [98.87.57.78] with 32 bytes of data:
 
Reply from 98.87.57.78: bytes=32 time=52ms TTL=238
Reply from 98.87.57.78: bytes=32 time=53ms TTL=238
Reply from 98.87.57.78: bytes=32 time=52ms TTL=238
Reply from 98.87.57.78: bytes=32 time=54ms TTL=238
 
Ping statistics for 98.87.57.78:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 52ms, Maximum = 54ms, Average = 52ms
 
 

About 30 minutes ago I manually entered the current IP address into the line monitor setup, and that works, but it would be a PITA to try to keep up with the frequent IP address changes on that particular (somewhat unstable) DSL circuit.

--
History does not long entrust the care of freedom to the weak or the timid.
-- Dwight D. Eisenhower


mjf
wish I was blue
Premium,Mod
join:2000-08-05
New Orleans, LA
kudos:2

reply to pende_tim
I know this may be obvious but have you updated your login password in your client setup - presuming that you changed it after the site crash.



NetFixer
From my cold dead hands
Premium
join:2004-06-24
The Boro
Reviews:
·Comcast Business..
·Vonage
·Cingular Wireless
·Comcast

said by mjf:

I know this may be obvious but have you updated your login password in your client setup - presuming that you changed it after the site crash.

Is this post (combined with your previous post saying that the DYNSITE client works) an unofficial way of telling us that we can now only use the DYNSITE client with the DSLR dynamic IP address line monitoring?
--
History does not long entrust the care of freedom to the weak or the timid.
-- Dwight D. Eisenhower


pende_tim
Premium
join:2004-01-04
Andover, NJ
Reviews:
·ProLog
·Verizon Online DSL
·voip.ms

reply to mjf

said by mjf:

I know this may be obvious but have you updated your login password in your client setup - presuming that you changed it after the site crash.

??? I did reset my password often the "event" a few weeks ago and am able to see all my history and IMs etc. is this what you are asking?

I almost feel it is a site bug that somehow showed up after the restore as a few others are also seeing it. If I manually put in the IP address, it tracks until the IP address changes so at least 50% of the process works. As NetFixer says , that is a workaround but also a PITA with a DSL circuit that changes every couple of days.
Tim
--
The difference between genius and stupidity is that genius has its limits.


mjf
wish I was blue
Premium,Mod
join:2000-08-05
New Orleans, LA
kudos:2
Host:
General Questions
Wireless Networking
Covad / covad.net
D-Link
South Central

DynSite is working for me. I haven't tested the other services.

I did have to update DynSite with my new password that I created to regain access to DSLR after the site crash event.

The other services that worked before should work now.



GeekJedi
RF is Good For You
Premium
join:2001-06-21
Mukwonago, WI
Reviews:
·RoadRunner Cable
·CenturyLink
·VOIPo

said by mjf:

DynSite is working for me. I haven't tested the other services.

I did have to update DynSite with my new password that I created to regain access to DSLR after the site crash event.

The other services that worked before should work now.

Actually, that doesn't mean the others should work. So far DynSite has worked, while DynDNS and ZoneEdit dynamic IP's are not working for me.
--
The goal of the broadcast engineer is to get all the meters on the transmitter to go as far to the right as possible!!


pende_tim
Premium
join:2004-01-04
Andover, NJ
Reviews:
·ProLog
·Verizon Online DSL
·voip.ms

reply to mjf

said by mjf:

DynSite is working for me. I haven't tested the other services.

I did have to update DynSite with my new password that I created to regain access to DSLR after the site crash event.

The other services that worked before should work now.

Unfortunately DynSite is not suitable for me. I do not leave a Windows PC connected 24x7 and none of my routers seem to support the DynSite service.

I did reset my login password a few hours ago, just in case that somehow was a problem.

Lets hope Justin can get DynDns going again but I am sure he has bigger issues to work on right now than this one subset of a free feature.
--
The difference between genius and stupidity is that genius has its limits.


NetFixer
From my cold dead hands
Premium
join:2004-06-24
The Boro
Reviews:
·Comcast Business..
·Vonage
·Cingular Wireless
·Comcast

reply to mjf

said by mjf:

DynSite is working for me. I haven't tested the other services.

I did have to update DynSite with my new password that I created to regain access to DSLR after the site crash event.

The other services that worked before should work now.

The problem is that yes, the other DDNS services should be working again, but they are not working.




In the line monitor graph shown above, the blank area to the left is the result of only using the DynDNS hostname (that hostname was properly assigned the correct IP address at the time). The crappy looking mess in the middle only appeared after I manually entered the IP address that was associated with the DynDNS hostname. The dropout was when the IP address changed (I manually had the router establish a new session both to see if I would get a better signal, and to see if the DSLR line monitor would detect the IP address change...I got a better signal, but the DSLR line monitor did not detect the IP address change). The cleaner signal to the right was when I once again had to manually enter the current IP address into the line monitor setup.

FWIW, the screen shot below shows how I have setup the DSLR line monitor for this particular circuit:




The area where the IP address is displayed used to be updated automatically when the line monitor would do a DNS lookup on the DynDNS hostname. Now however, I have to manually enter the current IP address, or the monitor does not work.

I have to use the DynDNS client that is built-in to this DSL router because it is located remotely in another building, and it has no PC's directly connected to it (so DYNSITE is not an option). It is strictly used as a WiFi hotspot (that I use only as a backup internet connection).
--
History does not long entrust the care of freedom to the weak or the timid.
-- Dwight D. Eisenhower


mjf
wish I was blue
Premium,Mod
join:2000-08-05
New Orleans, LA
kudos:2

I have set up my router using the built in DynDNS.

I have inserted my IP from this DNS as ccccc.dlinkddns.com (free host name from DLink) in the DSLR line monitor setup. I will check back to see if it is working.



mjf
wish I was blue
Premium,Mod
join:2000-08-05
New Orleans, LA
kudos:2

It does not work at all.

Let's see if I can get this on the priority list.

Thanks for your patience.



JimThePCGuy
Formerly known as schja01.
Premium,MVM
join:2000-04-27
Morton Grove, IL

reply to pende_tim
I am still having this issue.
It seems any existing dynamic monitors are working on whatever IP was in effect at the time of the system crash. Any IP updates are not being recognized. Also changing to static and plugging in a IP manually doesn't work either.
I ran this by a long time DSLR member lev See Profile who suggested I set the monitor to Dynamic then Static then back to Dynamic but that did nothing.
I'm willing to try anything to get this working again but so far nothing I've tried has worked.
J



lev
This site served its purpose
Premium,Ex-mod 2002-08
join:2001-05-30
Chicago, IL
kudos:2
Reviews:
·Comcast Business..

xz4gb8 See Profile told me that switching from dynamic to static to dynamic worked for him a few days ago; just last night he said it wasn't quite the case. I've invited him to post details of his experience here.


Friday, 24-May 02:17:29 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 13.5 years online © 1999-2013 dslreports.com.
Most commented news this week
Hot Topics