Peculiar Authentication Problem

  • Thread starter Thread starter Subbu
  • Start date Start date
  • Replies Replies 6
  • Views Views 6,919
Subbu

Subbu

Newbie
Messages
10
Location
NA
ISP
Tata Indicom
I have this weird problem.. This started from June 1st ~9:40pm.

Let me get to the basics:

[*]I live in Bangalore.
[*]I use Linksys WAG200G (but also have an UTStarcom UT300R2U for testing purposes).
[*]My DSL connectivity is fine, i.e. The DSL LED is stable and so are my SNR/Attenuation values (Details below)
[*]My Modem/Router is connected via RJ45 (LAN) cable and I use Windows 7 (Desktop)/Windows XP(Laptop)
[/list]
Here is the problem:
I'm not able to access internet on both Linksys/UTStarcom.. The DSL LED glows up, remains stable but the Internet LED doesn't come up after I give the correct Service Username/Password.

In fact, I've been in contact with my local exchange (which is very nearby) and they're trying to help too.. (Then 'engineer' termed it as a Peculiar Problem)

Things they've done:

[*]Reset Password (10 times?)
[*]Changed the Port (according to them, Thrice!)
[*]Removed Port-binding to test. (He was in my home when this was happening)
[*]Gave a new CPE for testing.
[/list]
But still I get this error when I use it with my given details.. (also, I get Error 691 if I try it in Bridge Mode):



Here is a screencap of the Diagnostics Page:



However, If I give the Username/Password which they gave for that Prepaid Promotional "StartUp" Plan, it works fine (!). i.e:

Username: xy@ppbb.bsnl.in
Password: password


That is, My Postpaid Username and Password is giving authentication error while the Pre-paid Account is working fine (No Authentication Failure/what-so-ever). Even the BSNL guys near my place are confused, they're trying their best but are unable to figure out what's wrong.. I mean, they reset the password and all!


Here is my ADSL stats in case it's helpful:



Also, proof that they reset the password 10 times (!):



I think it's the problem with NIB? (I'm in NIB-II BTW, I [used to] get IP addresses which start from 117).

Thanks in advance,
Subbu
 
OK. I've faced a similar problem with my BSNL line back in 2008. PPPOE authentication was working fine. One fine day, it stopped working. I complained. Those guys/babus at the exchange tried everything but still, it wasn't authenticating. They changed my password, line, port and just about everything they could. Finally, they gave up and as a last option they told me to forget PPPOE and try Bridged mode instead. Voila! It worked. So, apparently BSNL guys/babus had somehow managed to disable PPPOE authentication for my line. Since then, I started using Bridged mode. Finally, I surrendered my BSNL line sometime in 2009 and migrated to Airtel. Try Bridged mode and let me know whether it's working or not! 🙂
 
Hey Chaitanya! I've already tried Bridge Mode (using both my Linksys and UTStarcom), but both produce Error 691. :wall:


I've also noticed something strange from my Linksys's System Log (when using PPPoE in the Router).

