alright whats the trick

  • Thread starter Thread starter hp
  • Start date Start date
H

hp

I took some old parts and pieces and rebuilt a 'working' pc, loaded
windows XP pro. it fires up ok, but how do i get it online with a dsl
connection? head is blocked right now and too tired to think well.
no lights on the network ports of the motherboard.
Could there be some steps in XP that I need to ensure was done right?
Did get the mother board drivers all installed I thought.

Do I need to get IE8 before hitting the MS update site?

tanks
 
hp said:
windows XP pro. it fires up ok, but how do i get it online with a dsl
connection?

Who is your DSL provider? What brand/modelno DSL modem are you using?

What country are you in?
 
hp said:
I took some old parts and pieces and rebuilt a 'working' pc, loaded
windows XP pro. it fires up ok, but how do i get it online with a dsl
connection? head is blocked right now and too tired to think well.
no lights on the network ports of the motherboard.
Could there be some steps in XP that I need to ensure was done right?
Did get the mother board drivers all installed I thought.

Do I need to get IE8 before hitting the MS update site?

tanks

1) Verify BIOS settings. Check that the LAN is turned on. You don't
need the LAN boot rom enabled, unless you're doing something like
PXE boot over the net.

2) Step 1 is unnecessary if you check Device Manager while in
Windows, and it's present and the driver is installed. There
may be a couple tick boxes in the NIC device properties, such
as "allow the OS to turn off this device to save power" and
you can untick them so that the LAN is always on.

3) The NIC PHY (physical layer, the part that sends the 1's and
0's on the four or eight wire cable), has a negotiation function.
On some LAN chips, "no LEDs" equals 10BT mode, meaning the
PHY did not manage to communicate over the wire with another
Ethernet chip.

The PHY can also be prevented from negotiating, if the circuit is
jammed in reset. Of course, on a computer, the computer could not
boot if that was the case, so that is eliminated as a cause. But
when you know a LAN works, if the PHY lights don't come on, it's
either power is off or reset is jammed on.

4) Some LAN chips (perhaps Marvell brand), have a nice cable test
function. I have one motherboard, that can test the LAN interface
in the BIOS. The device on the other end of the link should be
powered down, if you're doing that kind of testing. The test is
basically an impedance test. It sends a pulse down each twisted pair,
and sees whether the pulse is hitting a termination resistor at the
end. If a pulse comes back, it can be right-side-up or upside-down,
and the pulse shape and time position, tells you where the cable
is broken, shorted, kinked etc. On other kinds of equipment, such
a test is called Time Domain Reflectometry or TDR. And a crude
version with 1 nanosecond resolution, is built into a few Marvell
gigabit chips. Some other LAN chips have a version of it now, but
they have even cruder time domain resolution.

