.local -> .com

We have an internal network configuration using the DNS domain,
companyname.local. We decided to allow access to a website on this domain
from outside the office (using SSL certificates). We configured the website
as a subdomain of our corporate site (hosted by a hosting provider). The
added the A-Name DNS info on our hosting provider's site to point the
subdomain, subdomain.companyname.com to an IP address coming in to our office
network.

SUMMARY:
Want to use IP address on internal companyname.local network as
subdomain.companyname.com

Already configured hosting provider's DNS to work point to IP address

Already configured internal DNS to point to IP address (albiet .local
instead of .com)

Already added IIS Host headers on the appropriate web app and set it to the
correct IP.

PROBLEM:
Sometimes it works fine from outside the office. Most of the time we can't
access the site from outside of the office. We can always access it from
within the office or via VPN.

How can I ensure consistent outside availability? Is this a DNS problem? Is
this an ApplicationPool problem? We have no IT dept, so I am new at this.

Thanks for the help in advance.
Jeff Millians

Re: .local -> .com

well to check to see if its a DNS problem, from your home machine (anything
not on your network) run an NSLOOKUP from the command prompt

nslookup subdomain.domain.com

also, another test to make sure the firewall exceptions and what not are
fine, instead of going to sd.d.com go to the ip of the machine and see if it
lets you in.

also, within IE, under tools, adv options, there is a check box that is by
default checked, called show friendly http errors, uncheck that and see what
info you get.

404 = server running but something is missing
500 = problem with your web app
a dns problem will typially get you a really horrible message that says
something generic about it not being able to find the host... give those a
try and let us know what you get.

Justin

"JMillians (beginner)" wrote
in message news:2381C2AF-AE9C-4FFC-99F5-A2296C8F83E6@microsoft.com...
> We have an internal network configuration using the DNS domain,
> companyname.local. We decided to allow access to a website on this domain
> from outside the office (using SSL certificates). We configured the
> website
> as a subdomain of our corporate site (hosted by a hosting provider). The
> added the A-Name DNS info on our hosting provider's site to point the
> subdomain, subdomain.companyname.com to an IP address coming in to our
> office
> network.
>
> SUMMARY:
> Want to use IP address on internal companyname.local network as
> subdomain.companyname.com
>
> Already configured hosting provider's DNS to work point to IP address
>
> Already configured internal DNS to point to IP address (albiet .local
> instead of .com)
>
> Already added IIS Host headers on the appropriate web app and set it to
> the
> correct IP.
>
> PROBLEM:
> Sometimes it works fine from outside the office. Most of the time we
> can't
> access the site from outside of the office. We can always access it from
> within the office or via VPN.
>
> How can I ensure consistent outside availability? Is this a DNS problem?
> Is
> this an ApplicationPool problem? We have no IT dept, so I am new at this.
>
> Thanks for the help in advance.
> Jeff Millians

Re: .local -> .com

Thanks Justin.

NSLOOKUP returned the correct IP from outside the office

Using the IP address instead of sd.d.com did not work

Unchecking the "Show friendly..." results in the "ugly" Internet Explorer
cannot display the webpage.

I assume this is a DNS error, but since the NSLOOKUP worked, the DNS problem
must be on my internal server.

Any ideas?


++++++++++++++++++++++++++++++++++++++++++++++++++

"Justin Rich" wrote:

> well to check to see if its a DNS problem, from your home machine (anything
> not on your network) run an NSLOOKUP from the command prompt
>
> nslookup subdomain.domain.com
>
> also, another test to make sure the firewall exceptions and what not are
> fine, instead of going to sd.d.com go to the ip of the machine and see if it
> lets you in.
>
> also, within IE, under tools, adv options, there is a check box that is by
> default checked, called show friendly http errors, uncheck that and see what
> info you get.
>
> 404 = server running but something is missing
> 500 = problem with your web app
> a dns problem will typially get you a really horrible message that says
> something generic about it not being able to find the host... give those a
> try and let us know what you get.
>
> Justin
>
> "JMillians (beginner)" wrote
> in message news:2381C2AF-AE9C-4FFC-99F5-A2296C8F83E6@microsoft.com...
> > We have an internal network configuration using the DNS domain,
> > companyname.local. We decided to allow access to a website on this domain
> > from outside the office (using SSL certificates). We configured the
> > website
> > as a subdomain of our corporate site (hosted by a hosting provider). The
> > added the A-Name DNS info on our hosting provider's site to point the
> > subdomain, subdomain.companyname.com to an IP address coming in to our
> > office
> > network.
> >
> > SUMMARY:
> > Want to use IP address on internal companyname.local network as
> > subdomain.companyname.com
> >
> > Already configured hosting provider's DNS to work point to IP address
> >
> > Already configured internal DNS to point to IP address (albiet .local
> > instead of .com)
> >
> > Already added IIS Host headers on the appropriate web app and set it to
> > the
> > correct IP.
> >
> > PROBLEM:
> > Sometimes it works fine from outside the office. Most of the time we
> > can't
> > access the site from outside of the office. We can always access it from
> > within the office or via VPN.
> >
> > How can I ensure consistent outside availability? Is this a DNS problem?
> > Is
> > this an ApplicationPool problem? We have no IT dept, so I am new at this.
> >
> > Thanks for the help in advance.
> > Jeff Millians
>
>
>

