Windows 2003 server only listening on local network ports?

You'll have to excuse me if this is very obvious. I'm not a 2003 Server
admin/expert.

I have a situation where we have a Windows 2003 server running IIS. It also
runs VNC. And not much else. Anyone on the internal network can connect to
both VNC and web server fine.

We have firewall rules in place to port forward to 192.168.10.100 (2003
Server's IP) any VNC and web request from the "outside world"

The only problem is we receive no response from the server. If I swap the
server for another one running at the same IP, then people on the outside
can connect to the VNC and web servers. If we change the firewall rules so
they point to an old NT box with a different IP address running VNC and a
web server it works fine.

So the problem appears to be any requests NOT on the internal LAN IP range
are being blocked/ignored by this 2003 Server. However it does not have the
Windows firewall activated. It doesn't have a 3rd party firewall.

Does 2003 have some new security model that by default will not "trust" any
IP packets not on the same subnet as it and hence its failing to respond to
requests from the outside? If so, where the hell do I find the switch for
this behaviour?

Note its not just IIS that is displaying this behaviour, its something
"global" on the server as more than one service is affected.

Yours,

Tearing his hair out.

Clive.

Check the server for packet filters, especially if you have configured RRAS.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"Bonge Boo!" <(E-Mail Removed)> wrote in message
news:BD52C44C.7A4CD%(E-Mail Removed)...
> You'll have to excuse me if this is very obvious. I'm not a 2003 Server
> admin/expert.
>
> I have a situation where we have a Windows 2003 server running IIS. It
also
> runs VNC. And not much else. Anyone on the internal network can connect to
> both VNC and web server fine.
>
> We have firewall rules in place to port forward to 192.168.10.100 (2003
> Server's IP) any VNC and web request from the "outside world"
>
> The only problem is we receive no response from the server. If I swap the
> server for another one running at the same IP, then people on the outside
> can connect to the VNC and web servers. If we change the firewall rules so
> they point to an old NT box with a different IP address running VNC and a
> web server it works fine.
>
> So the problem appears to be any requests NOT on the internal LAN IP range
> are being blocked/ignored by this 2003 Server. However it does not have
the
> Windows firewall activated. It doesn't have a 3rd party firewall.
>
> Does 2003 have some new security model that by default will not "trust"
any
> IP packets not on the same subnet as it and hence its failing to respond
to
> requests from the outside? If so, where the hell do I find the switch for
> this behaviour?
>
> Note its not just IIS that is displaying this behaviour, its something
> "global" on the server as more than one service is affected.
>
> Yours,
>
> Tearing his hair out.
>
> Clive.
>

On 25/8/04 11:20 pm, in article (E-Mail Removed), "Doug
Sherman [MVP]" <(E-Mail Removed)> wrote:

> Check the server for packet filters, especially if you have configured RRAS.

No packet filtering in place....

Hi Bonge,

Have you had any result yet? I'm having the exact same problem. Even
tried a different router with no luck.


> > Check the server for packet filters, especially if you have configured RRAS.
>
> No packet filtering in place....