LAN ports come with no LEDs, up to perhaps a couple LEDs. (Some embedded
systems can have as many as five LEDs, but that's because "we like LEDs" :-) )
It's likely if the port has a couple LEDs, that one LED will light
up for the most common 100BT or GbE negotiations with the other end.
You need a good cable, and a powered LAN box on the other end of the
link, to complete the negotiation sequence, which can be done
totally by the PHY hardware on each end. The OS gets to override
the negotiated value, once the OS is running, so if you "force" some
other LAN setting in the OS, eventually, it takes priority over the
hardware-negotiated value.

When the LAN RJ-45 connector has no LEDs, like on my $65 motherboard,
you've got a lot less feedback to go on.

*******

ADSL comes two ways. If you buy an ADSL modem today, chances are
it has a modem and router all in one. Even if there is only one RJ-45
for output, it can still have a router. One of the router functions,
is to convert PPPOE from the ISP, back into regular LAN packets.

"router mode"
X------ ADSL modem/router ------- Computer, thinks it's on a LAN
terminates PPPOE

I run my setup like this. The ADSL modem routing function is disabled,
and I use a separate router box. That's called "bridged mode".

"bridged mode"
X------ ADSL modem -------------- router ----------------- Computer, thinks
PPPOE terminates PPPOE it's on a LAN

So those are two options for the modern ADSL modem. I chose to do it
that way, because the web interface on my new ADSL modem, is horrible.
Router rules are loaded via a Telnet interface, and I'll be damned
if I'm heading back to the dark ages. The router rules in my
separate router box, are controlled by a web browser, and at
least those I can deal with easily. One of the things I do
in the router, is port forward IDENTD to a non-existent LAN-side
address, for stealth. That's about the only setting I need to make.

As far as I know, you can also do this. But because this limits you to
just the one computer, while my router has four wired ports, this
isn't as flexible. Not all operating systems, have the ability to
terminate PPPOE, and so this is more likely to work on a modern
computer. When I first got ADSL eons ago, I had to install a
software package to handle PPPOE. There was no router when I
set up my first ADSL. (And the ADSL modem only operated in
bridged mode and you had no choice in the matter.) I added a router
a few months later, when I got tired of the PPPOE software crashing.
The PPPOE software built into a modern OS, doesn't crash like that crap did.

"bridged mode"
X------ ADSL modem -------------- Computer, detects the PPPOE interface
PPPOE and has some software stack for it

I think I've tested the previous config on my WinXP box, as part of
my testing. So I did run it for about ten minutes, long enough
to set up the modem part, then once the router box was added and
I switched to the second diagram above, I've never been back
to the interface on the modem. Everything is controlled from
the router box (i.e. logging in to the ISP via PPP).

Paul
 
hp said:
I took some old parts and pieces and rebuilt a 'working' pc, loaded
windows XP pro. it fires up ok, but how do i get it online with a dsl
connection? head is blocked right now and too tired to think well.
no lights on the network ports of the motherboard.
Could there be some steps in XP that I need to ensure was done right?
Did get the mother board drivers all installed I thought.

Do I need to get IE8 before hitting the MS update site?

tanks

Did you install the motherboard's chipset driver package?
 
I took some old parts and pieces and rebuilt a 'working' pc, loaded
windows XP pro. it fires up ok, but how do i get it online with a dsl
connection? head is blocked right now and too tired to think well.
no lights on the network ports of the motherboard.
Could there be some steps in XP that I need to ensure was done right?
Did get the mother board drivers all installed I thought.

Do I need to get IE8 before hitting the MS update site?

tanks


Start please by telling us the exact model of motherboard. That way we can
guide you to the proper LAN drivers for the motherboard.
 
I took some old parts and pieces and rebuilt a 'working' pc, loaded
windows XP pro. it fires up ok, but how do i get it online with a dsl
connection? head is blocked right now and too tired to think well.
no lights on the network ports of the motherboard.
Could there be some steps in XP that I need to ensure was done right?
Did get the mother board drivers all installed I thought.

Do I need to get IE8 before hitting the MS update site?

tanks

Install the mobo driver disk.
 
I took some old parts and pieces and rebuilt a 'working' pc, loaded
windows XP pro. it fires up ok, but how do i get it online with a dsl
connection? head is blocked right now and too tired to think well.
no lights on the network ports of the motherboard.
Could there be some steps in XP that I need to ensure was done right?
Did get the mother board drivers all installed I thought.

Do I need to get IE8 before hitting the MS update site?

tanks
Did you get the correct motherboard drivers? It has been my experience
that motherboard driver CDs come with a number of different drivers for
different chipsets that may have been used on a range of motherboards.
Sometimes the wrong one is picked up by default. Had that scenario many
a time.
 
Could there be some steps in XP that I need to ensure was done right?
Did get the mother board drivers all installed I thought.

Step 1, after installing XP's MB Lan drivers, look for the default
network icon in the tray and plug in DSL modem. Never had network
lites per se at the ADSL port and never had anything but an auto-
connect after that. Both ISP providers I've dealt with, anyway.
Worst part was researching DSL modems, apart from a proprietary field
many ISPs are only too happy to establish in the name of commerce,
keeping customers in a dark place where only the ISPs' technical
support team, with only their equipment, purport to endorse a service
subscription contract.

Like the computer error codes for a Ford product, these days, the
dumber you are, they figure, the least likely you'll gain an inkling
of what they're doing or to switch providers.

I eventually found some beautiful DSL modems that connect like a dream
on a lower power consumption bases, so much better about handling
electrical spikes and, by all indications, look like they'll last
longer. The crap modems they were sending me went belly up the first
time over an outage, and when I'd call, trying to pull out their poor
little fingernails for a replacement modem, they'd whine back to me
about buying a UPS.
Do I need to get IE8 before

Speak English, please. Wad's dat?
 
Step 1, after installing XP's MB Lan drivers, look for the default
network icon in the tray and plug in DSL modem. Never had network
lites per se at the ADSL port and never had anything but an auto-
connect after that. Both ISP providers I've dealt with, anyway.
Worst part was researching DSL modems, apart from a proprietary field
many ISPs are only too happy to establish in the name of commerce,
keeping customers in a dark place where only the ISPs' technical
support team, with only their equipment, purport to endorse a service
subscription contract.

Like the computer error codes for a Ford product, these days, the
dumber you are, they figure, the least likely you'll gain an inkling
of what they're doing or to switch providers.

I eventually found some beautiful DSL modems that connect like a dream
on a lower power consumption bases, so much better about handling
electrical spikes and, by all indications, look like they'll last
longer. The crap modems they were sending me went belly up the first
time over an outage, and when I'd call, trying to pull out their poor
little fingernails for a replacement modem, they'd whine back to me
about buying a UPS.


Speak English, please. Wad's dat?

Pot Kettle Black LOL!!!!!!
 
I took some old parts and pieces and rebuilt a 'working' pc, loaded
windows XP pro. it fires up ok, but how do i get it online with a dsl
connection? head is blocked right now and too tired to think well.
no lights on the network ports of the motherboard.
Could there be some steps in XP that I need to ensure was done right?
Did get the mother board drivers all installed I thought.
Do I need to get IE8 before hitting the MS update site?

------------------------------------------------------------------

reply: Who is your DSL provider? What brand/modelno DSL modem are you
using?

What country are you in?

I wouldn't think this is an approach that would help. I have hardware
for the DSL connection that seems to work just fine, all I have had to
do until this particular situation is plug the PC network cord in and it
is allowed to go online provided the PC is capable.
This was the case with the 4 machines that do connect to the internet
now via the DSL connection.

---------------------------------------------------------------

reply: Did you install the motherboard's chipset driver package?

I do believe that I stated this in the original question message,
the motherboard CD seems to have done its thing when I installed drivers
off of it, BUT I will admit that so far I have not tested all the
functions. I thought I would do all the basic stuff then get all the
updates for windows XP 32bit before trying to hook up more stuff to the box.

----------------------------------------------------------------------

reply: Start please by telling us the exact model of motherboard. That
way we can guide you to the proper LAN drivers for the motherboard.

Would this NOT have been addressed when I used the motherboard drivers
CD to install the drivers as I stated I did? This was Done Before I
tried to go online with the setup to get windows updates.

But just in case its of any real value, ASUS A7NBX-E
This motherboard was working earlier this year, and has not been out of
service all that long. the current setup included a fresh HD with a
fresh install of windows XP PRO 32bit and a little more memory then it
had a short while ago.

--------------------------------------------------------------------

reply: Install the mobo driver disk.

I sure thought I did this. Right Off the CD that came with the motherboard

-----------------------------------------------------------------

reply: Did you get the correct motherboard drivers? It has been my
experience that motherboard driver CDs come with a number of different
drivers for different chipsets that may have been used on a range of
motherboards. Sometimes the wrong one is picked up by default. Had that
scenario many a time.

this I can't answer 100%, the CD's autostart process was allowed to
happen and the install program was allowed to do its thing as
automatically as possible, I had very few choices to make and very
little interaction with the install process.

-------------------------------------------------------------------

reply: > Do I need to get IE8 before.

Speak English, please. Wad's dat?


well, since I am installing Windows XP Pro (32bit) IE (INTERNET
EXPLORER) is installed by default AND to easily use the microsoft update
process a user NEEDS IE something to do so via the online process.
ERGO since the older XP PRo disk has IE6 and Not any newer versions on
it, the question was and is, Do I Need to Use IE8 on the microsoft
update site?? Specially Since MS is trying their hardest to kill off
the use of IE6 per their statements somewhere.

--------------------------------------------------------------------

Ok, I know I have been a tad slow in all this, but so far Time seems to
be on my side, so I have done little to the setup in the last week.
I addressed a problem with it not working every time I pressed to 'ON'
button and now the PC boots each time its asked to do so. But I really
haven't spent any serious time with it since the initial request. I
should buckle down in the near future to solve things.

I Did verify that both network ports on the motherboard have 2 LEDs
lamps per port, and thats why I was expecting to see some form of LED
lamp activity after the network cord was plugged in.

There were 2 responses with things to explore and pay closer attention
to and as the brain digests that I will develop my next plan of attack
and still try and get this thing online.

IF I can resolve the apparent connectivity problem.

Thanks for putting up with this
 
hp said:
all I have had to do until this particular situation is plug the PC
network cord in and it is allowed to go online provided the PC is
capable.

You stated just the opposite in your original post. "network ports of
the motherboard" says you were trying to use the NIC provided as a
backpanel connector on the mobo, NOT as a daughtercard you pushed into a
slot. Because YOU said that you were using the onboard NIC is why
others suggested installing the chipset drivers for that mobo.

The PC won't be "capable" until the OS has a defined interface to the
hardware and that requires the drivers.
I do believe that I stated this (installing the drivers) in the
original question message

Where? Reread your original post. There was no mention that you ever
installed any drivers to define either the onboard NIC (which is part of
the mobo chipset) or for the daughtercard NIC (something that wasn't
known until now).
reply: Start please by telling us the exact model of motherboard. That
way we can guide you to the proper LAN drivers for the motherboard.

Would this NOT have been addressed when I used the motherboard drivers
CD to install the drivers as I stated I did?

We don't know what program you ran off the CD because even you don't
know what you ran.
This was Done Before I tried to go online with the setup to get
windows updates.

Never ... N-E-V-E-R ... install hardware updates from the Microsoft web
site. Too often they detect the device wrongly and give you a driver
for a different model or proffer a version that isn't appropriate for
your particular hardware. Only use their "update" as indication that
you may want to go to the hardware maker's web site to see what THEY
offer for the latest version of driver for what you really have. Of
course, if the hardware is working, there's no need to update to a later
version of the driver: a new driver won't make work what's already
working.
But just in case its of any real value, ASUS A7NBX-E

While I could dig through ASUS' web site and their support pages looking
for the chipset package for you (and others may be willing to do it for
you), you could drill through there yourself and you should since it's a
good idea to get acquainted with the maker's support site for your
computer.

http://service.asus.com/
Product Support -> Motherboard menu
Download Drivers link

When I search on "A7NBX-E", there were no hits. You sure that's the
proper model number for your mobo? You sure the model isn't A7N8X-E (an
8, not a B). I could find a hit on A7N8X-E, selected it, and under the
Downloads tab I select Windows XP for the OS.

