Question Locked

SBS2003 and network unable to connect to a single website

0 helpful
20 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi all,
I have a clean build SBS 2003 server that works fine, except it just will not connect to a single website!!
The domain is called ricci whilst the externally hosted website is ricci-concept.com.
When I do an nslookup for ricci-concept.com on the server it responds with the local SBS IP address and server name, but the external unqualified name appears on the second line with the correct IP.
When I try to connect to the website ricci-concept.com it just times out.
This is more frustrating as thats where the emails are pulled from and we are unable to get them.
Does anyone have any ideas? I am on my jollies from the 28th for a week so a quick pointer or two would be very much appreciated.
TIA
Col

20 replies

by oh smeg

Odds are that it has something disabling this Auto Servicing Establishment.

In IE look at disabling the Phishing Filter and lowering the Security Rating.

Col ;)

by tosh124

If only it was that easy :)
That was the first thing I checked :(

by cg it

next is, are you trying to connect to the internal sharepoint web site?

if so, the url is http://companyweb not the SBS domain name.

Next is, if your company domain is ricci-concepts.com and you have an Internet web site named Ricci-concepts.com you should NOT host the web site on the SBS box and you should NOT use the SBS DNS server as the authoritative name server for an Internet web site. This will cause all sorts of problems both with accessing the web site and your internal users. Further, your SBS domain name should not use an Internet naming convention such as .com/.net you should use a non-Internet naming convention like .local.

So the bottom line is, host your public web site on a web server that is not part of your domain. Have the name servers that resolve the public domain name to your public IP address that is not your SBS box.

Use a non-Internet naming convention extension for your SBS domain eg use .local extension.

Users in the SBS domain can then access the companies public web site hosted on a web server via the http://domain name.com.

by tosh124

Nope, the SBS domain is ricci.local, BUT I do think that the local IIS server/companyweb is something to do with the problem. I have since removed the IIS server, but it hasnt made any difference.

The actual website is in the States so there SHOULDN'T be any confusion.

It is the same setup as I used before the hard drive crashed, which has presented no problems for the last couple of years...

by cg it

Small Business Server is an all-in-one-box solution that is configured by wizards and the management console. if you remove a role, you do so by inserting the DVD or CD 1 and rerun setup. Also, configuring the SBS box for internet access and email is done with the connect to the internet wizard. That is found in the Things to do list in the server management console [left pane].

what your problem sounds like is that there is an A record in DNS that says ricci.com = the SBS box. There's really no other way than that for client computers to be directed to the SBS box by a FQDN. The SBS box should not be able to resolve the company FQDN queries. It would then send that request to root-hint servers on the internet. Those queries would then be resolved by the authoritative name servers for the domain name which would direct the query to the hosting companies servers.

by tosh124

It will not connect via the IP either, so methinx it is a DNS issue :(

by netman1958

1 or 2 network cards in it? If it has 2, is 1 assigned a public IP and the other a private IP? If it only has 1 net card, is it assigned a private IP and does your internet router perform a static NAT from a public IP to the private IP?

I have seen an issue where a DNS query returns the public IP but some device is NAT'ing that public IP to the private IP that is actually assigned to that server. In that case, computers on the same LAN as the server can't connect to it using the public IP that DNS returns. You have to use the private ip from within the LAN. Split-brain DNS solves this issue.

by tosh124

The box has only card with an internal IP (192.168.0.1) and the router does perform a static NAT.

What is split-brain DNS?

by robo_dev

As long as there is a valid route through the LAN and/or firewall, and you are typing the correct IP address, that should work.

From here I see your site as:
67.201.13.98

Is that the internal address of the server as well? (I would doubt that).

if you enter that address in your browser, and it cannot connect to that, then I would try running tracert to that address, e.g.

tracert 67.201.13.98

by tosh124

There is a valid route through the LAN otherwise I wouldnt be able to connect to the other websites.
The site address you are viewing is correct and I can connect from everywhere else, and the internal server address is 192.168.0.1

When I did a tracert it stopped at about 25/30 hops which was somewhere in the States. If I do the tracert from a machine outside the LAN it traces the site without a problem.

by netman1958

Here is an article that explains split-brain DNS:
http://msdn.microsoft.com/en-us/library/ms954396.aspx
Scroll down the page to the section titled "Using Split-Brain DNS"

Usually, with Active Directory, your ADC is also your LAN's DNS server. It only knows about the actual(private)(the .local domain) IP's of your LAN devices. It is configured to forward DNS queries for zones it doesn't host(.com, .net) to a public DNS server which knows only about the public IPs for your network.

Can you connect to your server's website if you use the private IP that is actually assigned to the server? If so and you don't want to try split-brain, you CAN go to all of your local machines and add entries in their local hosts files that point to the private IP for devices you need to connect to.

by tosh124

I realise that the IIS should be an out-of-the-box solution, and to be fair usually is, but on this occassion...
IIS removal doesnt seem to have knocked the reliability any.
I dont use the Internet Connection wizard as it doesnt work well, preferring to set it up manually.
I must admit that my thoughts match yours re the FQDN, but I am having a problem finding the record...

by cg it

and not manually configure SBS.

look in DNS record folder _msdcs.[domain name]. XXX & [domain name].XXX folder for any records that have .com as the extension. if the folder itself has the .com extension, then your whole DNS record base is wrong and you will have to basically redo SBS from scratch.

if both folders do not have a .com extension, then you need to in forest and domain zones to find the wrong records. Also check your SOA. The primary server should have the non .com domain name listed.

look in your reserve look up zones for any records that have a FQDN extention in them.

by tosh124

TBH I don't normally use the wizards and to date this is the only time I have had a problem, maybe just luck :)
I don't recall seeing anything with a .com extension, but I will check again tomorrow and re-post.
Thanks for your help.

by tosh124

Hmm, I have checked all of the records and there isnt one with a .com extension, but there must be something wrong as the nslookup for the website points to 192.168.0.1 and there is an error on the logs
"The DNS server encountered a packet addressed to itself on IP address 192.168.0.1. The packet is for the DNS name "_ldap._tcp.pdc._msdcs.Ricci.local.". The packet will be discarded. This condition usually indicates a configuration error. "

Any other suggestions?
thanks

by tosh124

hiya & thanks for the link. Sadly there isnt anything new in there :(

by tosh124

there seems to be a discrepancy in the text of the domain.
In the system properties the domain is Ricci.local and the top line of the dns records refers as such, but the host is always lower case, ricci.local
Does this make a difference?

This discussion is closed to new replies.