adiemus00

I have three computers I am trying to network. I have a 3Com hub with my cable modem in the uplink port. the three computers are all plugged in and all have internet access.

My newest computer, with Windows 2000 as its OS, can see the newer of the other two computers. (the older computers have Windows 98 SE on them) The Win2K computer is the "D" computer. D can see D and C. C can see B, C and D. B can see B and D.

I am aware that Windows 2000 ptp access is gained by having the same logon name, so I've given all three computers the same password-less logon of my first name. I have Microsoft/3Com Homeclick software that diagnosed the network failure on one of the Windows 98 machines (which was the "browse master" wasn't enabled.) I just don't understand why my computer consistently sees the newer of the older computers, but not the other one.

I just recently upgraded the older one (albeit, rebuilding most of it) and it has a new network card (an SMC instead of the 3COM that came with my hub). The result is the same. My newer computer still can't see the rebuilt machine. I hope this isn't confusing. I'm just a bit frustrated. It seems that every time I turn around, the network isn't working again.

Is it just that Windows 2000 is not a ptp computer? I like Windows 2000 much more than any Win 9.x computer. It runs ALL of my programs and games and it's very stable. I'd install Win2K on all of my machines if I didn't have it on some proprietary 'recovery disk' from my newest computer's manufacturer.

Any help would be appreciated.

Jeffbx

A little more info - what protocols are you running? TCP/IP, I imagine since they can all see the Internet. Any others? What address, subnet mask, and default gateway are you using on each machine? Or are you running DHCP?

Are all the machines in the same workgroup with a unique computer name?

adiemus00

The Win2K's (computer-D)computer
Protocols: TCP/IP, IPX/spx, netBeui, and NWLink.
IP: 24.2.208.48
Subnet Mask: 255.255.255.0
Default Dateway: 24.2.208.1

The Newer Win98 machine (computer-C)
Protocols: TCP/IP, NDISWAN and IPX/SPX;
IP: 24.2.208.33
Subnet Mask: 255.255.255.0
Default Gateway: 24.2.208.1

The older Win98 machine (computer-B)
Protocols: TCP/IP, NDISWAN and IPX/SPX;
IP: 24.15.163.245
Subnet Mask: 255.255.255.0
Default Gateway: 24.15.163.1

Update: The two Win98 machines can see all three computers. It is only the Win2K machine that cannot.

adiemus00

I forgot to say.. The computer names are all unique (given to me by @home) and the workgroup names are all the same. If they weren't, none of the computers would see each other, right? It's just the Win2K machine not seeing the B computer. Is the default gateway the culprit? I am using DHCP, although I'm not sure how it is enabled or disabled. I know that I have to ad the IP address of the DHCP server to Zonealarm so my computers stay connected to the internet.

Jeffbx

Hm - interesting. With all those protocols running around, I'd think everything could see everything!

OK, here's my opinion - the W2K machine can see the newer one because they're both in the same subnet. The subnet mask 255.255.255.0 means that the PC can see everything in the range 24.2.208.0 - 24.2.208.254. Because the third PC is outside of that range, W2K cannot see it. The reason that the 98 machines can see each other is that they are using IPX/SPX rather than TCP/IP. I don't know why your W2K machine is not seeing them with IPX.

Anyway, here's what you can do:

Add a static route on your W2K machine that makes it believe the third PC is also local. Go to a DOS prompt in W2K and type:

route ADD -p 24.15.163.245 MASK 255.255.255.255 24.2.208.48

This tells your W2K machine to send all requests to that IP address to the local network rather than your gateway, which would send the request to the Internet where it would time out.

Then try to ping the address of the third PC. If you can ping it, you're good to go.

If you're feeling lucky, I would also suggest removing every protocol except for TCP/IP, and do the same route command on the second 98 machine, substituting the last address for its own IP address. Every additional protocol on a network adds additional overhead. Now, on a 3 PC network, it ain't a lot of traffic, so you don't have to sweat it unless it bothers you.

adiemus00

The IPX/SPX says in front of it "NW Link" and then in description, it says: "an implementation of the IPS/SPX protocols used by netware networks." could that be the cause. I was guessing the default gateways were the problem, but there's nothing i can do about that, is there? Could I manually assign everything and get around all that? does the default gateway HAVE to be the one that is assigned through DHCP?

I did what you said and I can ping the other computer (once I allowed my computer through the Zone Alarm firewall), but I still don't see it in my network places on the Win2K computer.

Jeffbx

You don't want to change the gateway address - if you do, you won't be able to see the Internet.

Do you have file & print sharing turned on on the 98 machines?

adiemus00

Yeah, the file and print sharing is enabled on all three machines. I was able to keep all the computers seeing each other when I had three Win98 machines, so I guess I have to upgrade the other machines to windows 2000 or maybe XP when it comes out. So long as I can connect to one of the computers and they can connect to each other, I guess I have a 'transitive' ptp network.

I did a search for computers and was able to find the older one, but I still don't know why it's not showing up in "my network places" unless it's finding it on the internet. Seems the more I know, the more I need to know.

I thank you for all of the assistance though. I am just going to resign myself to the fact that what I probably need is the same operating system on ALL of my computers.

Jeffbx

You really don't need the same OS on every machine - 98 & 2000 can network together just fine. It just takes some tweaking to get them all to be happy. Sure, it IS easier if they're all the same OS, but it is not required.

adiemus00

I had an idea last night. I've had the hub and the network up and running about a year now, but I have considered using a router/firewall appliance. Would that solve my issues since all the IP's would be internal?

marchk

Try putting those pc's in the hosts file.

using this syntax:
IP Address Computer Name


It may or may not fix your problem.

__________________
"This ain't no burger flippin job!"

Grimm

That could solve your problem. I would try it. It would have the added advantage of making your network a little more secure.

adiemus00

Well, the network is secure as far as I know. I installed ZoneAlarm after I had my first Trojan show up on my computer. Ever since, I've had no problems. It's just the whole decision making process for which firewall/router I should use. One where I don't need an added hub and one that is going to work for my different OS's.

Jeffbx

The router doesn't care what OS you are using, as long as it's running TCP/IP. The router may make networking easier by providing DHCP addresses, though. Then you just set the IP for DHCP & don't worry about it.

adiemus00

Well everyone, the problem is solved. I got myself a $120 LinkSys router/firewall and connected all of my computers. The Win2K computer is a bit slower in loading the other computers' contents in network neighborhood (probably because, according to my reading, it shares files through TCP/IP not IPX/SPX), but it's fully functional. I thank everyone for their help, especially Jeffbx. I much prefer the router. $14.00 less per month (subtracting two IP's that I was paying for through @home) and I can assign whatever computer names I want to make it easier to identify in Network Neighboorhood.

Thanks again!