Sung
Wed Jun 30 02:45:49 CDT 2004
Thanks for such a quick reply.
I can ping the server from the remote network by dns and
netbios name.
Pretty sure that port 80 is open, as the remote office is
able to hit another web server sitting on the same
subnet.
Will take your suggestion and post in a networking
newsgroup.
>-----Original Message-----
>And you are completely sure that port 80 is not closed
somewhere? It sounds
>like that.
>
>Can you ping the server from the remote network? It
could also be that the
>server is not reachable. But in any way, it does not
sound like a problem
>with IIS, more of a problem with the network. Maybe you
should try a
>networking newsgroup?
>
>microsoft.public.windows.server.networking
>
>--
>Regards,
>Kristofer Gafvert - IIS MVP
>
http://www.ilopia.com - When you need help!
>
>
>"Sung Duc" <anonymous@discussions.microsoft.com> wrote
in message
>news:2327c01c45e57$9ff9a400$a301280a@phx.gbl...
>> We have an issue here, where users on the same subnet
as
>> the IIS server are able to connect to it without any
>> problems. However, users on remote subnets are not able
>> to do so?
>>
>> The strange thing with this is, doing a port scan on
the
>> IIS server remotely, port 80 does not appear. While
doing
>> a port scan on the IIS server on the same subnet, port
80
>> does appear.
>>
>> Our router consultants have assured us that there are
no
>> ACLs preventing http traffic.
>>
>> We are running Windows 2003 IIS 6.0. There are no
>> firewalls to consider in this issue. IIS 6.0 is
>> permitting all traffic at this stage, so we are not
>> limiting access to specific subnets only, and anonymous
>> access is enabled.
>>
>> Has anyone experience a similar issue?
>>
>> Sung
>>
>
>
>.
>