Re: .local -> .com

you said you set a host header value. do you have multiple websites on this
server?
if not i would remove the host header info, there is really no need for it
and i suspect it might be your issue.

the host header basically allows you to run multiple websites off of one ip.


"JMillians (beginner)" wrote
in message news:55878146-00AC-4E64-93D7-43D2A767042D@microsoft.com...
> Thanks Justin.
>
> NSLOOKUP returned the correct IP from outside the office
>
> Using the IP address instead of sd.d.com did not work
>
> Unchecking the "Show friendly..." results in the "ugly" Internet Explorer
> cannot display the webpage.
>
> I assume this is a DNS error, but since the NSLOOKUP worked, the DNS
> problem
> must be on my internal server.
>
> Any ideas?
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++
>
> "Justin Rich" wrote:
>
>> well to check to see if its a DNS problem, from your home machine
>> (anything
>> not on your network) run an NSLOOKUP from the command prompt
>>
>> nslookup subdomain.domain.com
>>
>> also, another test to make sure the firewall exceptions and what not are
>> fine, instead of going to sd.d.com go to the ip of the machine and see if
>> it
>> lets you in.
>>
>> also, within IE, under tools, adv options, there is a check box that is
>> by
>> default checked, called show friendly http errors, uncheck that and see
>> what
>> info you get.
>>
>> 404 = server running but something is missing
>> 500 = problem with your web app
>> a dns problem will typially get you a really horrible message that says
>> something generic about it not being able to find the host... give those
>> a
>> try and let us know what you get.
>>
>> Justin
>>
>> "JMillians (beginner)"
>> wrote
>> in message news:2381C2AF-AE9C-4FFC-99F5-A2296C8F83E6@microsoft.com...
>> > We have an internal network configuration using the DNS domain,
>> > companyname.local. We decided to allow access to a website on this
>> > domain
>> > from outside the office (using SSL certificates). We configured the
>> > website
>> > as a subdomain of our corporate site (hosted by a hosting provider).
>> > The
>> > added the A-Name DNS info on our hosting provider's site to point the
>> > subdomain, subdomain.companyname.com to an IP address coming in to our
>> > office
>> > network.
>> >
>> > SUMMARY:
>> > Want to use IP address on internal companyname.local network as
>> > subdomain.companyname.com
>> >
>> > Already configured hosting provider's DNS to work point to IP address
>> >
>> > Already configured internal DNS to point to IP address (albiet .local
>> > instead of .com)
>> >
>> > Already added IIS Host headers on the appropriate web app and set it to
>> > the
>> > correct IP.
>> >
>> > PROBLEM:
>> > Sometimes it works fine from outside the office. Most of the time we
>> > can't
>> > access the site from outside of the office. We can always access it
>> > from
>> > within the office or via VPN.
>> >
>> > How can I ensure consistent outside availability? Is this a DNS
>> > problem?
>> > Is
>> > this an ApplicationPool problem? We have no IT dept, so I am new at
>> > this.
>> >
>> > Thanks for the help in advance.
>> > Jeff Millians
>>
>>
>>

Re: .local -> .com

"Sometimes it works, and sometimes it does not". What is changed from when
it works, and when it does not work?

My first thought when i hear this description (and it also always works
from the LAN) is that there is a network issue.

I don't think it is an IIS issue. If it were, you would have problems
accessing the website from the LAN as well.

--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


JMillians (beginner) wrote:

