TCP/IP auto obtains IP cause LAN no connectiv

August 20, 2011 at 15:06:48
Specs: Windows XP
This is the initial time to set up a new DSL provider's modem with their tech support.
TCP/IP auto obtain IP address does not work (LAN status is 'limited or no connectivity'),
entered static ip/dns, then LAN status is 'connected'. However, can't access internet
(...DNS lookup failed...). After several calls over 5 hours w/ tech support, now only works
using a manual broadband connection when cable physically connects modem and pc. Tried once to add wireless router(reset modem, connect and cold boot all 3 devices...) while the tech
supporter was on phone, but broadband connection won't work any more. So the service rep
said I had connection and could access internet, the router is not his issue.

Is this the new modem problem or the provider server issue. I have had SBC DSL for years
before swith to the new provider, everything worked fine. I also tried cable connect to a
different laptop, got the same problem. Both PCs can still connect to my neibauer's
wireless router no problem. Should I spend time on config the router (it worked with SBC
DSL) or shouldn't waste time because the problem is on the modem?

Any help is really appreciated.

Thanks,

Virginia


See More: TCP/IP auto obtains IP cause LAN no connectiv

Report •

#1
August 20, 2011 at 16:35:59
The tech support is correct on one thing. The router is not his issue & I don't think it's a provider issue. What is the make & model of the DSL modem? What port configuration does it have? Is it only wireless that doesn't work? If WEP or WPA is enabled on the router, make sure you entered the proper key on the PC if you are using wireless or disable the encryption for now.

If it still doesn't work open a command prompt & run ipconfig /all Post the output here.

How do you know when a politician is lying? His mouth is moving.


Report •

#2
August 20, 2011 at 21:20:30
Thanks for the reply. The modem is D-Link DSL-2320B from the provider. Currently my pc is working only have cable connected to modem and using a manual broadband connect (LAN does not work). Here's the output of 'ipconfig /all'.

Windows IP Configuration
Host Name . . . . . . . . . . . . : vvNetbook
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon 88E8040 PCI-E Fast Ethernet Controller
Physical Address. . . . . . . . . : 00-13-77-FD-08-6E
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.203.62
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Atheros AR5007EG Wireless Network Adapter
Physical Address. . . . . . . . . : 00-24-D2-9D-96-3E
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
192.168.0.1
Lease Obtained. . . . . . . . . . : Saturday, August 20, 2011 5:47:47 PM
Lease Expires . . . . . . . . . . : Sunday, August 21, 2011 5:47:47 PM

PPP adapter vvDsl2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 99.29.237.235
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 99.29.237.235
DNS Servers . . . . . . . . . . . : 68.94.156.1
68.94.157.1
NetBIOS over Tcpip. . . . . . . . : Disabled

Thanks,

Virginia


Report •

#3
August 20, 2011 at 22:36:09
I changed the router's WAN connection mode from dynamic to PPPoE which allowed me to enter my id and password, and the wireless router works fine now.

Thanks for your help.

Virginia


Report •
Related Solutions


Ask Question