No Internet. Limited or no Connectivity.

[accordingi2ime]

Hi
Ran in to another problem building my system.

I can't connect to the internet.
I am getting limited or no connectivity.
I tried to repair it but it's not working.

I have ASUS P5LD2 Deluxe motherboard
running windows xp x64 professional.
my internet connection is Verizon DSL.

My device manager shows that all my devices are working properly and I can't seem to find what's wrong with it.
Please help.

Thanks

[Ob1]

is your pc connected directly to the modem? or do you have a router connected to your dsl modem?

[accordingi2ime]

it is connected directly to the modem

[Ob1]

http://www.pchell.com/support/limitedconnectivity.shtml

[accordingi2ime]

I tried them but they didn't work.

[Gizmo]

Try this:

http://www.snapfiles.com/get/winsockxpfix.html

[accordingi2ime]

Originally Posted by DBG Try this: http://www.snapfiles.com/get/winsockxpfix.html

tried that also

[Ob1]

if you hook up another pc to your dsl modem are you able to get online? if so then try a different network card.

[accordingi2ime]

Yes I can. I am using a different computer on a same DSL modem. I will try that.
thanks

[Iniamyen]

Have you installed your motherboard drivers? These include network adapter drivers which are needed for them to work.

[accordingi2ime]

I tried using a different NIC but same thing.

Yes. I installed all the drivers.

[Ob1]

reinstall windows and all of the drivers? if it still doesnt work then it could be the mobo? ive had that happen before, where it showed that the network driver was working fine but i couldnt get online. this was on a laptop but it turns out the pcmcia slots where damaged they replaced the mobo, and everything worked again. during that time i had to resort to a usb network adapter until i got it fixed.

[mbossman2]

Originally Posted by accordingi2ime Hi Ran in to another problem building my system. I can't connect to the internet. I am getting limited or no connectivity. I tried to repair it but it's not working. I have ASUS P5LD2 Deluxe motherboard running windows xp x64 professional. my internet connection is Verizon DSL. My device manager shows that all my devices are working properly and I can't seem to find what's wrong with it. Please help. Thanks

lets get a little clarification:

what do you mean by "limited or no connectivity"?
is the icon in the system tray telling you this or are you experiencing something flaky?

[Valian]

he means that its telling him hes having limited or no connectivity, same message ive been getting.

[mbossman2]

it = networking icon in the system tray?

if that is the case, there is an issue with the IP address and subnet being assigned by the ISP.

I would disconnect and power down the modem for 5-10 minutes, do the same for the PC. then power up the modem, let it re-boot properly and then power up the PC. I'll bet this resolves the problem.

[Gizmo]

Originally Posted by mbossman2 if that is the case, there is an issue with the IP address and subnet being assigned by the ISP.

Hold on, isn't the IP address and subnet mask assigned by the modem?

[mbossman2]

I am thinking there may be an issue, wherever in the connection, with the IP addressing and the PC is reporting that fact...

[glc]

Originally Posted by DBG Hold on, isn't the IP address and subnet mask assigned by the modem?

It all depends what model modem it is and what mode it's operating in. If it's a bridge modem, you need a PPPoE client (WinPoet, Enternet 300, RASPPPoE, builtin XP PPPoE) to get connected. If it's a router type modem, the modem handles everything and standard TCP/IP setup works.

Using a bridge modem will always give you the limited or no connectivity error because Windows can't find a DHCP server, but the Internet will still work as long as you use a PPPoE client. Best way to get rid of the error in this case is assign a bogus local IP to the adapter.

[accordingi2ime]

giving bogus ip got rid of the error but still no internet.
sigh.... getting very frustrated.

[accordingi2ime]

it looks like the onboard NIC is bad.
I tried another NIC and it worked.
Is it easy to break NIC? I have 4 PCI NICs and only 2 are working.

How does ASUS Warranty service work? How long does it usually take?

[glc]

It depends how long you have had the motherboard. If it's less than 30 days, you can probably get the board exchanged by the vendor. If you have to send the board into Asus for repair plan on a few weeks for a turnaround.

I'd personally just turn off the onboard NIC in the bios and use a PCI card, they are dirt cheap. Considering they are less than $20 (I've even seen them as low as $5) I don't expect total reliability. The best NIC for the money out there is a 3Com 3C905, even those are down to about $25 now. Those suckers last forever, we use them in servers and have some out there that are almost 10 years old and still running strong.

[Gizmo]

Originally Posted by glc It all depends what model modem it is and what mode it's operating in. If it's a bridge modem, you need a PPPoE client (WinPoet, Enternet 300, RASPPPoE, builtin XP PPPoE) to get connected. If it's a router type modem, the modem handles everything and standard TCP/IP setup works. Using a bridge modem will always give you the limited or no connectivity error because Windows can't find a DHCP server, but the Internet will still work as long as you use a PPPoE client. Best way to get rid of the error in this case is assign a bogus local IP to the adapter.

Thanks for the clarification glc That cleared it up a lot.

Originally Posted by glc Using a bridge modem will always give you the limited or no connectivity error because Windows can't find a DHCP server, but the Internet will still work as long as you use a PPPoE client.

But that's only when the NIC has been assigned a private IP by DHCP, right?

Originally Posted by glc Best way to get rid of the error in this case is assign a bogus local IP to the adapter.

I'm assuming you mean modem when you say adapter?

[glc]

No, with PPPoE, TCP/IP is not used by the hardware Ethernet adapter (local area connection). You can even turn TCP/IP completely off on the adapter. TCP/IP is handled by the PPP adapter, which is a software adapter installed by the connection software. In this respect, PPPoE DSL works just like dialup, the Ethernet adapter is just a passthrough from the modem to the PPP adapter.

I did in fact mean adapter (Ethernet adapter). The modem does not assign IP addresses in the bridge mode, the ISP's DHCP server assigns an IP to the PPP adapter.

[Gizmo]

Ooh, that's what I was confusing. I always consider a modem a PPP adapter, obviously a hardware PPP adapter. Why is there a software PPP adapter? And when you say:-

Originally Posted by glc I did in fact mean adapter (Ethernet adapter). The modem does not assign IP addresses in the bridge mode, the ISP's DHCP server assigns an IP to the PPP adapter.

Do you mean the ethernet card for the Ethernet adapter and PPP adapter in this context, the modem (hardware PPP adapter)?

EDIT: One more thing to add. In a normal setup, nothing bridged, the DHCP address (local private IP) is on the modem, not the ethernet card. Is that right?

As always, I'll start a new thread on this if you think it's neccessary.

[glc]

In the router mode, the modem handles everything (PPPoE login, accepting an IP address from the ISP's DHCP server, TCP/IP) and assigns a private IP address to the Ethernet adapter using NAT.

A modem is not a PPP adapter, but a modem (dialup or a bridged DSL modem) can communicate with a PPP adapter, which is within the OS. The PPP adapter is where TCP/IP starts to happen. Read again - the Ethernet card is strictly a passthrough when you have a bridged modem, it does not require ANY protocols installed except PPP over Ethernet (PPPoE). PPP adapters do not use private IP's, they use real ones.

[accordingi2ime]

new motherboard and still getting the same problem.
Damn... What do I do now?

[randomprecision]

I had the same thing happen to me a couple of months ago. I installed and did everything that these guys helped me with and to my despair...nothing worked.

I reinstalled Windows and it still didn't work...but then I reset the router and then it magically worked. Now unfortunately it happened again yesterday and the funny thing was that I didn't do anything at all except unplug the cable while the computer was off. So now I have no idea what to do.