There are two problems here - routing and DNS.
1. Routing. Because your LAN clients are in a different subnet from the
cable router, the cable router does not know how to reach them. It needs
extra routing so it will forward traffic for the "local" subnet to the 2003
server, which does have an interface in that subnet (and can deliver it).
The only exception to this is if the 2003 server is doing NAT for the
"private" LAN. NAT solves the problem because all traffic reaching the cable
router is using the server's "public" IP, which is in the same subnet as the
router.
2. DNS. The LAN clients will be set to use the local DNS server. To resolve
"foreign" names, you will need to modify the DNS server so that it forwards
to a public DNS server (such as the one at your ISP).
"John Dickson" <(E-Mail Removed)> wrote in message
news:6c3201c42f3a$6f62efa0$(E-Mail Removed)...
> I have a dual-homed 2003 server that I'm setting up at
> home on my cable connection. I have the first NIC pulling
> a DHCP address from the cable modem, and the second NIC
> running back to a hub for the other machines. I have set
> the server up using the defaults for a first server. The
> second NIC is now assigned a static IP, and I am running
> DHCP and DNS.
>
> My problem is, when I connect another machine to the
> switch, I get a valid IP address, can check email and log
> into MSN, but cannot browse, or connect Yahoo Messenger.
>
> The only time I've seen something like this was while
> using an old Linksys router, and had some ports mapped to
> specific machines, which would prevent some services from
> running onother machines. Is this similar? Are there
> some firewall settings that I'm missing?
>
> Thanks for your help.
|
Similar Threads
Linear Mode
