Topic: W2K & SME Incompatibilty?

[Scott Rogers]

I have SME 5.1.2 installed as a gateway and server on an old pentium 150 Mhz PC and I'm using a D-Link 4 port server NIC (DFE-570TX) which is based on the Tulip chips.  SME has no problem recognizing and loading drivers for the Tulip NIC.  The server is connected on one of the NIC ports to my cable modem using a straight through CAT-5 cable and another port is connected to a PC running W2k Pro (with SP2) using a CAT-5 crossover cable.  The server has Internet connectivity, but the other PC running W2k Pro on the LAN does not.  Here's my ipconfig and ping response data below.  Note the Autoconfiguration IP address is not in the DHCP range assigned by the server (192.168.10.65 to 192.168.10.250).  Can anybody tell me what the problem may be?  Thanks,  Scott.

D:\>ipconfig

Windows 2000 IP Configuration

Ethernet adapter Local Area Connection 2:

        Connection-specific DNS Suffix  . :
        Autoconfiguration IP Address. . . : 169.254.71.110
        Subnet Mask . . . . . . . . . . . : 255.255.0.0
        Default Gateway . . . . . . . . . :

D:\>ping 192.168.10.1

Pinging 192.168.10.1 with 32 bytes of data:

Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.

Ping statistics for 192.168.10.1:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum =  0ms, Average =  0ms

[Schultz]

Is your 4-port NIC a hub or does it act as 4 seperate NIC's?

I've used something similar in the past that was basically a NIC with a built-in hub.  Try using a seperate NIC altogether for your internal network.

[Uwe Schreiber]

your Win2000 machine isn't getting an IP-Adress from the server.

The IP-Adress 169.254.71.110 is assigned by Windows 2000 automatically, because it can't find any DHCP-Server which could give him an IP-Adress.

It's the wrong IP-/Subnetmask-combination for your network

You should first of all try a static IP-Adress (e.g. 192.168.10.10/255.255.255.0, assuming, that is your correct network mask on your server) and repeat your ping to 192.168.10.1 (i think that is your SME-Server)

after that you should ping your Win2000 machine from within the console of your SME-Server

[Scott Rogers]

If the 4 port NIC is acting as a HUB, this would work better for my LAN and I'll try a single port NIC on the WAN side.  I'll post with results.  Thanks Schultz!

[Scott Rogers]

Thanks Uwe.  I will try this if I'm still having this problem after I've tried a single port NIC on my WAN side in case my 4 port NIC is acting as a hub.  See response from Shultz.

[Kelvin]

Hi Scott,

The D-Link 4 port server card is NOT a hub. SME would normally pick it up as 4 network cards. This server NIC's strength (at least in a Win-type PC) is that the ports can be configured for redundancy or load balancing. Additionally, for it to work correctly, the NIC should be connected to an intelligent switch as well.

Kelvin

[Scott Rogers]

I'm sure this card works great in a Windows NT or 2000 server, but I can't get SME to recognize the four ports (really NICs) on the D-Link four port server card nor can I get both connectivity to the Internet via the cable modem and connectivity on the LAN with with just two ports connected.  I can only get one side or the other working depending on how I configure.  Even using a separate single port NIC for the WAN does not work.  Moreover, I've never been able to get SME to recognize and work with more than two NICs in separate PCI or ISA slots, even with all the NICs connected to running clients and one to my cable modem.