Re: Windows 2003 with 2 NICs

Thanks for your reply, Doug. I'll double-double check the points you've
raised!
>From the webserver I can ping its external interface - I'm using
172.16.255.253, the router is 172.16.255.254, the internal interface is
192.168.0.2, both with masks of 255.255.255.0.

What sort of inbuilt firewall protection does Windows erver 2003 have out of
the box - I'm wondering if the box is simply not letting any packets leave
the external interface?

Thanks again.


"Doug Sherman [MVP]" <dsherman@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:u5$rfXeHGHA.3984@xxxxxxxxxxxxxxxxxxxxxxx
> Lots of possibilities, but the most likely/easily overlooked possibilities
> are:
>
> 1. Wrong subnet mask or otherwise misconfigured IP on NIC connected to
> router.
>
> 2. Both NICs on same subnet.
>
> 3. If the machine points to itself for DNS, forwarders to a public DNS
> server are not properly configured.
>
> #1 and 2 are the only ones that would prevent you from pinging the router.
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
> "N. Hughes" <quadrantcomputerNOSPAM@xxxxxxxxxxx> wrote in message
> news:#iy9zaZHGHA.3100@xxxxxxxxxxxxxxxxxxxxxxx
>> Noted an earlier thread on this from Alan Owen but not sure if we have
>> the
>> same problem.
>>
>> We are trying to set up a Windows 2003 Server box as a public web server.
>> The box is set up as a member server with no AD, but it does have DNS and
> 2
>> NICs, both with manually set IPs in different subnets. The public NIC
>> connects to a router/firewall, the internal NIC to a small switch - there
> is
>> only one workstation connected, used for testing.
>>
>> Multiple web sites have been loaded using host headers and can be
>> accessed
>> by the workstation fine. Problem is, we can't get onto the 'net! The
>> physical 'net connection is fine since if we put another workstation on
> the
>> router/firewall, it works. However, our box can't even ping the router,
> so
>> we suspect that we missed a basic step somewhere!
>>
>> One clue - the box used to have ISA 2000 on it but this was recently
>> uninstalled. I gather that when ISA was working, we could access the
>> 'net...
>>
>> Appreciate any ideas, thanks!
>>
>>
>
>


.

Relevant Pages

  • Re: Urgent! New router and big disaster
    ... NIC, you need to specify an external DNS server for DNS, instead of the ... Both NICs should point to his internal IP for DNS. ... forward ports to it reliably in the router. ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... No Phantom NICs as far as I can see. ... that it can not find the server. ... Configure your Router as an Eithernet Bridge. ... Once you have this then configure the Routers Firewall and Port ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... No Phantom NICs as far as I can see. ... that it can not find the server. ... Configure your Router as an Eithernet Bridge. ... Once you have this then configure the Routers Firewall and Port ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... laptop plugged into port on DSL router. ... service, e-mail, and RWW is available to all users on the network. ... The server is a SBS2003 SP1 Standard box without ISA, ... of the two NICs by clicking the Advanced tabs, it won't open that box, ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... The server is a SBS2003 SP1 Standard box without ISA, ... the two NICs by clicking the Advanced tabs, it won't open that box, and ... program or service is running that might use the network address translation ... Is the Modem also your Router? ...
    (microsoft.public.windows.server.sbs)
Quantcast