D-Link Forums

The Graveyard - Products No Longer Supported => DIR-655 => Routers / COVR => Europe DIR-655 => Topic started by: Moxide on May 26, 2014, 01:42:06 AM

Title: Problem with invalid username
Post by: Moxide on May 26, 2014, 01:42:06 AM
Hello  :),

I have a DIR-655, linked to a DSL-320B modem (in bridge mode). I'm facing intermittent connection loss, and I want to change the "Reconnect mode" (in the DIR-655, Internet setup PPPOE) from "On demand" to "Always on ", as I saw in a previous post.
But the router can't save settings and shows the message "Invalid username".

I think the issue comes from the fact that the ISP username contains a slash ("/") character. When I initially set up the router, I went through the quick setup process (using the CDROM), entered the PPPOE username and password, and everything was accepted. But from the web administration page, it seems there is a kind of "invalid character check".

I tried with different browsers, both IE and FF.

Router infos :
DIR-655 rev C1
firmware : 3.00
region : EUROPE/FRANCE

Is there a solution to this problem ?
Thanks in advance !
Title: Re: Problem with invalid username
Post by: FurryNutz on May 26, 2014, 04:42:10 PM
Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)

It maybe that special characters are not supported in the PPPoE user name section of this router. Generally there isn't any special characters in the user name for PPPoE accounts. I guess your ISP is one exception. Is there any chance you can contact your ISP and have them change the user name to something with out a special characters?

Where did you get this router from?
I don't see a Rev C listed for the EU region on the support page...
Title: Re: Problem with invalid username
Post by: Moxide on May 28, 2014, 12:17:44 AM
Hello,

My ISP is Orange, the biggest french ISP, and all its usernames begin with "fti/....".
Anyway, I managed to bypass the character check by using the Firefox javascript debugger. Several special characters are authorized "@", "-"..., but not the slash "/" :-(

I got the router from a well known french retailer (LDLC). Indeed, the rev C does not appear on the EU support page, but maybe because it's not updated yet...

Thanks for your suggestions !
Regards.
Title: Re: Problem with invalid username
Post by: FurryNutz on May 28, 2014, 06:44:33 AM
Looks like you found a work around.

I would recommend that you phone contact your regional D-Link support office and ask them about this. This is a new HW Rev router and they might be able to make some changes regarding it so you don't have to do a work around. Ask for level 2 or higher support.

I'll pass this along to my contact here and see if I get any info.

Thanks for sharing your info. Let us know if you gain any info.
Title: Re: Problem with invalid username
Post by: FurryNutz on May 29, 2014, 09:37:53 AM
I've asked my contact to pass this issue on to the EU team there and is all we can do from here.

Let us know if you find out anything.

Good Luck.
Title: Re: Problem with invalid username
Post by: mtztraktoros on June 10, 2014, 12:14:35 AM
Hi,
I will provide u a beta fw to solve this issue before 6/18, please be patient!
Title: Re: Problem with invalid username
Post by: mtztraktoros on June 12, 2014, 02:57:58 AM
Hi,
ftp://87.204.207.155/dir/dir-655/driver_software/ (ftp://87.204.207.155/dir/dir-655/driver_software/)
(dir655_C1_3.02B03Beta02)

Here will be the new fw in few hours, please test it. This is a beta version and released to solve the PPPoE user name problem with "/" slash.
Please give us a feedback about the result!

Thanks in advance!
 the link is: ftp://87.204.207.155/dir/dir-655/driver_software/DIR655C1_FW302B03Beta02(0612155358).rar (http://ftp://87.204.207.155/dir/dir-655/driver_software/DIR655C1_FW302B03Beta02(0612155358).rar)
Title: Re: Problem with invalid username
Post by: Moxide on June 13, 2014, 11:10:35 AM
Hello,

I'll test it as soon as possible !

thanks for the lightning fast fixing !  :o


Regards.
Title: Re: Problem with invalid username
Post by: FurryNutz on June 16, 2014, 09:07:39 AM
Thanks for the link and update. Please let us know if this fixes the problem.