They didn't list Windows XP Pro (32-bit) and Windows XP Pro x64 so I'll
assume this mobo isn't 64-bit hardware. They listed 2 LAN drivers which
are the same but just different versions: latest and next to latest (for
what they support since there could be later drivers from the chip
maker).
This motherboard was working earlier this year, and has not been out of
service all that long.

Since you flattened the machine by doing a fresh install of the OS, that
it worked before is only relevant in knowing that the hardware used to
work before. With the fresh OS install, you're starting from scratch.
reply: Install the mobo driver disk.

I sure thought I did this. Right Off the CD that came with the motherboard

Which makes me look at your statement that there are no lights when you
plug in the CAT5 cable into the NIC port on your mobo. Even without an
OS loaded (which is when the drivers gets loaded to define an interface
for the hardware to the OS), the hardware should still function on its
own. The LEDs alongside the NIC connector will be unlit when no cable
is plugged into it. The lights will still not be lit when you simply
plug in a cable. It's when you plug the other end of the cable into
another network device that the lights should appear (on both ends).

The LEDs on the NIC (on both ends) should behave as follows:

10 LNK Green:
Description: Link integrity
If flashing: Reversed polarity
Steady on: Good 10BT connection
Off: No connection between NIC & hub
100 LNK Green:
Description: Link integrity
If flashing: Reversed polarity
Steady on: Good 100BT connection
Off: No connection between NIC & hub
ACT Yellow:
Description: Port traffic for either speed
Flashing: Network traffic present
Steady on: Heavy network traffic
Off: No traffic

