dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
18
share rss forum feed


mjf
" "
Premium,Mod
join:2000-08-05
New Orleans, LA
kudos:3
reply to pende_tim

Re: [bug] Line Monitor Dynamic IP Not Updating

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
Freedom is NOT Free
Premium
join:2004-06-24
The Boro
Reviews:
·Cingular Wireless
·Comcast Business..
·Vonage
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
kudos:1
Reviews:
·Comcast
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
" "
Premium,Mod
join:2000-08-05
New Orleans, LA
kudos:3
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
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
kudos:1
Reviews:
·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.

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
Freedom is NOT Free
Premium
join:2004-06-24
The Boro
Reviews:
·Cingular Wireless
·Comcast Business..
·Vonage
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
" "
Premium,Mod
join:2000-08-05
New Orleans, LA
kudos:3
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
" "
Premium,Mod
join:2000-08-05
New Orleans, LA
kudos:3
It does not work at all.

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

Thanks for your patience.