|
Home > Archive > IIS Server > July 2005 > Why will IIS work with localhost, but not with IP address?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Why will IIS work with localhost, but not with IP address?
|
|
|
| We run Windows XP pro with IIS 5.1. We have always been able to access
our default web site via either localhost or the router's IP address.
Now, all of a sudden, I get nothing with the IP address, but the
localhost still works. I can ping the IP address. I can telnet the IP
address. I just can't see IIS with the IP. I tried turning off the
Windows firewall. I tried bypassing the router, hooking the PC
directly to the DSL modem. Nothing matters. IIS had worked forever. We
didn't install or reconfigure anything. But I do think Windows Update
may have run a few times. A Netstat shows this line for port 80:
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
Since I've never had to look at netstat before, I'm not sure whether
this is right. Can anyone help? Are there any diagnostics that I can
run?
Thanks.
| |
| Ken Schaefer 2005-06-08, 7:48 am |
| Using the router's IP address relies on the router routing the port 80
packets back to your local box.
When your machine is connected to the router, it should have an internal,
private, non-routable IP address. You can find out what this is by opening a
command prompt and typing in: ipconfig.exe
Typically these addresses start with 192.168...
If you type that into your browser instead of your public IP address, can
you access IIS?
Cheers
Ken
--
IIS Blog: www.adopenstatic.com/cs/blogs/ken/
Web: www.adopenstatic.com
"Joe" <joewasik@msn.com> wrote in message
news:1118217897.496905.188310@g49g2000cwa.googlegroups.com...
: We run Windows XP pro with IIS 5.1. We have always been able to access
: our default web site via either localhost or the router's IP address.
: Now, all of a sudden, I get nothing with the IP address, but the
: localhost still works. I can ping the IP address. I can telnet the IP
: address. I just can't see IIS with the IP. I tried turning off the
: Windows firewall. I tried bypassing the router, hooking the PC
: directly to the DSL modem. Nothing matters. IIS had worked forever. We
: didn't install or reconfigure anything. But I do think Windows Update
: may have run a few times. A Netstat shows this line for port 80:
: TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
: Since I've never had to look at netstat before, I'm not sure whether
: this is right. Can anyone help? Are there any diagnostics that I can
: run?
: Thanks.
:
| |
|
| not much help - but i have the same issue in reverse - localhost no longer
works - only the ip works - this was after sp2.
"Joe" <joewasik@msn.com> wrote in message
news:1118217897.496905.188310@g49g2000cwa.googlegroups.com...
> We run Windows XP pro with IIS 5.1. We have always been able to access
> our default web site via either localhost or the router's IP address.
> Now, all of a sudden, I get nothing with the IP address, but the
> localhost still works. I can ping the IP address. I can telnet the IP
> address. I just can't see IIS with the IP. I tried turning off the
> Windows firewall. I tried bypassing the router, hooking the PC
> directly to the DSL modem. Nothing matters. IIS had worked forever. We
> didn't install or reconfigure anything. But I do think Windows Update
> may have run a few times. A Netstat shows this line for port 80:
> TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
> Since I've never had to look at netstat before, I'm not sure whether
> this is right. Can anyone help? Are there any diagnostics that I can
> run?
> Thanks.
>
| |
|
| That internal IP address is fixed, not a DHCP address. It is
192.168.1.240. The router had to be told which computer to which to
route HTTP traffic. And no, that address not does work. I get an
Action Canceled error when going there. Firefox reports a Connection
Refused".
| |
|
| is the ipaddress bound to the site? Are you running all unnasigned, or have
you perhaps added a hostname entry?
"Joe" <joewasik@msn.com> wrote in message
news:1118217897.496905.188310@g49g2000cwa.googlegroups.com...
> We run Windows XP pro with IIS 5.1. We have always been able to access
> our default web site via either localhost or the router's IP address.
> Now, all of a sudden, I get nothing with the IP address, but the
> localhost still works. I can ping the IP address. I can telnet the IP
> address. I just can't see IIS with the IP. I tried turning off the
> Windows firewall. I tried bypassing the router, hooking the PC
> directly to the DSL modem. Nothing matters. IIS had worked forever. We
> didn't install or reconfigure anything. But I do think Windows Update
> may have run a few times. A Netstat shows this line for port 80:
> TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
> Since I've never had to look at netstat before, I'm not sure whether
> this is right. Can anyone help? Are there any diagnostics that I can
> run?
> Thanks.
>
| |
| David Wang [Msft] 2005-06-08, 5:58 pm |
| Your situation (localhost does not work) is likely due to a security change
in XPSP2. There is a KB describing it.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Jason" <microsoft@anywhere.com> wrote in message
news:e3izo8AbFHA.1384@TK2MSFTNGP09.phx.gbl...
not much help - but i have the same issue in reverse - localhost no longer
works - only the ip works - this was after sp2.
"Joe" <joewasik@msn.com> wrote in message
news:1118217897.496905.188310@g49g2000cwa.googlegroups.com...
> We run Windows XP pro with IIS 5.1. We have always been able to access
> our default web site via either localhost or the router's IP address.
> Now, all of a sudden, I get nothing with the IP address, but the
> localhost still works. I can ping the IP address. I can telnet the IP
> address. I just can't see IIS with the IP. I tried turning off the
> Windows firewall. I tried bypassing the router, hooking the PC
> directly to the DSL modem. Nothing matters. IIS had worked forever. We
> didn't install or reconfigure anything. But I do think Windows Update
> may have run a few times. A Netstat shows this line for port 80:
> TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
> Since I've never had to look at netstat before, I'm not sure whether
> this is right. Can anyone help? Are there any diagnostics that I can
> run?
> Thanks.
>
| |
|
| With "bound" you're asking me if this IP address is static? Yes, it
is. It even has a real domain name pointing to it, which by the way,
is also not working. An important clue here is that we tried running
without the router and saw the same result. The IIS logs see the
localhost access, but not the IP access. And Windows Updates have
shown up in the Windows folder.
IIS broke once before, a year ago, when installing SP2. I had to
rebuild the machine from scratch to get IIS to work back then. This
time I will not rebuild. I hope that someone can point me to a
solution or a way to diagnose the problem. But in the end, if IIS
won't work. We'll have to install Apache (which is bad since we want to
use ASP.Net).
Thanks though for all of your suggestions.
| |
| Jeff Cochran 2005-06-08, 5:58 pm |
| On 8 Jun 2005 08:05:14 -0700, "Joe" <joewasik@msn.com> wrote:
>That internal IP address is fixed, not a DHCP address. It is
>192.168.1.240. The router had to be told which computer to which to
>route HTTP traffic. And no, that address not does work. I get an
>Action Canceled error when going there. Firefox reports a Connection
>Refused".
Many routers won't let you route out to a public IP and back in to
another private IP. Localhost doesn't go outside the server.
Jeff
| |
|
| Thanks. But as I pointed out before, we already tried removing the
router, then connecting the PC directoy to the DSL modem. It doesn't
help. We also disabled all firewalls and virusscanners. The point is,
IIS used to work. We didn't change a thing -- at least not on purpose.
All of a sudden, no one can get to the web site anymore except locally
using localhost. A netstat seems to say that IIS is listening, but we
can't seem to reach it. Wish I knew what was going on. We run AdAware
and Spybot. Is it possible that these tools blocked IIS? Seems far
fetched, but I grasping at straws here. Isn't there a good diagnostics
tool out there that can show me port 80 traffic?
| |
| Pierre Tramo 2005-06-08, 8:48 pm |
| On 2005-06-08, Joe <joewasik@msn.com> wrote:
>
> Thanks though for all of your suggestions.
Forget about IIS, it sucks. That's my suggestion.
Bye ! Have a good day !
--
Pierre Tramo
J2EE Lead Architect.
| |
|
| Perhaps. I completely re-installed IIS. Had a bunch of headaches
doing that. And it still doesn't work.
Looks like its goodbye IIS, ASP.Net, and maybe even Visual Studio.Net
What a shame.
| |
|
| Is this right ??? Advice will be greatly appreciated.
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:7 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9 0.0.0.0:0 LISTENING
TCP 0.0.0.0:13 0.0.0.0:0 LISTENING
TCP 0.0.0.0:17 0.0.0.0:0 LISTENING
TCP 0.0.0.0:19 0.0.0.0:0 LISTENING
TCP 0.0.0.0:21 0.0.0.0:0 LISTENING
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1111 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2869 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1032 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1048 0.0.0.0:0 LISTENING
TCP 127.0.0.1:5679 0.0.0.0:0 LISTENING
TCP 192.168.1.240:139 0.0.0.0:0 LISTENING
UDP 0.0.0.0:7 *:*
UDP 0.0.0.0:9 *:*
UDP 0.0.0.0:13 *:*
UDP 0.0.0.0:17 *:*
UDP 0.0.0.0:19 *:*
UDP 0.0.0.0:161 *:*
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:1054 *:*
UDP 0.0.0.0:3456 *:*
UDP 0.0.0.0:4500 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1037 *:*
UDP 127.0.0.1:1043 *:*
UDP 127.0.0.1:1900 *:*
UDP 192.168.1.240:123 *:*
UDP 192.168.1.240:137 *:*
UDP 192.168.1.240:138 *:*
UDP 192.168.1.240:520 *:*
UDP 192.168.1.240:1900 *:*
| |
| Jeff Cochran 2005-06-09, 7:49 am |
| On 8 Jun 2005 16:11:11 -0700, "Joe" <joewasik@msn.com> wrote:
>Thanks. But as I pointed out before, we already tried removing the
>router, then connecting the PC directoy to the DSL modem. It doesn't
>help. We also disabled all firewalls and virusscanners. The point is,
>IIS used to work. We didn't change a thing -- at least not on purpose.
> All of a sudden, no one can get to the web site anymore except locally
>using localhost. A netstat seems to say that IIS is listening, but we
>can't seem to reach it. Wish I knew what was going on. We run AdAware
>and Spybot. Is it possible that these tools blocked IIS? Seems far
>fetched, but I grasping at straws here. Isn't there a good diagnostics
>tool out there that can show me port 80 traffic?
Did your ISP start blocking port 80? Have you tried using another
port to test? Have you tried a Telnet to port 80?
Using the DSL modem, does your system get assigned a public IP? Did
you use that IP in your tests? Everything you post shows a
192.168.x.x number is why I ask.
Are you testing with just the IP to eliminate name resolution issues?
Is IIS set to use host headers? Are you answering on all IP's or just
a single one?
Jeff
| |
| Jeff Cochran 2005-06-09, 7:49 am |
| On 9 Jun 2005 01:54:43 -0700, "Joe" <joewasik@msn.com> wrote:
>Perhaps. I completely re-installed IIS. Had a bunch of headaches
>doing that. And it still doesn't work.
>
>Looks like its goodbye IIS, ASP.Net, and maybe even Visual Studio.Net
>
>What a shame.
Especially sincce the problem isn't IIS. If Localhost worked, IIS is
working. Your problem is network communications related, and will
transfer to using any web server software on your system.
Jeff
| |
| John Cesta 2005-06-09, 7:49 am |
| On 9 Jun 2005 00:13:15 GMT, Pierre Tramo <ptramo@gmail.com> wrote:
>On 2005-06-08, Joe <joewasik@msn.com> wrote:
>
>Forget about IIS, it sucks. That's my suggestion.
Oh, that's intelligent. That's my suggestion.
John Cesta
>
>Bye ! Have a good day !
John Cesta
The CPU Checker - Monitors your CPU % while you sleep
LogFileManager - IIS LogFile Management Tool
WebPageChecker - Helps Maintain Server UpTime
DomainReportIt PRO - Helps Rebuild IIS
http://www.serverautomationtools.com
| |
|
| Thanks for your interest. I really appreciate your input. The answers
to your questions are: (1) Is my ISP blocking port 80 -- I don't know
for sure (2) Yes, I tried using port 81 with the same bad results. (3)
I have not tried Telnet on port 80. I'm not sure how to listen on port
80 with Telnet. I have tried FTP on port 21. No luck with that either,
so far. (4) We have a static IP address which I have to configure the
PC to use when bypassing the router. (5 & 6) I am trying to reach IIS
both ways, with only an IP address and with IP+header. Neither works.
Attempting to reach the machine via its computer name does not work
either. Only localhost appears to work. (7) We only have one static
IP.
Someone else suggested that this is not an IIS issue. I'm willing to
believe that, but I lack the diagnostics tools to prove that. I
downloaded a TCP monitor from SysInternals. That tool does appear to
say that there is perhaps no incoming TCP. The reliability of this tool
in unknown.
I completely un-installed and re-installed IIS from scratch. No
improvement. And by the way, the re-install fought back. It seems
that XPSP2 has some restrictions. I had this error: ""Setup cannot copy
the file staxmem.dll." and it took this command to fix the problem:
"esentutl /p C:\security\database\secedit.sdb". Something going on
with policies perhaps?
So, We're not giving up. We've put in a lot of hours trying to find
out what's going on.
Thanks again.
| |
| Jeff Cochran 2005-06-10, 2:48 am |
| On 9 Jun 2005 08:41:47 -0700, "Joe" <joewasik@msn.com> wrote:
>Thanks for your interest. I really appreciate your input. The answers
>to your questions are: (1) Is my ISP blocking port 80 -- I don't know
>for sure (2) Yes, I tried using port 81 with the same bad results. (3)
>I have not tried Telnet on port 80. I'm not sure how to listen on port
>80 with Telnet. I have tried FTP on port 21. No luck with that either,
>so far. (4) We have a static IP address which I have to configure the
>PC to use when bypassing the router. (5 & 6) I am trying to reach IIS
>both ways, with only an IP address and with IP+header. Neither works.
>Attempting to reach the machine via its computer name does not work
>either. Only localhost appears to work. (7) We only have one static
>IP.
Okay, if none of these work there is definitely something blocking
communication. Firewall, router issues, address translation,
something.
For telnet, you just need IIS running. From a remote system, ata
command pronpt type:
Telnet {IP_Address} {Port}
Use the external IP and port 80. You should get a response back.
>Someone else suggested that this is not an IIS issue. I'm willing to
>believe that, but I lack the diagnostics tools to prove that.
Sure you do. You even stated it. Localhost works. That means IIS is
working. The only possible way IIS could be involved is if you set
your site to only answer on 127.0.0.1, or you use host headers and the
only header you entered is "localhost."
>downloaded a TCP monitor from SysInternals. That tool does appear to
>say that there is perhaps no incoming TCP. The reliability of this tool
>in unknown.
>I completely un-installed and re-installed IIS from scratch. No
>improvement. And by the way, the re-install fought back. It seems
>that XPSP2 has some restrictions. I had this error: ""Setup cannot copy
>the file staxmem.dll." and it took this command to fix the problem:
>"esentutl /p C:\security\database\secedit.sdb". Something going on
>with policies perhaps?
>
>So, We're not giving up. We've put in a lot of hours trying to find
>out what's going on.
Get a second system, attach it to this one through a hub, disconnect
your internet cable connection. Make sure the systems have basic IP
communication, can PING, etc. Test from that system. That will tell
you if the issue is the server system or somewhere outside it.
Jeff
| |
|
| Thanks for your notes. At this point I think I'm going to have to find
someone smarter than me to come and examine this system. Your
suggestion of hooking up two computers is probably a good one but
beyond my capabilities. I did find a port sniffer to have closer look
at what is going on. From a second computer I tried to access IIS on
the problem computer. The port sniffer saw 3 incoming packets. It
identified them as http packets on port 80. The sniffer showed 3 acks
going back. All six packets had a zero data length. So it seems that
no firewall or ISP is blocking incoming traffic. I did get Telnet to
work properly, but on its own default port, not 80. So Telnet is
getting through everything and working. I may still try and install
Apache as an experiment, and if by chance it works, as a replacement
for IIS.
| |
| ProMaker 2005-06-10, 5:56 pm |
| Try hosting your site on port 8080 as port 80 sometimes gets blocked by
internet browsers, antivirus updaters, etc.
"Joe" <joewasik@msn.com> wrote in message
news:1118217897.496905.188310@g49g2000cwa.googlegroups.com...
> We run Windows XP pro with IIS 5.1. We have always been able to access
> our default web site via either localhost or the router's IP address.
> Now, all of a sudden, I get nothing with the IP address, but the
> localhost still works. I can ping the IP address. I can telnet the IP
> address. I just can't see IIS with the IP. I tried turning off the
> Windows firewall. I tried bypassing the router, hooking the PC
> directly to the DSL modem. Nothing matters. IIS had worked forever. We
> didn't install or reconfigure anything. But I do think Windows Update
> may have run a few times. A Netstat shows this line for port 80:
> TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
> Since I've never had to look at netstat before, I'm not sure whether
> this is right. Can anyone help? Are there any diagnostics that I can
> run?
> Thanks.
>
| |
| Tiago Halm 2005-06-10, 8:48 pm |
| Check if you installed WinXP SP2.
Check if you have a rule to block IPs other then 127.0.0.1.
Tiago Halm
"Joe" <joewasik@msn.com> wrote in message
news:1118422772.512972.239730@o13g2000cwo.googlegroups.com...
> Thanks for your notes. At this point I think I'm going to have to find
> someone smarter than me to come and examine this system. Your
> suggestion of hooking up two computers is probably a good one but
> beyond my capabilities. I did find a port sniffer to have closer look
> at what is going on. From a second computer I tried to access IIS on
> the problem computer. The port sniffer saw 3 incoming packets. It
> identified them as http packets on port 80. The sniffer showed 3 acks
> going back. All six packets had a zero data length. So it seems that
> no firewall or ISP is blocking incoming traffic. I did get Telnet to
> work properly, but on its own default port, not 80. So Telnet is
> getting through everything and working. I may still try and install
> Apache as an experiment, and if by chance it works, as a replacement
> for IIS.
>
| |
|
| Jeff, I have installed Apache and it works like a charm. No problems
what-so-ever. No setup what-so-ever. Installed Apache and it worked
out of the box. Thanks for all of your help and your expertice, but I
think you now need to re-evaluate how to diagnose HHTP server problems.
| |
| David Wang [Msft] 2005-06-12, 2:48 am |
| Pardon me for jumping in here.
I do not think there is anything wrong with what Jeff was suggesting. Like
everyone, it is puzzling to see IIS work just fine for localhost but not for
remote -- all of a sudden.
We have seen many reports of "IIS stops working in random ways" on the
newsgroup, and I'd like to figure out if yours is a case of some overzealous
security software setting, configuration, product issue, or non issue.
Putting together the facts that Apache is working on port 80 but IIS does
not tells me that either IIS is just plain broken, or something is
intentionally blocking IIS for non-localhost requests somehow. But, you said
that IIS was working fine on that machine some time back, and barring some
random hard drive corruption of IIS files that prevent it from functioning
(seems unlikely), I have to start looking at whether you or someone else
installed software or configuration that intentionally prevents IIS from
responding to non-localhost requests.
Your network capture suggests that IIS did get the remote requests but the
responses were mysteriously zero bytes. Hmm... maybe some ISAPI Filter was
installed to do that (consume response entity of non-localhost requests), or
IPRestriction got set on IIS by some product (you can't set IP Restriction
on IIS on XP Pro from the UI).
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Joe" <joewasik@msn.com> wrote in message
news:1118543754.182068.238750@g14g2000cwa.googlegroups.com...
Jeff, I have installed Apache and it works like a charm. No problems
what-so-ever. No setup what-so-ever. Installed Apache and it worked
out of the box. Thanks for all of your help and your expertice, but I
think you now need to re-evaluate how to diagnose HHTP server problems.
| |
|
| David, I mentioned this in a previous post. I did completely
un-install IIS and re-installed it. The InetPub folder was manually
removed and automatically re-created. This re-install did not improve
things. Only a few days went by during which, sometime, IIS stopped
working. During that period, I'm only aware of Windows Update running
(something called a malitious software removal tool?). I also run
Norton Anti-Virus, but disabling it did not help. I used to have
Symantec Firewall, but its frequent corruption led me to un-install it.
I don't know what else to tell you. It would be nice if there were
some kind of diagnostics. Thanks, though.
| |
| Jeff Cochran 2005-06-13, 2:48 am |
| On 11 Jun 2005 19:35:54 -0700, "Joe" <joewasik@msn.com> wrote:
>Jeff, I have installed Apache and it works like a charm. No problems
>what-so-ever. No setup what-so-ever. Installed Apache and it worked
>out of the box. Thanks for all of your help and your expertice, but I
>think you now need to re-evaluate how to diagnose HHTP server problems.
Glad to hear it works for you. But as long as the localhost address
works, the logical place to look is outside IIS. David is correct
that an ISAPI filter of some sort could possibly be involved, but
that's something that is hard to install unnoticed.
Hopefully you won't run into issues with Apache, but there are support
groups for those issues as well.
Jeff
| |
|
| Dear Microsoft MVPs, This is now an old thread, but I hope you will
still find this. I did an experiment. On the problem PC, I installed
Microsoft Virtual PC. In it, I installed another Windows XP Pro --
which, by the way, runs extremely slow. My new Virtual IIS has a new
internal IP address. My router passes HTTP traffic to this new IP
address. I left this whole thing running. Went to work. Presto!
Virtual IIS works normally. If it weren't so incredibly slow, I'd
meticulously compare every file, every setting between the real IIS and
the virtual IIS. I'm hoping you can suggest some likely places to look.
I'm going to start with "local security policies".
| |
| David Wang [Msft] 2005-07-02, 7:50 am |
| Did you install VM Additions in the Guest VM? VM Additions make Windows run
a lot better inside a Virtual PC VM.
It really seems like something in your host PC was blocking IIS, but in your
clean Guest VM installation, it wasn't installed -- so things worked.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Joe" <joewasik@msn.com> wrote in message
news:1120172991.563732.308310@g47g2000cwa.googlegroups.com...
Dear Microsoft MVPs, This is now an old thread, but I hope you will
still find this. I did an experiment. On the problem PC, I installed
Microsoft Virtual PC. In it, I installed another Windows XP Pro --
which, by the way, runs extremely slow. My new Virtual IIS has a new
internal IP address. My router passes HTTP traffic to this new IP
address. I left this whole thing running. Went to work. Presto!
Virtual IIS works normally. If it weren't so incredibly slow, I'd
meticulously compare every file, every setting between the real IIS and
the virtual IIS. I'm hoping you can suggest some likely places to look.
I'm going to start with "local security policies".
| |
|
| Hello, No I had not installed the VM additions. When I read that some
things don't work with VM Additions, I went for maximum compatibility.
Thanks for that advice. I will follow it. As for you suggestion that
something is blocking my IIS, I am forced to give the "well.. duh"
response. How about a suggestion on how to find out *what* is blocking
IIS. Thanks.
| |
| David Wang [Msft] 2005-07-03, 8:47 pm |
| You have said that "localhost works with IIS", and "Virtual Machine work
with IIS", which suggest that the problem is not with IIS nor with its
configuration (assuming you did something similar) but rather something else
on the problematic system. Since that "something else" is arbitrary,
suggestions on how to figure it out is also arbitrary.
For example:
- Use IP address instead of localhost/names to remove DNS (and HOSTS file)
resolution from the picture
- Use netstat to check on the bindings that IIS uses to listen for requests
- Make sure things like IP Restriction (both in IIS as well as at the
TCP-level throughout the OS)
- Make sure there is no firewall blocking inbound and outbound requests
- Make sure there is no NAT/Proxy blocking your inbound and outbound
requests
- etc
The numbers of knobs to tweak here is completely arbitrary and depends on
the set of software on your system, and most of the time, they have nothing
to do with IIS (though people that want to run web servers end up having to
figure it out -- thus people think it is an IIS-issue when it really isn't)
As I had said earlier -- there are many products out there that love to
disable IIS in non-obvious ways because they don't want you to run in on XP
Pro (and you condone their actions by installing those products on your
machine). You're pretty much fighting the uphill battle. You may want to
take the opportunity to figure out what programs you have NOT installed in
the Virtual Machine and see which is breaking IIS for you.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Joe" <joewasik@msn.com> wrote in message
news:1120367692.345869.262170@f14g2000cwb.googlegroups.com...
Hello, No I had not installed the VM additions. When I read that some
things don't work with VM Additions, I went for maximum compatibility.
Thanks for that advice. I will follow it. As for you suggestion that
something is blocking my IIS, I am forced to give the "well.. duh"
response. How about a suggestion on how to find out *what* is blocking
IIS. Thanks.
|
|
|
|
|