Win2003 Server R2 CONFUSION

I've installed two virtual server guest machines using Windows Server 2003
Release 2. One as an IIS server and one as an Exchange 2003 server.
Something ODD is going on with these two. In the case of the IIS machine,
clients outside of the local subnet (but still part of the internal network)
cannot access the web pages UNLESS Inet Explorer is configured with proxy
server settings to our ISA Server which is on the same subnet.

In the case of the Exchange server, clients on a different subnet cannot
access their mailboxes.

Does this start to ring anyone's bell? I have been on the phone with MSOFT
for three hours today with no progress yet.

To me it seems like the W2K3 "R2" servers are blocking access by anyone
outside the local subnet. This may be by design, but I have no clue on how
to undo that if it is.

Hi Jeff,

Please try using W2k3 SP1 without R2. R2 doesn't make any changes to the Sp1
core. It only add new features, which I don't think will contribute to this
issue.

I'm cross postin this questoin to IIS and Exchange NG so people over there
can respond to it.

--
Jabez Gan [MVP]
Microsoft MVP: Windows Server
http://www.blizhosting.com
MSBLOG: http://msblog.resdev.net


"Jeff Hofstetter" <(E-Mail Removed)> wrote in message
news:%23$(E-Mail Removed)...
> I've installed two virtual server guest machines using Windows Server 2003
> Release 2. One as an IIS server and one as an Exchange 2003 server.
> Something ODD is going on with these two. In the case of the IIS machine,
> clients outside of the local subnet (but still part of the internal
> network) cannot access the web pages UNLESS Inet Explorer is configured
> with proxy server settings to our ISA Server which is on the same subnet.
>
> In the case of the Exchange server, clients on a different subnet cannot
> access their mailboxes.
>
> Does this start to ring anyone's bell? I have been on the phone with MSOFT
> for three hours today with no progress yet.
>
> To me it seems like the W2K3 "R2" servers are blocking access by anyone
> outside the local subnet. This may be by design, but I have no clue on how
> to undo that if it is.
>
>
>

May want to post to microsoft.public.virtualserver

I haven't heard of WS03R2 having such blolcking behavior, but people have
experienced similar networking/access blocking behavior with Virtual Server
2005 Guest VMs either inbound or outbound. I haven't been curious enough to
look into why - I've never had such problems from Guest VMs so it all looks
working to me, so I have no basis to compare.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//

"Jabez Gan [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Jeff,
>
> Please try using W2k3 SP1 without R2. R2 doesn't make any changes to the
> Sp1 core. It only add new features, which I don't think will contribute to
> this issue.
>
> I'm cross postin this questoin to IIS and Exchange NG so people over there
> can respond to it.
>
> --
> Jabez Gan [MVP]
> Microsoft MVP: Windows Server
> http://www.blizhosting.com
> MSBLOG: http://msblog.resdev.net
>
>
> "Jeff Hofstetter" <(E-Mail Removed)> wrote in message
> news:%23$(E-Mail Removed)...
>> I've installed two virtual server guest machines using Windows Server
>> 2003 Release 2. One as an IIS server and one as an Exchange 2003 server.
>> Something ODD is going on with these two. In the case of the IIS machine,
>> clients outside of the local subnet (but still part of the internal
>> network) cannot access the web pages UNLESS Inet Explorer is configured
>> with proxy server settings to our ISA Server which is on the same subnet.
>>
>> In the case of the Exchange server, clients on a different subnet cannot
>> access their mailboxes.
>>
>> Does this start to ring anyone's bell? I have been on the phone with
>> MSOFT for three hours today with no progress yet.
>>
>> To me it seems like the W2K3 "R2" servers are blocking access by anyone
>> outside the local subnet. This may be by design, but I have no clue on
>> how to undo that if it is.
>>
>>
>>
>
>