The meanings of the LEDs could vary between manufacturers but the above
are the common meanings. The manual for your mobo should tell you what
to expect for lighting of the LEDs.

You sure the cable is okay? Have you tried another cable? With nothing
attached to a NIC port, the lights are off (no 10/100 LAN connection so
obviously no traffic). With a cable attached, well, it's not a device
so there's still no connection to *something* else. With a cable
attached on both its ends (and assuming both devices are powered up)
then you should see one of the green LEDs is on to reflect the hardware-
level negotiated speed (the yellow active LED will only flash if there
is some traffic).

By the way, there is a cross-over Ethernet cable used to connect 2 hosts
directly without an intervening comm device. I doubt you want to be
using that in your setup (although some devices will detect the
incorrect cross-over and adjust for it). You need a straight-through
Ethernet cable (i.e., a normal one).
reply: > Do I need to get IE8 before.

Speak English, please. Wad's dat?

The OS and whatever apps are installed in it, like IE, are irrelevant if
you aren't first getting the *hardware* to negotiate a connection
between the 2 devices on either end of the cable. You said there were
not lights on the NIC. Presumably that statement meant your computer
and another device (router, cable modem, switch, or whatever your
computer is connected) were both powered up and connected with a good
cable at the time you noticed there were no lights. The hardware has to
work correctly before the OS, drivers, or any app can utilize it.
I Did verify that both network ports on the motherboard have 2 LEDs
lamps per port, and thats why I was expecting to see some form of LED
lamp activity after the network cord was plugged in.

