newb: Allowing other LAN users to connect to my IIS instance

I've been stuck with updating our website and have deployed a development
version to my localhost IIS. I've set the virtual directory to Application.
I can connect just fine by browsing to http://localhost/my_virtual_directory

When another user on the LAN tries to connect to
http://my-machine-name/my_virtual_directory it times out. We are all on the
same domain.
I haven't changed the secutiry settings in IIS as I have no idea what
settings to change. I have done this years ago and though it was a simple
process, and it may be, but I'm missing something. Google is not coming
back with the information I need, probably because I'm not sure what terms
to search for.

I'm running asp.net 2.0 on Windows XP Professional.

Thanks for any suggestions,
Steve

Re: Allowing other LAN users to connect to my IIS instance

a) Is anything logged in the IIS logfile for the request from your
co-worker? If not, then the request may not be making it to IIS at all

b) in that case, I would start by looking at firewall/proxy settings. You
(or your coworker) may have a firewall enabled that is blocking access to
the webserver

Cheers
Ken

"sklett" wrote in message
news:uN0ysUcEIHA.3880@TK2MSFTNGP06.phx.gbl...
> I've been stuck with updating our website and have deployed a development
> version to my localhost IIS. I've set the virtual directory to
> Application. I can connect just fine by browsing to
> http://localhost/my_virtual_directory
>
> When another user on the LAN tries to connect to
> http://my-machine-name/my_virtual_directory it times out. We are all on
> the same domain.
> I haven't changed the secutiry settings in IIS as I have no idea what
> settings to change. I have done this years ago and though it was a simple
> process, and it may be, but I'm missing something. Google is not coming
> back with the information I need, probably because I'm not sure what terms
> to search for.
>
> I'm running asp.net 2.0 on Windows XP Professional.
>
> Thanks for any suggestions,
> Steve
>

Re: newb: Allowing other LAN users to connect to my IIS instance

On Oct 18, 1:24 pm, "sklett" wrote:
> I've been stuck with updating our website and have deployed a development
> version to my localhost IIS. I've set the virtual directory to Application.
> I can connect just fine by browsing tohttp://localhost/my_virtual_directory
>
> When another user on the LAN tries to connect tohttp://my-machine-name/my_virtual_directoryit times out. We are all on the
> same domain.
> I haven't changed the secutiry settings in IIS as I have no idea what
> settings to change. I have done this years ago and though it was a simple
> process, and it may be, but I'm missing something. Google is not coming
> back with the information I need, probably because I'm not sure what terms
> to search for.
>
> I'm running asp.net 2.0 on Windows XP Professional.
>
> Thanks for any suggestions,
> Steve


It is still a simple process.

It's the (Internet) world that has changed, from being a very open,
friendly environment to a very closed and secured/constrained
environment. You may be friends with someone and they have a computer
on the LAN, but your computer hardly carries over your human
relationships and is unlikely to be friends with that person's
computer.

By default, XPSP2 will turn on the Windows Firewall, which will block
another user on the LAN to connect to http://my-machine-name. You will
need to open the HTTP port in the Firewall.

If your issue is not the Firewall, then check the IIS log file to make
sure the other LAN user's request even shows up in the IIS log file.
If it doesn't show up, then it means that their timeout is because
their request went to the wrong server -- at which point you have to
look at that user's DNS configuration to figure out where they went
astray.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Re: newb: Allowing other LAN users to connect to my IIS instance

"David Wang" wrote in message
news:1192761200.925169.271590@i13g2000prf.googlegroups.com.. .
> On Oct 18, 1:24 pm, "sklett" wrote:
>> I've been stuck with updating our website and have deployed a development
>> version to my localhost IIS. I've set the virtual directory to
>> Application.
>> I can connect just fine by browsing
>> tohttp://localhost/my_virtual_directory
>>
>> When another user on the LAN tries to connect
>> tohttp://my-machine-name/my_virtual_directoryit times out. We are all on
>> the
>> same domain.
>> I haven't changed the secutiry settings in IIS as I have no idea what
>> settings to change. I have done this years ago and though it was a
>> simple
>> process, and it may be, but I'm missing something. Google is not coming
>> back with the information I need, probably because I'm not sure what
>> terms
>> to search for.
>>
>> I'm running asp.net 2.0 on Windows XP Professional.
>>
>> Thanks for any suggestions,
>> Steve
>
>
> It is still a simple process.
>
> It's the (Internet) world that has changed, from being a very open,
> friendly environment to a very closed and secured/constrained
> environment. You may be friends with someone and they have a computer
> on the LAN, but your computer hardly carries over your human
> relationships and is unlikely to be friends with that person's
> computer.
>
> By default, XPSP2 will turn on the Windows Firewall, which will block
> another user on the LAN to connect to http://my-machine-name. You will
> need to open the HTTP port in the Firewall.
>
> If your issue is not the Firewall, then check the IIS log file to make
> sure the other LAN user's request even shows up in the IIS log file.
> If it doesn't show up, then it means that their timeout is because
> their request went to the wrong server -- at which point you have to
> look at that user's DNS configuration to figure out where they went
> astray.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>

Thanks for the reply David,

I checked the log file and there are no requests from the other machine. I
can see my 127.0.0.1 requests but nothing else. I don't have the windows
firewall on my machine turned on. I don't think it's a DNS problem because
the same name entered into explorer will open my shared folders.
Additionally, I tried hitting my machine with the IP and it still isn't
logging anything.

If I had a security configuration problem in IIS, would I still see
something in the log? Would there be any indication of why a page wasn't
served up?

Thanks again,
Steve

SOLVED

I was mistaken, it was windows firewall. Please ignore my previous post
saying it wasn't.
Thanks for the suggestions guys, I feel like a dope for not checking this
before asking here! ;0)

-Steve