snoopy78 schrieb:Hallo,
habe auch gerade festgestellt, dass die letzte Aktualisierung meines SX-541 (FW 2.11 SMC) am 07.06.07 war.
Vorher hat es mit DYNDNS.ORG einwandfrei funktioniert, vermute daher dass dyndns.org etwas verändert hat, da die FW 2.11 schon seit längerer Zeit stabil läuft.
UPDATE
ok..hab grad mal den SX541 rebootet und er meldet mir auch
"
06/12/2007 16:51:19 NTP Date/Time updated.
08/01/2003 00:00:22 DDNS> Operation complete, DDNS IP=xx.xx.128.57
08/01/2003 00:00:21 If(PPPoE1) PPP connection ok !
"
hab natürlich auch gleich bei DYNDNS.org nachgeschaut...und siehe da
"
IP in Database/DNS: xx.xx.176.54
Last Updated: June 07, 2007 6:19:04 AM
New IP Address: xx.xx.128.57
"
sieht also wirklich so aus, als ob dyndns.org uns SX541 User ausgesperrt hat
naja habe bei dyndns.org mal ne supportanfrage aufgemacht [DYNDNS #442286]
==================================
==================================
ok.. hier die BLITZANTWORT von dyndns.org
"
Thank you for contacting our customer support team.
> I'm currently using an Siemens SX541 with SMC 2.11 Firmware as
> my internet connection.
>
> Since several days I and several other Siemens device (SX 541,
> SE 555, SE 515) users experiencing the problem, that our device
> is registering successfully at your service.
>
> The Log of my last connection:
> "
> 06/12/2007 16:51:19 NTP Date/Time updated.
> 08/01/2003 00:00:22 DDNS> Operation complete, DDNS
> IP=xx.xx.128.57
> 08/01/2003 00:00:21 If(PPPoE1) PPP connection ok !
> "
>
> But at your Website i can see that the new IP isn't stored.
>
> "
> IP in Database/DNS: xx.xx.176.54
> Last Updated: June 07, 2007 6:19:04 AM
> New IP Address: xx.xx.128.57
> "
>
> Can you please tell me how we can get the Service working again.
We have not made any changes that should affect your router's ability to
update. If your router is unable to properly update your IP address it
means that its update client was created incorrectly. Our update
guidelines are displayed on our website so that anyone can create an
update client to work with our systems. If yours does not, it means that
they did not create it correctly. You will need to contact the
manufacturer for help. Here is the information on our update API:
http://www.dyndns.com/developers/specs/
"
====
danach ging noch folgende mail an den support raus (incl. deren antwort)
"
> if you PLEASE read my mail carefully you will realize that i'm using
> exactely this router & configuration for several months right now.
>
> Also the LOG shows that the router is updating successfully.
>
> PLEASE check out if there is not an bug or "small" glitch in your
> system.
I did carefully read your email and am acknowledging that it was working
for you for the past few months. As I stated in my email we have not
made any changes that should affect your router's ability to update if
it was designed with our specifications. If it is failing to update that
means that it was not designed correctly. We have made it easy for
developers to get the information necessary to create a compliant update
client. It sounds like they have failed to do so. You must contact them
for help as we did not design the update client that you are using.
--
"
=========
=========
ok.. anfrage an smc ging auch gerade raus
=======
hmmm.....komisch.. jetzt geht es wieder ?
"
IP in Database/DNS: xx.xx.148.141
Last Updated: June 12, 2007 4:38:10 PM
&
06/12/2007 21:38:10 DDNS> Operation complete, DDNS IP=xx.xx.148.141
"
Zuletzt bearbeitet:
