On Mon, 04 Sep 2006 21:09:34 -0400, kony <spam@spam.com> wrote:

>Try the card in the slot the sound card is in, and leave the
>sound card out temporarily.
>

Done. Wired works. wireless doesn't.


>What evidence do you have that it connects?

The indicator is 'green'. It says 'connected, at 98-100% connectivity.


>Voltage levels good on the 5V and 12V rails?


>
>When you have no internet access, first thing to do is check
>the signal strength.

Signal strength is fine. Laptop on wireless connects just fine.
Connection on problem pc is fine.



>Did the link lights on the NIC and the
>switch/whatever-on-other-end, light?

Yes. Router indicated that nic card was online, and nic card did light
up.

>Did it have the right
>IP range address assigned? What did (command prompt...)
>IPCONFIG /ALL show?

No. Not with the wireless card. But even if I put in the regular nic
first, and set that up, actually, had both in at the same time, and
the wireless didn't work.


>
>Could it ping itself (it's IP address) ? How about anything
>else on the lan?

Itself yes. Anything else no. Well, actually, it could ping the
router, when I manually added a gateway and subnet mask. No DHCP
though.

>Could you pull up the router configuration
>screen over HTTP (web browser)? Does your router/whatever
>have a HTTP configuration screen?

Not available on wireless. works with wired.


>Hmm, I should read ahead more often. The
>troubleshooting-networking stuff above still applies though.

Assume I did the troubleshooting stuff. I did a lot of troubleshooting
before asking here.



>Well of course THEN, you will only have it bound to one
>adapter at a time.

Or, not. I've had wired and wireless running at the same time on other
systems, and it worked just fine when I pulled either out. So, this is
just not applicable.


>
>You might check on a bios update for your motherboard, but
>it's way too early to conclude (blame) it's the problem, so
>read any available bios notes on motherboard manufacturer's
>site to see if anything stands out.

But why would it work yesterday, and not today?


>
>What are you calling "network access"?

Umm. Anything relating to connecting over a network to anything other
than the problem computer. The physical 'network' is there. either
wired, or wireless. It works there. But the actual network access.
Connecting to another computer. Connecting to the internet. Pinging
anything other than itself.

>Did you try pinging anything/everything?

Yes. Nothing but itself.

>Does your router (or is it through an access point or ??)
>show this system in it's connected-client list (if it has
>one), or at least that card's MAC address?


Rout

>Also low odds, not impossible, but insufficient info about
>the state of the wireless connections. Swapping these cards
>around might've just confused windows, when you did the
>reinstall was it overtop of an existing installation or a
>clean install?

Uninstall first, before installing new cards.

> Do you have the wireless card manufacturer's
>utility installed?

Yes. for both cards.


>Working, but at good signal strength where this desktop is?


>If you had a really bad computer case, or the board was
>canted funny on the standoffs so the cards weren't sitting
>in the slots right, that might cause a problem, or if the
>slots had a contact defect or a lot of gunk (like in a smoky
>or other airborn polluted environment) then perhaps bad
>contact with the cards. You'd probably be able to see this
>though, if you had a good view of the board slot and a
>strong flashlight.

Can't see anything like that.


>I suggest you pick the card you consider
>the better of the two, put it back in and run the windows
>"Internet Connection Wizard" or "Connect to Internet" (or
>whatever it's called on Win98 I don't recall, but IIRC it's
>off the start menu, maybe in Communications folder). Then
>reboot windows- win98 loves to be rebooted.


Did this 7 times before asking here.


>
>Come to think of it, on win98 you have another tool besides
>Ipconfig, it's on the start menu (start-> run -> (type)
>"winipcfg" ).

Winipconfig, and the DOS ipconfig all fix the problem. They just show
that the problem exists.

Funex.