HELP! Win2k Server sees nothing on Internal NIC!

[Robert Paris]

I have a server (windows 2000) that's connected through a NIC to DSL.
There's another NIC in the server that's connected to a Dell PowerConnect
2016 Switch (which as I understand it is basically a Hub with buffering).

I have set up NAT/DHCP on the server.

For some reason, the internal NIC card has 0 packets received even though I
have a laptop (win2k pro) that is also connected to the PowerConnect switch
and is configured to obtain IP automatically.

I don't think it's the switch as I also have a Lynksys 5-port hub (which
I've used successfully in the past), and with that, there's also 0 packets
received.

Also the laptop is obviously not finding the server as it keeps getting the
default 169.x.x.x IP.

Does anyone know what might be wrong? What can I do to get the laptop to see
the server?

Thanks!

 

[Paul King]

Ok, what adapter does your DHCP server use when starting?

Ensure that the adapter is the one connected to the PowerConnect

Regards
Paul.

 

[Robert Paris]

I'm not sure. I haven't installed the full DHCP server, but instead have set
up NAT through "Routing and Remote Access". Do I have to install the DHCP
server to get NAT to work properly? I was under the impression that it had
its own internal DHCP server software. If it does, then where in RRAS do I
check for which adapter DHCP is using?

Thanks!

 

[Paul King]

Ok lets start from the beginning.

NAT is used only when you want to add a layer of security to your network.
Normally a DSL router will let you configure your network using NAT and then
you assign your server an internal address.

However, from your message you are using RRAS so in effect this has become
the router between the 2 networks.

DHCP on the other hand is for issuing out internal addresses on your Local
LAN. To check to see how this is configured Open up Administrative Tools >
DHCP Server. This should be able to tell you the address pool it has
allocated and what subnet to issue DHCP requests.

Personally I would strongly suggest that you buy a dedicated DSL Router and
or Firewall and remove the RRAS service from your Win2k server. That way
the Win2k server can be used for DHCP and other applications.

By doing it your way, you are compromising security on your box, unless you
have another server that uses ISA or a firewall product.

Hope this helps
Paul

 

[Robert Paris]

One note: I did (under NAT -> Properties -> Address Assignment), check
"Assign IP Automatically using DHCP." And I chose "192.168.0.0" subnet mask
"255.255.255.0" with an exclude of "192.168.0.1" (which is the server's IP).

Plus, I set the internal NIC to be "Private" and the internet NIC "Public,
connected to internet."

 

[Robert Paris]

Thanks for the reply.

OK, I have only one static IP from my DSL provider and I'm trying to setup
an internal network. So I have a DSL Modem (not router) to the internet, and
my win2k server (with a firewall) acts as the router so the other comp's can
get on the internet.

My problem is: why is my internal NIC seeing no traffic? How can I make it
and the laptop see each other?

Thanks!

 

[Paul King]

Ok, so your network is 192.168.0.0/24 and your Server IP is 192.168.0.1

What happens if you manually assign an IP address to your client machine,
say 192.168.0.10 - can these machines get to the Internet?

Again you need to check to see what adapter your DHCP server is using as it
could be assigned to the one which is your Internet NIC.

Regards
Paul

 

[Paul King]

Ok, here's what I would do....

Start again....

Disable the DSL Nic adapter on your Server. Remove RRAS service and install
DHCP server.

Ensure that you have DHCP working correctly with your laptop. If not then
it could be your adapter, port on the switch, or the cable itself!

If this works then re-enable your 2nd NIC - retest the laptop by doing a
ipconfig /release > ipconfig /renew - if this doesn't work then its a setup
issue with DHCP somewhere.

If it works then reinstall RRAS with NAT.

This would be a process of elimination.....

Regards
Paul

 

[Robert Paris]

YES! Thank you! It appears that DHCP is the problem because setting the
laptop to 192.168.0.3 (static assigned) allows me to ping the server!

OK, I guess I need to figure out the DHCP problem. What's the best way to
walk through that?

Thanks again!!