Question about 'Getting Network Neighborhood to recognize newly attached computers'
Tuesday, January 29, 2002 at 4:41 pm
Posted by John Holmes
(1 messages posted)
I have a question about Getting
Network Neighborhood to recognize newly attached computers:
My dilemma seems very similar to John Watts. I'm attempting to connect five computers
to my home network. Three run '98, two ME. I use one of the ME computers as my shared
internet host. Three of the machines, the ME internet host and two of the '98s, work
fine. The other two, no matter what I do, see only themselves and are not seen by
the other three or each other. Pinging from/to these machines times out. One of
the machines has network diagnostics, and indicates everything to the hub is fine.
Likewise the hub indicators show both problem machines working OK. While I've tried
other variations, currently I have fixed IP address of the 192.168.0.x form. I've
tried removing and reinstalling protocols and devices. I've tried manually setting
things up every way I can think of, but I'm pretty much a network novice... Suggestions?
[Reply or follow-up to this message]
|
re: Question about 'Getting Network Neighborhood to recognize newly attached computers'
Sunday, February 3, 2002 at 2:16 am
Posted by Sarah
(3 messages posted)
I also had that problem. I suggest first of all uninstalling the communications folder
and network card(s) to restore default settings.
Below is what i did to configure my network + internet sharing.
First thing you need to have the networking interface cards configured in each system,
using the proper drivers etc.
-You also should always check the physical connection to each device, such as the
networking cable in the back of the computer in the network card, and in the actual
physical hub. Physical examination of the network cabling is also something that
shouldn’t be looked past.
-Once you have the physical work done then you switch to software mode. You want
to assign each of the computers on the network an IP address. This idea is called
assigning them static IP addresses. Meaning they do not change, where as Dynamic
IP addresses do change. But this requires a DHCP (Dynamic Host Control Protocol)
Server, that hands out IP Addresses each time a person “logs” onto the network.
With the absence of a DHCP server you need to assign static IP addresses, and make
sure the IP addressing scheme doesn’t have any conflicts, such as the multiple use
of the same IP address.
-Sometimes for things to work correctly, you will also need to configure a Default
Gateway for each client computer, DHCP can also hand out this extra information,
but since there is no DHCP server the information isn’t handed out and you need to
manually set these settings. The Default Gateway should be the computer running
ICS, you may also need to state a DNS server, which is also the computer running
ICS.
-ICS is actually a cut down version of a few different servers; this is why you need
to specify the same IP for all these settings. By default the ICS server sets it’s
IP address to 192.168.0.1, but you can force it to other IP addresses, this will
only complicate remembering it and is not recommended.
*Tips – Ping each network device using the ping command and don’t forget to use the
Ipconfig /all command to view network settings at each node.
*Sometimes it will take a while for computers to register on the network with other
computers, so this may be confusing as well,
I recommend installing the Microsoft NetBeui Protocol, because it’s small and optimized
for local area networks as far as for connecting to local machines.
.. Hope it helps!!!
[Reply or follow-up to this message]
|
