Windows 2000 adv server and linksys router networking problem

  • Thread starter Thread starter Jon Lauer
  • Start date Start date
J

Jon Lauer

I have a windows 2k server with 2 nics placed in between my cable
modem and a linksys wrt54g wireless router. On the other side of the
router are 3 workstations. I have dhcp enabled on the server and on
the router. The server is connected to the uplink port on the router.
I have internet access on the server as it is directly connected to
the cable modem. The internal ip of the server is 192.168.1.1 and it
assigns the router 192.168.1.100 the router then assigns the 3
machines their respective ip's and the ip of the router (192.168.1.2)
as the gateway. I can ping the router from any of the machines, and
vice versa but i can't ping the server from the router and i can't
ping the router from the server. the router's gateway is that of the
server (192.168.1.1). What am i doing wrong here? thx
 
Normally in this configuration you would run the
router as an access point and leave the WAN port
disconnected. I can't really think of a plausible scenario
in which you would want to put a router in the path
between the workstations and server.

Plugging the server in on the LAN side will put the
workstations (wired and wireless) on the same network as the
server and should solve your problems. Note that you still
need to enable NAT routing on the server if you want to allow
the workstations to access the broadband connection.

The alternative -- and more common -- approach, is to put
the router in between the cable modem and the LAN, so that
all the workstations and the server connect through it and thus
to the broadband line. The server only needs 1 NIC for this.
There are reasons to do it this way vs. the other, but without knowing
more about what you're trying to do, I can't say which is correct
in your case.

Steve Duff, MCSE
Ergodic Systems, Inc.
 
I would suggest you're using the first nic to connect to a hub/switch, and
the second to your router which connects to the cablemodem.
The internal nic would have a blank gateway, external nic would be in a
different IP-range. DNS on both internal and external nic should *only*
point to your server-IP. On the external nic only TCP/IP should be bound.
In DHCP-server add options 003, 006 and 015 to Scope options, and if you
have W9x/ME/NT4-clients also WINS-server and options 044 and 046 (0x8).
In DNS-server you put the ISP-DNS-numbers in the tab forwarders.
DHCP should only be running on your server.
Check the bindingorder and make sure the internal nic is on top.

The nics of the clients should be set to obtain an IP and DNS automatically
from your DHCP-server.

Marina
 
Jon...

IMHO, Steve has the best suggestion.

Modem > Router > LAN

Only run one DHCP server. A DHCP client cannot choose which DHCP server
they want to request an address from. They just send out a DHCP request of
0.0.0.0 and the DHCP server, if successful, responds with an available
address from its pool.

I prefer to run my DHCP on my router but I'm sure there are those that will
argue it is better to run it on the server. I'm not running only Windows
computers so... [I can feel oncoming objections]

I have a setup similar to yours except my router is a Belkin 54G Wireless. I
have some workstations connected to the built-in switch on the router and
some connected to a switch which connects to the router and of course, my
wireless connections connect to the router.

My setup:
modem > router > switch/PCs/wireless connections

I run AD on my server and it is also running a web server with hosted DDNS
(dynamic). This is similar to hosting my web site externally except the
DDNS points a public address to my dynamic one and I run the DDNS client
service to keep it updated.

My external domain: domain.com
My internal domain: internal.domain.com

My server is running DNS and its network settings set the primary DNS to
itself, it's private address, 192.168.0.1.
My workstations point their primary DNS to 192.168.0.1.
There are NO entries pointing to the ISPs DNS servers. You would only need
that in your DNS server setup if you were adding a forwarder, which I do not
have.
Their suffix search order is:
internal.domain.com
domain.com

This means if I'm looking for 'host', it appends host.internal.domain.com
and if that fails, it puts host.domain.com.

I removed the root entry "." in the forward lookup of my DNS server setup so
external (public) DNS queries will be routed to the Internet and the root
hint servers will be used to provide addressing.

I'm also running Exchange Enterprise Server 2000 on this box and all my
addresses have both internal and external email addresses:

(e-mail address removed)
(e-mail address removed)

The first one is the default so when I send email to public users, my
reply-to address will be @domain.com and not @internal.domain.com. The
latter does not exist on the Internet.

Some people prefer, on SOHO networks, to route through the server. I see
this as a waste of resources and unnecessary overhead.


I have a windows 2k server with 2 nics placed in between my cable
modem and a linksys wrt54g wireless router. On the other side of the
router are 3 workstations. I have dhcp enabled on the server and on
the router. The server is connected to the uplink port on the router.
I have internet access on the server as it is directly connected to
the cable modem. The internal ip of the server is 192.168.1.1 and it
assigns the router 192.168.1.100 the router then assigns the 3
machines their respective ip's and the ip of the router (192.168.1.2)
as the gateway. I can ping the router from any of the machines, and
vice versa but i can't ping the server from the router and i can't
ping the router from the server. the router's gateway is that of the
server (192.168.1.1). What am i doing wrong here? thx
 
Back
Top