Re: Cannot find server or DNS Error

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Sparky Polastri (jafiwam_at_MuNGEDyahoo.com)
Date: 01/26/05 

Date: Wed, 26 Jan 2005 07:27:12 -0600

The ip address of the internal side of your firewall/gateway cannot be the
same as the IP address of the NIC on the web server. (This, assuming
"Internal IP Address" is not a "forward to" instruction but rather a "what's
the IP of" instruction in your firewall setup, it's not clear from your post
what it actually is.)

You must assign an IP address (or more than one if you want) to your
webserver NIC, then translate using your pinhole to point traffic coming in
on port 1101 to the external side of your firewall to the LAN side using a
DIFFERENT IP address on that LAN than the one(s) on your web server NIC.

Then you tell your web server (IIS) that it should look for traffic on that
NIC on such and such port (in the case of your setup, port 80) on *.49.

>From your info, you may have a routing issue on your network due to
duplicate IP addresses. (Again, I am assuming the "internal IP line"
defines the LAN IP of the router, and not as a target for the traffic to go
to.)

Else;

IIS is configured like this;

Find out IP address on NIC.

Find out if server can send/receive traffic on that IP on that NIC.

Match up hostnames to the NIC address using DNS.

Look in IIS, find or create a web. IF you are just using one web site and
not doing interesting stuff, you can make a site respond on all traffic
(where any HTTP traffic to the IP address on the NIC gets a response). IF
you are going to use more than one web site, or do different things with
"www" and "www2" or whatever, then you have to assign "Host headers" to the
web. So do; Hostname; port# in the "advanced" area for EACH hostname you
use. Then, when traffic hits the web server the server looks up the
hostname, (and assuming its on the right IP) uses that to determine which
web site should respond to the HTTP traffic.

The Key; the web server must get traffic on the ip address it expects and on
the port it expects as told to it by you.

I'd say you should stick with the first "IF" above if possible. Your router
might not be translating the HTTP header IP address so your server gets
"webname and IP" where the IP is still the external WAN ip address. It
won't know what to do with it and won't respond (or will respond with the
default web).

"Rick" <Rick@discussions.microsoft.com> wrote in message
news:D6F64724-3956-46C8-BD6A-54F4DE3925A7@microsoft.com...
> The web address is www.thepayrollpros.com. At the bottom of this main page
> is
> a link called "Client Entry". This link is "https://68.157.93.254/".
>
> The pinhole is defined...
> Pinhole Name UnsecureHTTP
> Protocol Select TCP
> External Port Start 1101
> External Port End 1101
> Internal IP Address 192.168.1.49
> Internal Port 80
>
> In IIS under "Web Sites" at "Default Web Site" properties..
> Description Default Web Site
> IP address 192.168.1.49
> TC port 80 SSL port 443
> at "Advanced"
> IP TCP port
> 192.168.1.49 80
>
>
>
>
> "Roland Hall" wrote:
>
>> "Rick" wrote in message
>> news:D26FFFB4-C5C2-4E75-8F4F-1F66D725F581@microsoft.com...
>> : "Sparky Polastri" wrote:
>> :
>> : > "Rick" <Rick@discussions.microsoft.com> wrote in message
>> : > news:89D3EE6B-421A-4A4B-A905-74D3511AEED8@microsoft.com...
>> : > >I replaced my Linux/Apache server box with Microsoft Server 2003 Web
>> : > >Edition.
>> : > > I also have a Netopia Cayman 3346 DSL Router the I have a pinhole
>> defined
>> : > > for
>> : > > internal port 80 (external port start 1101; external port end
>> 1101),
>> to be
>> : > > able to have my public IP address serve up pages on this web
>> server.
>> The
>> : > > pinhole basically maps the public IP address to the internal IP
>> address of
>> : > > the server. This worked fine on the Linux/Apache. But on the
>> Windows
>> box I
>> : > > get the above message. When I use the interanl IP address,(while at
>> work
>> : > > on
>> : > > the network) IE serves up the page just fine. I know that is must
>> be
>> some
>> : > > security setting in IIS but I am not very familiar with IIS. Help.
>> : >
>> : > Longshot, but did you add the hostname and ports IIS should respond
>> on?
>> You
>> : > have to tell it that it needs to respond to the traffic. (Web Site
>> : > properties, Web Site tab, advanced button)
>> : >
>> : Thanks for the quick response. On the advancved tab I have the IP
>> address
>> : defined to port 80. Do I need anything else.
>>
>> Please be specific. Your internal address doesn't tell anyone where you
>> are
>> but it does tell us what you have to help you configure it. "the IP
>> address" is not much on this end.
>>
>> The advanced button allows you to assign host headers. So, there are 3
>> things you can do, not just two. IP assignment is either all unassigned
>> or
>> an IP address, this would be an internal IP address. Port, default 80
>> and
>> host header (FQDN) you want the server to answer to if you're not
>> answering
>> to all. This would be your public domain name, including subdomain if
>> you
>> offer it.
>>
>> Ex. www.domain.com
>>
>> What settings do you have here?
>> Also, do you have internal DNS? If so, have you setup a forward lookup
>> zone
>> for your public (external) domain name?
>> What you try to access the web site from the public (Internet) network,
>> do
>> you use a name or an IP address?
>>
>> --
>> Roland Hall
>> /* This information is distributed in the hope that it will be useful,
>> but
>> without any warranty; without even the implied warranty of
>> merchantability
>> or fitness for a particular purpose. */
>> Online Support for IT Professionals -
>> http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
>> How-to: Windows 2000 DNS:
>> http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
>> FAQ W2K/2K3 DNS:
>> http://support.microsoft.com/default.aspx?scid=kb;EN-US;291382
>>
>>
>>

Relevant Pages

  • Re: SuSEfirewall2 and internal web server problems
    ... YaST provides some usefull tip. ... > the internet and everything works fine. ... > IP shows that I do have port 80 open, and it is possible to establish some ... > web server is not able to send anything in return. ...
    (alt.os.linux.suse)
  • Re: Virtual Directory to a remote UNC not working properly
    ... not auto-login to Internet address by default. ... it eventually accesses a page with NAS URL that looks ... My current authentication method on the Web Server is only set to Integrated ... need to open more holes in the firewall to allow RPC and UNC ports as ...
    (microsoft.public.inetserver.iis.security)
  • Re: Virtual Directory to a remote UNC not working properly
    ... The reason you get a login popup from Intranet is because browsers do ... not auto-login to Internet address by default. ... it eventually accesses a page with NAS URL that looks ... My current authentication method on the Web Server is only set to Integrated ...
    (microsoft.public.inetserver.iis.security)
  • Re: Apache web server being attacked
    ... There is no domain name pointing to my web server. ... But have had port 80 attacks that did not work. ... after yourself once you've generated a config file. ... This way my web site has total access by anyone who knows it's URl, the URL is scanned by yahoo and google indexing bot and becomes know to the public. ...
    (freebsd-questions)
  • Home web server hosting
    ... I am trying to set up a web server on my Mac so that a third party, for whom I am developing a web site, can look in from time to time to monitor progress. ... What I cannot get to work is an external (ie another computer on the internet) connection to the Apache server. ...
    (comp.sys.mac.comm)