Prev: "Access denied" frm Vista client to Win2003 server, but not XP or
Next: Workstation Administrator
From: James McIllece [MS] on 10 May 2010 13:18
niemiro <guest(a)unknown-email.com> wrote in
news:39edeb16430034950780b2be1024bdfa(a)nntp-gateway.com:

>
> Hi Everyone,
>
> Sorry, this is probably the wrong newsgroup (I could not decide between
> here, Virtual Server or Networking!)
>
> I am trying to set up a local Intranet (a local website, not file share
> system) and I am using IIS 7 because this is a very advanced asp.net
> website. I have got it working on my machine, but I cannot get it to
> work on any other machine connected to my network. They can all access
> my file share and normal network, but cannot use the IIS localhost.
>
> I have read about changing the Hosts file, but when I try to ping
> localhost, I do not get a valid IP to enter in the Hosts file. I am
> obviously doing something wrong. Does anyone have any tips on how to do
> this?
>
> After yet more research, is this a better way of trying: Set all local
> IP addresses to static. Note my static IP. This website inhabits a
> special folder, not directly on my IIS server which is making things
> more difficult. Can I add this to the Hosts file:
>
> {My Local IP}\{Website Directory} localhost\{Website Name}
>
> eg: 192.168.2.2\Test localhost\Test
>
> Thanks for any advice,
>
> Richard
>
>

Hi Richard --

It sounds like there is a possibility that your basic network services are
not installed and running correctly.

Using DHCP is usually a good idea, rather than statically configuring IP
addresses. In DHCP options (or in TCP/IP properties if you are doing static
IPs), ensure that the IP address of your name resolution server (WINS
server or DNS server) is present.

It is possible that your users are unable to access your Web server because
you don't have one of these technologies deployed or if they are deployed
the users' computers can't locate the server. (Using WINS or DNS means you
don't need to manually configure hosts or lmhosts files on each individual
machine.)

In case you are not familiar with these technologies, WINS is low
maintenance and good for small networks - all you have to do is install it
and it works. But if you think your network is going to expand or you want
the added security of a domain, use DNS with Active Directory. (The Windows
Server 2008 Foundation Network Guide provides instructions on how to deploy
this type of network, at http://technet.microsoft.com/en-
us/library/cc771066(WS.10).aspx).

You might also double-check your Web server deployment using the IIS 7
Deployment Scenarios content at http://technet.microsoft.com/en-
us/library/cc772326%28WS.10%29.aspx, and ensure that users' browser
security settings are not preventing them from accessing the site.

--
James McIllece, Microsoft

Please do not send email directly to this alias. This is my online account
name for newsgroup participation only.

This posting is provided "AS IS" with no warranties, and confers no rights.

 | 
Pages: 1
Prev: "Access denied" frm Vista client to Win2003 server, but not XP or
Next: Workstation Administrator