Yep. With a good non-specialized cable connecting two NICs that are
powered up, you should see a green LED on both ends.

I'd try a different cable. You might find wiggling the old cable may
show an intermittent light but only if the connection of wire to
connector were intermittent versus permanently disconnected. Although
there is a strain relief inside the RJ-45 connection (where a plastic
insert gets pushed down onto the cable), it's a friction relief and you
could end up pulling away the wire from the connector which scissors
through the insulation to contact the wires. It could be a bad
connection in the connector isn't making good contact with the wire.
Try another cable.

If you have another port on the router, switch, or to whatever your
computer connects, see if switching to another port gets the LEDs lit on
your NIC. Typically its the cable that is bad or goes bad but sometimes
users are abusive to the connectors for the ports. Look inside the port
connector. It could be the pins inside the connector that stick out to
contact the pins on the cable have been smashed (back up so they won't
contact the connector) or got misaligned (since they are just sticking
out into the air space inside the female connector). The female
connector's contacts are wires that either look like they're small
springy wires sticking out into the airspace inside the connector or
curved pins that stick out onto which the jack's pins slide onto (it's a
friction connection). If the pins don't push hard enough against each
other, they don't wipe against each other enough to eliminate oxides and
reduce resistance. These are just 2 wires pushing against each other
along the same face of each wire.

If the female connector's pins are damaged, you might be able to use a
small pick or tweezers to bend them back into position. These pins (on
male and female connectors) may not be gold plated (just [nickel-plated]
copper or brass) so they could have oxide on them so repeatedly
re-inserting the cable to repeatedly wipe the contacts could get a bad
connection working again. If the locking tang is missing from the male
connector on the cable, replace the cable (or the connector if you have
the crimper); else, the connection will work itself loose and you may
not be fully inserting the male connector to ensure good contact between
the wires.
 
hp said:
On 11/16/2011 11:35 AM, hp wrote:
But just in case its of any real value, ASUS A7NBX-E

It's probably A7N8X-E Deluxe.

Ben used to post to USENET years ago, and I expect
the info in this table is still useful (as new drivers
don't keep on rolling out).

http://www.ben.pope.name/a7n8x_faq.html

"Which drivers should I install?"

Win XP Win 2K Win 98/me
nForce2 nVidia ForceWare 5.10 nVidia ForceWare 4.27 nVidia ForceWare 4.27"

*******
From the nVidia ForceWare 5.10 download page...

http://www.nvidia.com/object/nforce_udp_winxp_5.10

Windows XP Driver Versions

* Audio driver 4.42 (WHQL)
* Audio utilities 4.44
* Ethernet driver 4.42 (WHQL) <---- makes your "upper" connector work.
* GART driver 4.36 (WHQL)
* Memory controller driver 3.38 (WHQL)
* SMBus driver 4.04 (WHQL)
* Installer 4.46
* IDE NVIDIA driver 4.46 (WHQL)

*******

I have the A7N8X-E Deluxe here, and it has two LAN
connectors. I'm willing to bet, one of the connectors
will start to work, when you install nVidia ForceWare 5.10.
The connector near the PS/2 connectors, is connected
to a PHY chip, and the MAC is in the Nforce2 Southbridge.
Once you install ForceWare, that one should work.

The lower one (RJ-45 furthest from the PS/2 connectors),
runs to a Marvell 88E8001. And you can likely get the
latest driver right from Marvell for that. Go to marvell.com
and look for the Support link. I think what that download
gives you, is a simple NDIS driver (right click .inf file,
select "Install" from the menu). It means doing a manual install.

If you go to support.asus.com and find their download
section, they have a driver package which is 20 times larger,
and includes a nice automated install (complete with support
for Virtual Cable Tester). I expect it'll be easier to figure
out how to install that one.

http://support.asus.com/Download.aspx?SLanguage=en&m=A7N8X-E Deluxe&p=1&s=10

http://dlcdnet.asus.com/pub/ASUS/lan/marvell/Marvell_v628.zip

Paul
 
Back
Top