Networking fings
Discussion
Trying to get an old IBM laptop (thinkpad 380ED) running Win98 to access the internet via my WGT624 Netgear router and Zyxel broadband modem.
I've got a 3com pcmcia ethernet card and lots of ethernet cable but I can't get it to work.
Is there some setup I need to do on the laptop once the ethernet card software has loaded?
Ta.
I've got a 3com pcmcia ethernet card and lots of ethernet cable but I can't get it to work.
Is there some setup I need to do on the laptop once the ethernet card software has loaded?
Ta.
Ohh bloody hell... erm...
Start > Control Panel > Network? Sorry it's been a while for Win98, but basically you need to go in to the properties of TCP/IP for that network card and tell it to "Assigned Automatically" on everything to do with the first tab.
Actually, if the little two computers icon is down the bottom by the clock, double click that for instant shortcut goodness.
After it's finished faffing around, it should try to pull an IP from the router, I belive Start > Run > command will get you a prompt and ifconfig should work (hopefully). If it says 169.blah something is up with either the network card, the drivers, the port on the router or the cable.
Make sure you're getting a link light on both ends and that the router is set to do dhcp.
If you're getting 192.168.blah then the router is issuing the IP's properly and you need to look at the configuration of it so it'll talk to your modem.
Start > Control Panel > Network? Sorry it's been a while for Win98, but basically you need to go in to the properties of TCP/IP for that network card and tell it to "Assigned Automatically" on everything to do with the first tab.
Actually, if the little two computers icon is down the bottom by the clock, double click that for instant shortcut goodness.
After it's finished faffing around, it should try to pull an IP from the router, I belive Start > Run > command will get you a prompt and ifconfig should work (hopefully). If it says 169.blah something is up with either the network card, the drivers, the port on the router or the cable.
Make sure you're getting a link light on both ends and that the router is set to do dhcp.
If you're getting 192.168.blah then the router is issuing the IP's properly and you need to look at the configuration of it so it'll talk to your modem.
detchibe said:
rednotdead said:
Apart from that, wot he said above...........
He?! Edited by rednotdead on Sunday 10th June 16:22
rfisher said:
Thanks.
No lights either on the card adapter cable thing that tells you if it's 10 or 100mbs or the router.
Think the card and slot may be 16 bit not 32 so maybe it's time for the bin?
Try a different length of cable and make sure Windows is detecting the card properly. No lights either on the card adapter cable thing that tells you if it's 10 or 100mbs or the router.
Think the card and slot may be 16 bit not 32 so maybe it's time for the bin?
Edited by ThePassenger on Monday 11th June 01:40
The Griffalo said:
K77-widow maker said:
how about from a command prompt, pinging 127.0.0.1 and seeing if you get a reply.
If you do then your nic is working and the problem is further down the line.
Not quite... You know your IP stack is alive but the HW can still have a problem....If you do then your nic is working and the problem is further down the line.
rfisher said:
Still confused about the ethernet cable - crossover or straight?
As it's all old gear, including the 3com card, I presume it won't automatically switch the cable connection itself if it's the wrong cable type as newer hardware can.
Exactly. Old n' busted. You'll need to give it a helping hand. As it's all old gear, including the 3com card, I presume it won't automatically switch the cable connection itself if it's the wrong cable type as newer hardware can.
Do the start/run/winipcfg thing above, if the 3com card isn't listed in the drop down box at the top then the drivers aren't working/installed properly. If it is, the problem is elsewhere. If you list everything thats listed in control pannel/network I might be able to make some suggestions.
K77-widow maker said:
The Griffalo said:
K77-widow maker said:
how about from a command prompt, pinging 127.0.0.1 and seeing if you get a reply.
If you do then your nic is working and the problem is further down the line.
Not quite... You know your IP stack is alive but the HW can still have a problem....If you do then your nic is working and the problem is further down the line.
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff