Groups | Blog | Home
all groups > iis security > december 2005 >

iis security : Internet access breaks after installing IIS 6 on Windows Server 20


RickinPA
12/30/2005 1:37:02 PM
We are setting up a new Windows Server 2003 machine to be used to host our
websites and e-mail service. In setting it up, PRIOR to installing IIS 6, we
had Internet access working. AFTER installing IIS, Internet access no longer
worked - cannot even go to online to microsoft.com. Uninstalling IIS 6 did
not restore Internet access. What setting was modified by the IIS
installation which broke our Internet access, and how do we re-enable it?
Dave
12/31/2005 12:17:27 PM
i just did the same basic thing here and didn't break it. i would guess it
was just a coincidence... do the basic local tests on the stack, ping
yourself, turn iis on and see if you can browse to yourself, check ipconfig
and see if you can ping your gateway and dns servers, turn off firewall and
filtering, etc... then try unistalling the ethernet port and reinstalling
it. install a different card, there is always the spectre of 'infant
mortality' with new hardware... the most likely time for failure is in the
first week or two.

[quoted text, click to view]

Bob
1/2/2006 9:26:19 PM
On Fri, 30 Dec 2005 13:37:02 -0800, "RickinPA"
[quoted text, click to view]

What level of networking ability do you have ? Can you ping 127.0.0.1?
Can you do an NSlookup on DNS names? Can you access web sites by IP
address ? eg. MS is http://207.46.18.30

RickinPA
1/3/2006 7:58:04 AM
I found, after returning to work from the long weekend, that the Internet
access was mysteriously working again! I then did a simple reboot, logged on
as admin, and tried the Internet access again - once again, it did not work.
Cannot access websites by IP address. Could there be something that only
slowly works its way through the LAN and eventually connects up properly? In
particular, I was wondering if IIS installation reconfigured the default
anonymous user such that Internet access was then disabled. We have a
standalone firewall and our own router, if it makes any difference. Windows
built-in firewall is NOT enabled.

My network admin knowledge is extremely limited; my niche is website
programming, but I was asked to install IIS 6 and get the websites working. I
was able to do this under IIS 5 on the old Windows 2000 server, but have not
been able to reprise that success. The bar of technical knowledge seems to
have been significantly raised under Windows Server 2003 and IIS 6!

Rick

[quoted text, click to view]
jeff.nospam NO[at]SPAM zina.com
1/4/2006 4:34:11 AM
There really isn't anything in IIS that should affect this. My guess
is it's not IIS related. But you'll need to test network
connectivity, check routing, NAT, firewalls, IP rnages, etc. to see
where there may be an error. Not something you can be taught in a
newsgroup post.

Jeff

On Tue, 3 Jan 2006 07:58:04 -0800, "RickinPA"
[quoted text, click to view]
Brian Womack
1/11/2006 10:02:07 PM
This is likely the curse of a Windows Update patch. The same thing
happens to me when I apply the patches since SP1 on my Windows 2003
server. A repair makes the problem go away.

I do know networking in and out, and still have not come up with an
answer to this other than repair and disable windows update. But
clearly, this is not how I want to keep things for long from a security
perspective.

Brian

In article <43bf4ff3.1615246281@msnews.microsoft.com>,
jeff.nospam@zina.com says...
[quoted text, click to view]
AddThis Social Bookmark Button