Local network users can't see website

  • Thread starter Thread starter JonnyCab®
  • Start date Start date
J

JonnyCab®

Hi,

I have a Windows-2000 SP4 web server installed within an office network, IP
192.168.50.80. The router routes all HTTP, FTP, and Remote desktop traffic
to this server only.

With two sites on the server and the headers in IIS correctly configured,
the sites work fine OUTSIDE the office, but local users (not using DHCP, but
with hard-coded 192.168.xxx.xxx numbers) can't see the sites at all.

What am I doing wrong? I've tried all of the IIS IP address options (all,
192.168.50.80, and the external IP). The external IP makes the site
invisible to the internet.

I really need to get this working internally. Any help would be
appreciated!

Thanks!
 
I have a Windows-2000 SP4 web server installed within an office network, IP
192.168.50.80. The router routes all HTTP, FTP, and Remote desktop traffic
to this server only.
Click to expand...

Are you trying connect internally using the router external ip
address? You need to use the internal address of the webserver
http://192.168.50.80


Jim.
 
Hi,

I have a Windows-2000 SP4 web server installed within an office network, IP
192.168.50.80. The router routes all HTTP, FTP, and Remote desktop traffic
to this server only.

With two sites on the server and the headers in IIS correctly configured,
the sites work fine OUTSIDE the office, but local users (not using DHCP, but
with hard-coded 192.168.xxx.xxx numbers) can't see the sites at all.

What am I doing wrong? I've tried all of the IIS IP address options (all,
192.168.50.80, and the external IP). The external IP makes the site
invisible to the internet.

I really need to get this working internally. Any help would be
appreciated!

Thanks!
Click to expand...

Are the internal users accessing the site using http://192.168.50.80 or
http://whatever-yourpublic-address-is.com?

Internal users will need to use the former format not the later.
 
I have each site now set up in IIS as All Unassigned, and www.sitename.com
for each host header name. I also tried 192.168.50.80 for the IP, and it
still doesn't work...
Click to expand...

You need to get back to basics. Can you ping the ip addresses?
uninstall firewalls etc.


Jim.
 
JonnyCab® said:
Hi,

I have a Windows-2000 SP4 web server installed within an office network, IP
192.168.50.80. The router routes all HTTP, FTP, and Remote desktop traffic
to this server only.

With two sites on the server and the headers in IIS correctly configured,
the sites work fine OUTSIDE the office, but local users (not using DHCP, but
with hard-coded 192.168.xxx.xxx numbers) can't see the sites at all.

What am I doing wrong? I've tried all of the IIS IP address options (all,
192.168.50.80, and the external IP). The external IP makes the site
invisible to the internet.

I really need to get this working internally. Any help would be
appreciated!

Thanks!
Click to expand...

Is there a difference in the default gateway assigned to the DHCP PCs versus the
STATIC PCs?

What does a tracert to the site say? How far do you get.

Do you have more then one router?
 
shutout39 said:
Hi,

I have a Windows-2000 SP4 web server installed within an office network, IP
192.168.50.80. The router routes all HTTP, FTP, and Remote desktop traffic
to this server only.

With two sites on the server and the headers in IIS correctly configured,
the sites work fine OUTSIDE the office, but local users (not using DHCP, but
with hard-coded 192.168.xxx.xxx numbers) can't see the sites at all.

What am I doing wrong? I've tried all of the IIS IP address options (all,
192.168.50.80, and the external IP). The external IP makes the site
invisible to the internet.

I really need to get this working internally. Any help would be
appreciated!
Click to expand...

You need to setup DHCP and DNS on your server so that you can use it to
issue the IP addresses and so that you can create domain information in
DNS. Once you setup local DNS server you need to configure all the
workstations that have fixed IP so that they use the Windows 2000 DNS
server's DNS which forwards unresolved DNS queries outbound.

With this method, you create DNS entries for each domain in your server
and since your people are using your local DNS server for resolving the
names.
 
Back
Top