>We have an internal network configuration using the DNS domain,
>companyname.local. We decided to allow access to a website on this domain
>from outside the office (using SSL certificates). We configured the
>website
>as a subdomain of our corporate site (hosted by a hosting provider). The
>added the A-Name DNS info on our hosting provider's site to point the
>subdomain, subdomain.companyname.com to an IP address coming in to our
>office
>network.
>
>SUMMARY:
>Want to use IP address on internal companyname.local network as
>subdomain.companyname.com
>
>Already configured hosting provider's DNS to work point to IP address
>
>Already configured internal DNS to point to IP address (albiet .local
>instead of .com)
>
>Already added IIS Host headers on the appropriate web app and set it to the
>correct IP.
>
>PROBLEM:
>Sometimes it works fine from outside the office. Most of the time we can't
>access the site from outside of the office. We can always access it from
>within the office or via VPN.
>
>How can I ensure consistent outside availability? Is this a DNS problem?
>Is
>this an ApplicationPool problem? We have no IT dept, so I am new at this.
>
>Thanks for the help in advance.
>Jeff Millians

Re: .local -> .com

Sounds like a dual homed machine to me. If you have two NICs setup,
you can NOT have two default gateways, Windows will mess up. What
will happen is that sometimes it will take the public route back,
other times it will take the private route back and die. I still
haven't figured out why it will work hours and hours and then Windows
suddenly decides to use the other gateway. Either way, you have to
remove the default gateway off the local NIC and then put in static
routes to send local traffic to the local gateway.


beginner JMillians wrote:
> We have an internal network configuration using the DNS domain,
> companyname.local. We decided to allow access to a website on this domain
> from outside the office (using SSL certificates). We configured the website
> as a subdomain of our corporate site (hosted by a hosting provider). The
> added the A-Name DNS info on our hosting provider's site to point the
> subdomain, subdomain.companyname.com to an IP address coming in to our office
> network.
>
> SUMMARY:
> Want to use IP address on internal companyname.local network as
> subdomain.companyname.com
>
> Already configured hosting provider's DNS to work point to IP address
>
> Already configured internal DNS to point to IP address (albiet .local
> instead of .com)
>
> Already added IIS Host headers on the appropriate web app and set it to the
> correct IP.
>
> PROBLEM:
> Sometimes it works fine from outside the office. Most of the time we can't
> access the site from outside of the office. We can always access it from
> within the office or via VPN.
>
> How can I ensure consistent outside availability? Is this a DNS problem? Is
> this an ApplicationPool problem? We have no IT dept, so I am new at this.
>
> Thanks for the help in advance.
> Jeff Millians

Re: .local -> .com

Thank you all for your help. It seems that the problem is the dual NIC
setup. Thank you Will - I had no idea this was the case. We are currently
working on proper routing in lieu of the default gateway.

Again, thank you all for your help.

Jeff

"Will" wrote:

> Sounds like a dual homed machine to me. If you have two NICs setup,
> you can NOT have two default gateways, Windows will mess up. What
> will happen is that sometimes it will take the public route back,
> other times it will take the private route back and die. I still
> haven't figured out why it will work hours and hours and then Windows
> suddenly decides to use the other gateway. Either way, you have to
> remove the default gateway off the local NIC and then put in static
> routes to send local traffic to the local gateway.
>
>
> beginner JMillians wrote:
> > We have an internal network configuration using the DNS domain,
> > companyname.local. We decided to allow access to a website on this domain
> > from outside the office (using SSL certificates). We configured the website
> > as a subdomain of our corporate site (hosted by a hosting provider). The
> > added the A-Name DNS info on our hosting provider's site to point the
> > subdomain, subdomain.companyname.com to an IP address coming in to our office
> > network.
> >
> > SUMMARY:
> > Want to use IP address on internal companyname.local network as
> > subdomain.companyname.com
> >
> > Already configured hosting provider's DNS to work point to IP address
> >
> > Already configured internal DNS to point to IP address (albiet .local
> > instead of .com)
> >
> > Already added IIS Host headers on the appropriate web app and set it to the
> > correct IP.
> >
> > PROBLEM:
> > Sometimes it works fine from outside the office. Most of the time we can't
> > access the site from outside of the office. We can always access it from
> > within the office or via VPN.
> >
> > How can I ensure consistent outside availability? Is this a DNS problem? Is
> > this an ApplicationPool problem? We have no IT dept, so I am new at this.
> >
> > Thanks for the help in advance.
> > Jeff Millians
>
>