Log snippet when given correct password:
Code: 
Mon, 2002-09-09 01:17:03 - Initialize LCP.Mon, 2002-09-09 01:17:03 - Plugin pppoe loaded.Mon, 2002-09-09 01:17:03 - PPPoE Plugin InitializedMon, 2002-09-09 01:17:03 - Plugin pppoe called.Mon, 2002-09-09 01:17:03 - pppd 2.4.1 started by root, uid 0Mon, 2002-09-09 01:17:03 - setting line discipline hookMon, 2002-09-09 01:17:03 - Sending PADIMon, 2002-09-09 01:17:03 - HOST_UNIQ successful matchMon, 2002-09-09 01:17:04 - Got connection: 1cdfMon, 2002-09-09 01:17:04 - Connecting PPPoE socket: 00:30:88:23:26:13 df1c nas0 0x1000d398Mon, 2002-09-09 01:17:04 - using channel 268Mon, 2002-09-09 01:17:04 - Using interface ppp0Mon, 2002-09-09 01:17:04 - Connect: ppp0  nas0Mon, 2002-09-09 01:17:04 - Couldn't increase MTU to 1500.Mon, 2002-09-09 01:17:04 - Couldn't increase MRU to 1500Mon, 2002-09-09 01:17:04 - LCP is allowed to come up.Mon, 2002-09-09 01:17:04 - Couldn't increase MRU to 1500[B][COLOR="red"]Mon, 2002-09-09 01:17:04 - Remote message: CHAP authentication failure, unit 1945Mon, 2002-09-09 01:17:04 - CHAP authentication failed[/COLOR][/B]Mon, 2002-09-09 01:17:04 - Couldn't increase MTU to 1500.Mon, 2002-09-09 01:17:04 - Couldn't increase MRU to 1500Mon, 2002-09-09 01:17:04 - LCP down.Mon, 2002-09-09 01:17:10 - This terminate is called from lcp_finished()Mon, 2002-09-09 01:17:10 - Connection terminated.Mon, 2002-09-09 01:17:10 - Doing disconnectMon, 2002-09-09 01:17:10 - Exit.
Log snippet when given WRONG password:
Code: 
Mon, 2002-09-09 01:19:14 - Initialize LCP.Mon, 2002-09-09 01:19:14 - Plugin pppoe loaded.Mon, 2002-09-09 01:19:14 - PPPoE Plugin InitializedMon, 2002-09-09 01:19:14 - Plugin pppoe called.Mon, 2002-09-09 01:19:14 - pppd 2.4.1 started by root, uid 0Mon, 2002-09-09 01:19:14 - setting line discipline hookMon, 2002-09-09 01:19:14 - Sending PADIMon, 2002-09-09 01:19:15 - HOST_UNIQ successful matchMon, 2002-09-09 01:19:15 - Got connection: 2821Mon, 2002-09-09 01:19:15 - Connecting PPPoE socket: 00:30:88:23:26:13 2128 nas0 0x1000d398Mon, 2002-09-09 01:19:15 - using channel 272Mon, 2002-09-09 01:19:15 - Using interface ppp0Mon, 2002-09-09 01:19:15 - Connect: ppp0  nas0Mon, 2002-09-09 01:19:15 - Couldn't increase MTU to 1500.Mon, 2002-09-09 01:19:15 - Couldn't increase MRU to 1500Mon, 2002-09-09 01:19:15 - LCP is allowed to come up.Mon, 2002-09-09 01:19:15 - Couldn't increase MRU to 1500[COLOR="red"][B]Mon, 2002-09-09 01:19:16 - Remote message: Invalid CHAP-PasswordMon, 2002-09-09 01:19:16 - CHAP authentication failed[/B][/COLOR]Mon, 2002-09-09 01:19:16 - Couldn't increase MTU to 1500.Mon, 2002-09-09 01:19:16 - Couldn't increase MRU to 1500Mon, 2002-09-09 01:19:16 - LCP down.Mon, 2002-09-09 01:19:16 - This terminate is called from lcp_finished()Mon, 2002-09-09 01:19:16 - Connection terminated.Mon, 2002-09-09 01:19:16 - Doing disconnectMon, 2002-09-09 01:19:16 - Exit.
See the highlighted parts? It says I've given a wrong password, but even with the correct one it fails to authenticate. -_-


Here is the packet capture log when trying in Bridge Mode (somewhat similar to above):
https://i.imgur.com/VqS2k.png


...If only Airtel was feasible in my area. 😢
 
Same Pinch to you - I too got the same problem on same day/time. Then I logged a complaint online (1502) and later took the Docket Number and informed the JTO next day morning. By 2nd June afternoon my connection was up and I could see 2Mbps speed on my UL-1350 plan. I am guessing that yours is also UL-1350.When your port/Network changes, then it may change your ID/Password. Two months back I changed my plan and didn't knew that it would involving moving my Port from P2 Network to MP Network.Even my User ID which was my name, got changed to "shXXXXXXXX" where X is the telephone number and default password is "password".Try taking your Modem/Laptop to BSNL Exchange and sit on their head to fix the problem. The JTO at Indiranagar (Bangalore) exchange is bit friendly and patience. Hope you get similar JTO for your exchange 🙂
 
I am guessing that yours is also Unlimited-1350.
Yesh! My plan is UL1350 too.

Username will change uh? Probably that's the reason why I'm not able authenticate myself. I'll give the Vijayanagar Exchange a visit first thing monday morning. -_-

(sadly, shXXXXXXXX didn't work for me.. are you sure it's only the 8-digit Phone Number and doesn't include area code? i.e. not sh80XXXXXXXX?)

Thanks!
 
Error 691. :wall:
Error 691? Then I'm 100% sure the problem is not at your end. As mentioned above, looks like your userid has changed. So, I suggest you contact your exchange and demand your (new?) userid. I also had the contact numbers of NIB (Bangalore) but misplaced them. Try getting their numbers and contact them directly. NIB people might be able to help you out.
 

w00t. Thanks for all the help. Been in contact with Local Exchange since morning, but they still couldn't solve the problem (they again reset the port and password today.. -_-)


Did a quick search on Google for JTO/NIB contacts in Bangalore and found this.

Made a call to 25808870 and the lady there listened to me patiently, put me on hold for a while, told me that there was something wrong and it is now corrected and to use the same UserID and Password.. It's working fine now ^_^
 

Top