Archived from groups: comp.sys.ibm.pc.hardware.storage (
More info?)
On Thu, 07 Oct 2004 17:18:30 -0700, John . <john@notme.com> wrote:
>Kenneth <usenet@SPAMLESSsoleassociates.com> wrote:
>
>>On Thu, 07 Oct 2004 12:53:31 -0700, John . <john@notme.com> wrote:
>>
>>>Kenneth <usenet@SPAMLESSsoleassociates.com> wrote:
>>>>Hi Peter,
>>>>
>>>>First, the good news: Neither of the machines in question is wireless.
>>>>They are hard wired and are connected by coax...
>>>>
>>>>Ordinarily, they talk to each other happily using NetBEUI. It was
>>>>suggested to me that I should do these experiments with only TCP/IP
>>>>running, and so have disabled NetBEUI on both boxes.
>>>>
>>>>Now, the surprise:
>>>>
>>>>Running Windows on both machines, they cannot ping one another...
>>>>
>>>>I just get endless time out errors, going both ways.
>>>>
>>>>Though this is a hassle, I do suspect that we are getting closer to
>>>>home on all this.
>>>>
>>>>BTW, the switch through which these are piped is a Linksys EZXS88W.
>>>>
>>>>Because of the ping failures, I think it best to go no further with
>>>>your other steps above.
>>>>
>>>>Sincere thanks,
>>>
>>>Kenneth, you are getting good advice from Peter. I've read all the
>>>threads here and in backup.
>>>
>>>If your two PC's (A & B) are both ONLY using TCPIP, and if the
>>>router/switch is configured for DHCP, you should be able to ping
>>>between the two. If you can't that MUST be fixed first. Don't just
>>>disable NETBEUI by unchecking it, make sure it's not in the network
>>>properties list.
>>>
>>>I would disconnect all other cables from the router/switch except A &
>>>B and concentrate on getting those two to communicate properly with
>>>each other.
>>>
>>>Make sure A and B can browse the other's network neighborhood shares.
>>>Then see if those two can access the Internet via the router.
>>>
>>>Once all that is working, then reboot one of them with Ghost 9, and
>>>see if you can access the other one. In the Windows 2000 Pro PC with
>>>the images on its hard drive, you wilt need have a valid logon
>>>id/password defined for the Ghost user.
>>>
>>>john
>>>
>>
>>Hi John,
>>
>>Thanks for your comments...
>>
>>I did not merely un-check NetBEUI, I "removed" it. But with TCP/IP, I
>>could not ping either box from the other.
>>
>>I have not tried the un-plugging approach as yet, but certainly will.
>>
>>One other question:
>>
>>I assume that to ping successfully, there is no logon issue. Is that
>>correct?
>>
>>When I have more info, I will post here.
>>
>>Sincere thanks, once again,
>
>There is no logon with ping. The only thing that could stop it would
>be router blocking pings, but I doubt it.
>
>If you can't ping between two PC's and get a response, then your
>network is not setup correctly.
>
>If the PC's are physically close to each other you could further
>isolate it by connecting an Ethernet cross-over cable between the two.
>
>Before pinging though, check both PC's with ipconfig /all and compare
>results. They should both have similar ip addresses except last such
>as 192.168.1.100 and 192.168.1.101. Both should have 255.255.255.0
>and both should have gateway address of your router (probably
>192.168.1.1)
>
>(above rule applies to all PC's on your network.)
>
>You should not have to release or renew ip's to get it to work. They
>must both have same workgroup name also.
>
>I think there is a "Setup home network" wizard in Windows 2000. If so
>run this, then reboot.
Hi John,
You may have pointed me in an important direction...
With the remote box running Windows, and the local box running off the
Ghost CD, I unplugged all but those two systems from the switch.
Then, as you suggested, I ran IPCONFIG /all on both.
They both show DHCP: yes
They both show Autoconfig: yes
The IP address are just as you suggest, that is differing by one in
the last field.
The subnet for both is 255.255.255.0
But, the remote (Windows) box displays the Default Gateway as
192.168.1.1 while the local (CD booted) box shows nothing in that
field.
So, that would seem to be telling us that the CD booted local box is
not seeing the router, and thus, not seeing anything else.
What should be my next step?
Sincere thanks,
--
Kenneth
If you email... Please remove the "SPAMLESS."
Facebook
Twitter
Instagram