K
Kevin Spencer
Argumentative fellow, aren't you?
Visual Studio uses lots and lots of things. It uses a multitude of services,
network protocols, Internet Explorer, FrontPage Server extensions, the
ENTIRE .Net Platform, and even the Operating System. So, if the problem was
with the operating system, would you say that the problem is a VS.Net issue
as well? A problem with a service does not equate to a problem with a
client. D00d!
Your TCP/IP stack isn't hardware. It's software. And circumventing a problem
doesn't solve it.
As a suggestion, try adding a localhost entry to your machine's hosts and
lmhosts.sam files. It won't hurt to try, and it might help. And I think
Juan's recent advice would be well-taken. Look into your TCP/IP stack, if
you have the time.
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
Ambiguity has a certain quality to it.
Not so fast. If VS.NET is set up to use FrontPage Extensions and/or File
Sharing to communicate with IIS, then that is a VS.NET issue, not an
environment issue. You can't just rule out VS .NET and IIS without first
looking into the configuration of each.
Visual Studio uses lots and lots of things. It uses a multitude of services,
network protocols, Internet Explorer, FrontPage Server extensions, the
ENTIRE .Net Platform, and even the Operating System. So, if the problem was
with the operating system, would you say that the problem is a VS.Net issue
as well? A problem with a service does not equate to a problem with a
client. D00d!
I agree. So when I repeatedly informed Juan that hardware has been ruled
out and he repeatedly insisted that this was, in fact, my problem, I knew
that he was not someone who understands how to troubleshoot.
Your TCP/IP stack isn't hardware. It's software. And circumventing a problem
doesn't solve it.
As a suggestion, try adding a localhost entry to your machine's hosts and
lmhosts.sam files. It won't hurt to try, and it might help. And I think
Juan's recent advice would be well-taken. Look into your TCP/IP stack, if
you have the time.
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
Ambiguity has a certain quality to it.