Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I have a Win98 desktop PC and a Win98 laptop connected via an ethernet crossover cable. I have the PC CD shared so I can install software on the laptop.
While installing software over the network connection, I jumped on the Net via the dialup on the PC. Once connected to the net, the connection between the PC and laptop dropped out and I have not been able to re-establish the connection since.
I've removed the PC network drivers and re-installed. I have not done the laptop driver as it is not mine and I did not have the driver disks etc.
Any ideas???

the first rule of networking .......... never use windows 98 for the purpose
use win 2k/xp/ntrgds
raja

Disregard what Raja said....I networked at home with 98 for years without trouble. Don't let the fact that I'm an IT professional fool you either. 98 was designed to network in a basic workgroup scenario and anybody can do it.
Judging from the original post, your problem started when you decided to go online via dialup while installing software on the laptop from the PC's CD. I hope you learned your lesson, don't do that! *smile*
You may have to go into device manager on both the PC and laptop and remove the NIC and restart so 98 can "find" the new hardware and reinstall it. Then reinstall your TCP/IP and configure it and your LAN connection should start working again.

I forgot to add, if you need some basic networking help (and I think Mr. Raja does too!) try the following web site:
www.wown.com

Curt,
I have 2 win 98 PC's wired to a linksys router that goes into by modem. One of the PC's has a printer hooked-up to it. Both PC's can share the printer. I have another wireless router wired into the other router. A MAC is wired to the wireless and I have a wireless laptop. All can see the internet. Now for the problem...I can't get the wireless laptop to see/share the printer. I changed the PC with the printer to the same workgroup name as the laptop...no luck. Can you tell me what I'm missing? Thanks.

Curt (and Raja),
Thanks both for your replies. I had a feeling that it was going to be a case of re-load the laptot drivers. I'll give it a try.I have not gone to 2000 and/or XP because I prefer 98 cause it works better. But that's the beauty of personal preferance. Hey.
Cheers

Darryl...
Each router creates its own LAN; You can't network with a printer on another LAN quite so easily By default the wireless router automatically drops packets originating from clients to the other router because these have "local" IP Addresses so LAN#2 clients can't "see" LAN#1 clients even though clients on both LANs can see the Internet.
If you were using a wireless bridge/wireless access point it would work because a bridge doesn't create an internal DHCP client/server network; The wireless clients would use instead use LAN#1's router for their DHCP server and there'd only be 1 network.
IIRC for what you're doing you have to set the wireless router's default IP Address from 192.168.0.1 to something above that of the last IP address on LAN#1, set the local address range to start with this number, and then disable port filtering. That allows packets to flow freely between LAN#1 and LAN#2, LAN#2 client packets won't conflict with LAN#1 client packets and vice-versa, and they'll both still be protected by the firewall on the LAN#1 router.

Curt,
Thanks for getting back to me. I should have mentioned that I did set the wireless router's IP address to 192.168.0.2 and I believe I disabled it as a DHCP Server to get the wireless laptop to see the internet when I set it up. I'll confirm that. When you say "set the local address range to start with this number" is that what I did by setting the wireless router IP address to 192.168.0.2? Also I'm assuming I need to get to the admin screen of the wireless router to disable port filtering. I will look at that tonight as well. Thanks for your help and I'll let you know how it goes.

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |