Click to See Complete Forum and Search --> : Can't get a whopping TWO-NODE network going.
gstokes
January 18th, 2000, 01:14 PM
I have a computer running Windows 98 v.2, and another running NT 4 SP6. They're both plugged into a 3Com FMS II hub. Both their network cards seem to be working fine. The NT computer is not a domain controller. These are the only computers on the network. They're in the same room, and cable runs are very short. The cables are OK.
TCP/IP is the only protocol installed on each computer. The 98 has automatic addressing turned on. Since NT doesn't have this feature, the NT computer has an IP address of 1.1.1.1 with subnet 255.255.0.0.
The 98 has file and printer sharing turned on, and the log-on is set for "Client for Microsoft networks". They're both set up with the same workgroup name and unique computer names.
They can't see each other. Even more perturbing, the Network Neighborhood doesn't even exist on the 98 computer. The NT computer sees only itself under the Network Neighborhood.
On the NT, LMHOSTS lookup is enabled. Basically, everything was left at default.
Where is the 98's Network Neighborhood, and how am I supposed to configure the network settings so these two can see each other?
Thank you!
January 24th, 2000, 11:10 PM
For the 98 machine, usually the Network Neighbourhood icon wouldn't show, if the NIC drivers are not install on the machine, as
soon as you install the respective driver for your NIC, it will show you Network Neighbourhood icon on the desktop.
I'm not sure about the IP address that you have assigned to yor NT machine. Usually, for a private network, I would use 10.0.0....
or 192.168.90.... address with their respective Netmasks. Make sure that they both are on the SAME Subnet !!!
The hub between the 2 machine is pretty much redundant, if you have a cable that's long enough to connect directly to each other.
gstokes
January 25th, 2000, 04:30 PM
Thanks for the info.
The Network Neighborhood didn't show up even after I had the NIC installed and functioning.
I have the hub in place in case I want to plug in a third computer from time to time.
Another problem is that Internet Connection Sharing just doesn't seem to work. It always reports a malfunction immediately after installation, even on a totally clean machine. Pathetic.
Gavin
Explorer
January 31st, 2000, 03:53 PM
Does your control panel show the "network" icon ?? If yes, play around with that to setup the Net. Neigh. setting. What NIC do you use ?(spec.)
How are you connecting to the internet ??
Explorer
January 31st, 2000, 04:10 PM
Does your control panel show the "network" icon ?? If yes, play around with that to setup the Net. Neigh. setting. What NIC do you use ?(spec.)
Make sure that you sign static IP on both of the machines that are on the same netmasks.
How are you connecting to the internet ??
tdrury
February 22nd, 2000, 03:29 PM
I wouldnt run those IP addresses. Manually set your IPs to 192.168.1.1 and .2 with a netmask of 255.255.255.0. This will make sure they are on the same subnet.
Then trying pinging _yourself_:
ping 192.168.1.1 (or .2)
If you get "network unreachable", then your card/driver isn't installed correctly. After you get that resolved, ping the other machine. 99% of the time, problems are due to the card/driver not being setup properly.
-tim
gstokes
February 23rd, 2000, 01:33 PM
Thanks.
I did get the thing working, more or less. I had a bad network card in the 98 machine.
However, although the new card works, it's no good either. It's a Netgear FA 310TX, and it causes inexplicable temporary hangs. You'll launch a program or click on a hyperlink, and the computer will do nothing. After 20 seconds of sitting and waiting, the program will continue.
I disabled the network card in the Device Manager, and the problem disappeared.
I sent a message to Bay Networks about this, and they said I had to set up a SERVICE CONTRACT with them to get any support! For a $20 network card!
What jerks.
codeguru.com
Copyright WebMediaBrands Inc., All Rights Reserved.