Strange problem

[StevenJW]

Hi all and thanks in advance.

Okay, here's the beef. I have a Gateway Solo 5300 notebook running Win98 Second Edition which I need to add to a NT4 network. I can't say whether this notebook has been on a network before, as I have no knowledge of it's history. I installed a 3com 10/100 LAN + 56K modem pc card and added all the relevant network settings, (client for microsoft networks with log on and restore network connections and TCP/IP) however, the card will not pick up the network. I have tested the pc card and am happy that it is working. I can't ping the server (destination host unreachable) or log on to the network. The data light on the pigtail jack connector is lighting on 100 mbps, and I know there is data through the cable. I thought maybe it could be a problem with TCP/IP but there's not much I can do short of removing and re-adding the network settings, which doesn't help.

The other thing is that there is a port for an RJ45 on the laptop but I cannot use it as there is no reference to it in windows. If windows doesn't pick this up in device manager, I assume I cannot use it. What should have been a hour job is now going on two days.

If anybody has any ideas on this or has experienced anything like this before I would greatly appreciate any input you might have.

Thanks

Steve

[Spider]

Hi Steve,

Originally posted by StevenJW
notebook running Win98 Second Edition which I
need to add to a NT4 network

NT4 has a group and policies set for the win98 notebook?
Can't you get the person who runs the network to setup
the notebook?

I installed a 3com 10/100 LAN + 56K modem pc
card...The other thing is that there is a port for an RJ45
on the laptop If windows doesn't pick this up in device manager
I assume I cannot use it

If there is an RJ45 port on the notebook then it already
has ethernet capabilities and the purchase of the 3com
was redundant. Either way 3com is a much better quality
than anything Gateway ever put in one of their machines.

I'd get the network administrator to look at the notebook
and request they have a look at it. It sounds like the NT4
has not been setup to let the notebook into the system's
network.

[StevenJW]

Hi Spider,

there aren't any issues with policies or permissions etc on the network for this notebook. It should be able to see the dhcp server with no problems. I put notebooks like this on our network all the time, without experiencing any such issues. Regarding your suggestion that I get 'the person who runs the network' to set it up, well, with all due respect Spider, if I could get somebody else to do it, I wouldn't be posting the problem here. It's up to me to get it sorted, and I should and will!!

Anyway, I re-installed all the networking drivers from the W98 cd-rom and it did actually obtain an IP address from the dhcp server. Still it wouldn't log on or ping, giving 'request timed out', when I tried to ping anything. After I'd re-booted a couple of times, it lost it's IP address, and couldn't find the dhcp server anymmore. I've no idea why this happened as I didn't change of the settings. That's how it stands now. I'm thinking of doing a re-install of W98 from cd, without erasing any of the programs or files on it, which I hope may help. I don't know though. Like I said the network card is fine, and I've never come across problems like this before with trying to put a w98 system on to the network.

Thanks again,

Steve

[Spider]

Have you tried adding the NetBEUI protocol on the win98 machine?

Sometimes you will get network "drops" like your describing. This
is usually caused by the NIC card. Changing to a 3Com NIC solves
that problem for me 99% of the time.

You can reinstall win98 over top like you suggested. This would be the
last thing to try before replacing the NIC. When you reinstall you should
remove the NIC first, then once win98 has been reinstalled and totally
updated from Windows Update then install the NIC and add the NetBEUI
protocol.

With win98 and winME there is a delay for the network to show up after
fully booting up. Wait about one minute then perform pings.

Originally posted by StevenJW
Regarding your suggestion that I get 'the person who runs
the network' to set it up, well, with all due respect Spider,
if I could get somebody else to do it, I wouldn't be posting
the problem here. It's up to me to get it sorted

You'll have to forgive me but I noticed your at the children's hospital
and I assumed there was an IT department there.

Like I said the network card is fine, and I've never come
across problems like this before with trying to put a
w98 system on to the network

Again, some NIC cards will act like this where they seem to
have access and then they all of a sudden don't. NICs are
inexpensive and it just isn't worth trying to force a semi-incompatible
card to behave.

[Alfons]

Have you had the Add New Hardware Utility look for the NIC? If it wasn't installed or was removed, it wouldn't necessarily show in the Device Manager. If your machine does find it, you'll need the NIC driver from Gateway to install before you can configure it with TCP/IP. Once it has been detected, the OS will keep hounding you for the driver until you either install it or remove it from the profile.

[StevenJW]

You'll have to forgive me but I noticed your at the children's hospital
and I assumed there was an IT department there.

Yeah there is spider, and I'm in it, and this is a job I need to get done. Thanks for your suggestions.

[Spider]

I had a Gateway last year (was a desktop) and I to was
asked to add it to the network. I banged on it for a day till
I gave up and put in a 3com, problem solved. I think what
I took out was a D-Link.