OK

standard network check list (sorry if some items sound silly, but please check
them anyway).

1. All devices have power - PCs, Switch.

2. Connection light lit on all NICs and switch ports that are in use.

3. If the switch indicates speed, note, which ports are at which speed.

4. Check the spec of the switch - is it a 10/100 FDX N-Way autosensensing switch
on all ports ?
    If not adjust settings to suit on the NICs - eg only HDX not FDX, only 10Mb/s
not 100 Mb/s.

5. Is this a "managed" switch - if so ensure that all ports that
you wish to use
are enabled and set to the speed / duplex mode, that you need.  I suspect this is
an unmanaged switch, so you can do anything.

6. Check IP configuration on problem system (s).  Do these have static IP
addresses or do you use DHCP. If Static, make sure you don't have a duplicate IP
assignment. If DHCP, is the DHCP server working and on the same IP subnet ? What
subnet mask is in use on the systems - they all need to be using the same subnet
mask, be in the same range of IP addresses and all be set to the same default
router or gateway. If you are using DHCP, this should all be taken care of for you
automatically.

7. On the problem PC(s) can you ping 127.0.0.1 (loopback address), can you also
ping the address of the NIC. If either of these don't work, you have a problem
within the PC. This could be a faulty NIC card, an incorrect driver or
configuration.  As you say using a cross over cable works, I don't think you will
have a problem here, but please check anyway.

If all of the above doesn't bring up something, I'd have to say again that the
problem lies in the switches that you are trying to use - perhaps these do need
configuration ? Can you give me the exact make and model numbers and I'll see if I
can find anything about them.

Cheers/2

Ed.

Michael Oujesky wrote:

> >> Been trying to work through this for the last couple of weeks
and finally
> >> need some assistance.
> >>
> >> Trying to upgrade my peer-to-peer networking from 10base-T/hub to
> >> 100base-T/router.
> >>
> >> Peer between Connect, Win95, and Win98 working fine before starting the
> >> changes and it still works fine with crossover cable between
two systems.
> >> The Win* machines already had 10/100 capable interfaces, so no changes
> >> there.  Only changes implemented were to the OS/2 machine.  Initially
> >> installed a 3C597, but no connectivity going through the DLink DI-524.
> >> Changed to a Kensington KNE12oTX on the chance that the 3C597's lack of
> >> auto-negotiation might be the problem.
> >>
> >> PING does not see the other machine from either Connect or
Win95.  Activity
> >> leds on the router/switch indicate that when the WIN95 machine pings
> >> Connect, the router/switch is not accessing the Connect machine.
> >>
> >> Same results  when trying a DLink DSS-5+.
>
> >If your reference to a Switch/router refers to a router with a
built-in N-Way
> >10/100 switch, then you should be able to simply remove the hub and plug the
> >cables into the switch ports. Everything should work. OK, some parts (or
> all of
> >the network) may be working at only 10 Mb/s but this is the first stage. If
> >this doesn't work, even at 10Mb/s - take the router/switch back to the
> retailer
> >and demand your money back or a replacment unit as it's not working.
>
> Thanks for the suggestions, but as I stated above, the problem persists
> across two different models of router/switch devices.
>
> >Presuming everything is working, but not at 100Mb/s as you wish, go
> through all
> >PCs NICs and set them to to 100 Mb/s FDX, don't have them set to auto.
>
> Done. Same results as before.
>
> >Restart everything (including the switch) and see how you stand. If you find
> >one device not communicating, then you need to change it's network
> >cable (I presume you're using at least Cat5e cabling ??)
>
> Done.  Upgraded to CAT-6 patch cords with no difference in failures.
>
> >and if that doesn't work, try changing the port on the switch it
is connected
> >into
>
> Done. No change in failures.
>
> >and last of all the NIC itself.
>
> The NICs are fine - they work with the crossover cable and hub without a
> problem.
>
> Now what?
>
> Thanks again.
>
>
> Yahoo! Groups Links
>
>
>
>



 
Yahoo! Groups Links

 To visit your group on the web, go to:
    http://groups.yahoo.com/group/os2hardware/

 To unsubscribe from this group, send an email to:
    os2hardware-unsubscribe{at}yahoogroups.com

 Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 




---