Thread: Unable To Connect to internet through UT Starcom WA3002G4!

Hello All,

I'm using UT Starcom WA3002G4 router with BSNL Home UL-750 plan!
My router is connected through LAN to my computer! I've tried everything!

Lineman checked all the lines & The BSNL officer also checked my modem throughmy port.. it is working fine!
I tried resetting it & then also checked the ping to 192.168.1.1...
Everything is right..

I've checked all the settings, VPI & VCI Values, tried bridging 0/32 in WAN option..
I've only connected my desktop to it.. But, It is not connecting!

Please Help!
Thanks!

Is the DSL light (yellow one) blinking ?

If it is blinks,then you are getting our internet but the modem was not configured properly.

Please let me know what u see here __>

login to your router htp://192.168.1.1

Go to Device Info -- >click on WAN -- > let me know what u see on the right side

it will be like

VPI/VCI Con. ID Category Service Interface Protocol Igmp QoS State Status IP Address

0/35 1 UBR pppoe_0_35_1 ppp_0_35_1 PPPoE Disabled Disabled Enabled Up 59.92.112.125

Copy and paste yours !!

its 0/35 for bsnl not 0/32

Lineman checked all the lines & The BSNL officer also checked my modem throughmy port.. it is working fine!

Now what exactly you are trying to do ?
see this link and check the settings.
http://chennai.bsnl.co.in/BBS/WA3002G4.htm

http://mydataone.net/dialer/wa3002g4.html

All setings are default!
I've resetted my modem several times!

It shows DSL Light STABLE... But When I try to connect it, it says..
Error:815
"The remote host server could not be established..."

I talked to the Exchange manager, He said Your phone line is getting earthed!
Lineman checked everything but... Nothings there!

I've tried pinging 192.168.1.1 -t & I'm getting reply from 192.168.1.1!

The line is clear, but It is not connecting!

DUNS ERROR 815

815 - Failed to connect.

Windows Vista Only - This error occurs only with Windows Vista. It "replaces" error codes 676, 678, 691 and 769 from Windows XP and earlier, and covers at least 4 different causes of failure to connect. This error can occur on attempts to make a DSL connection. The actual detailed reason for the failure to connect does not show up on the standard Vista error screen, but is available if you look hard enough and includes:

* Line is busy (for DSL the line isn't really busy, but the DSL server has a problem)
* Remote Computer did not respond (there is a connectivity error)
* Username or Password Error (the username and/or password specified for the DSL connection is incorrect or not recognized by the DSL server)
* Destination Host Unreachable (networking or network card error)

Presume your OS is vista
Check your network card.
Post ipconfig /all data

Originally Posted by essbebe

Presume your OS is vista
Check your network card.
Post ipconfig /all data

Yes.. My OS is Windows Vista Ultimate 32-bit!

are you meant to say post your network card preferences & all ipconfig data..?
Sorry.. I'm new here!

Sorry. I have Xp Pro Sp2.
Anyway
Start RUN type cmd
a new page will open
type ipconfig /all ( * note space after ipconfig )
Please post the results.

Para two :
Start Network Show all connections
Select LAN
Properties
A page called Network will appear.
On top your Network will be listed.
Click Configure
check enabled or not.

In same page
high light tcp/ip
properties
see DNS
enter
208.67.220.220
and 208.67.222.222
Apply Save.

Feedback.

Ok Thanks for the help essbebe!

I'm not on my PC. I'll try what you said & will give you feedback tomorrow!
Thanks Buddy!

Hoping it should get worked!

Hey essbebe, I've tried what you told... but it is not working!

Here is the screenshot of my... ipconfig /all..

Originally Posted by Izhar_ITS

Hey essbebe, I've tried what you told... but it is not working!

Here is the screenshot of my... ipconfig /all..

START Network LAN properties
Network page
Disable IPV6

Apply Save.
Start run type cmd type ping 192.168.1.1
type ping say Google

Check Diagnostics page of modem and report Fail entries .

Thanks Dude, Thanks for your help.

The problem was in the line. It has been solved. Using My NET...
Thanks for the help though.

Feel Free to close this thread.