• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1031
  • Last Modified:

FQDN leads to timeout

Hi guys

i'm stumped with this one...

I have a server that i've moved from our LAN to the DMZ. This has IIS running on it.
Everything was working fine up to today, when suddenly the FQDN leads to a timeout, though when i browse to just the host name, it works fine.

Would it have anything to do with DNS refreshing, or something like that?
Brian
0
ITUCIRL
Asked:
ITUCIRL
  • 2
1 Solution
 
meko72Commented:
Check DNS entries in advanced TCP/IP settings. Make sure you have appropriate DNS suffix entries. If not a member of the domain you need to have DNS suffix for this computer setting as well.

Another thing often missed is the System settings in the control panel. On the Computer Name tab select change and then more. Ensure your primary DNS suffix is entered here.
0
 
ITUCIRLAuthor Commented:
The server has the DNS suffix under the Computer Name in CP.

when i ping the box, i get the following:

c:\ping servername
pinging servername.domainname

so it looks as though DNS is ok. Would it be something in IIS?
0
 
ITUCIRLAuthor Commented:
IT turns out that the firewall was blocking some LDAP etc ports that were preventing the server from registering correctly.
It now is reachable with the FQDN.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now