Can't connect behind a DNS Server?

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
orangeibm

Can't connect behind a DNS Server?

Post by orangeibm » Wed Mar 24, 2004 12:08 am

Is there anyway to expose the Vault Server from behind a DNS hosted server? Do I need to enable any services or open up any ports?

I am getting the message: No server found at URL
http://mysite/VaultService

sterwill
Posts: 256
Joined: Thu Nov 06, 2003 10:01 am
Location: SourceGear

Post by sterwill » Wed Mar 24, 2004 8:14 am

I'm a little confused about what you mean. Assuming DNS means Domain Name System, which is a method of resolving names to IP numbers, it sounds like your problem may be with name-based virtual host configuration (where a web server with a single IP hosts web sites for multiple domains by requirement of the HTTP/1.1 "Host" header). In this situation, the web server will bind to port 80 on its single IP, which will service all domains.

I'd try the following troubleshooting steps, in approximate order:
  • Make sure the client can resolve "mysite" to an IP. Use something like "nslookup mysite" at the command prompt.
  • Make sure the web server that "mysite" resolves to is listening on port 80. "telnet mysite 80", type "GET" then Enter a few times, and wait for some HTML to come back (possibly an error message).
  • If you've come this far, everything on the client seems OK. Opening http://mysite/VaultService in a web browser should also work.
  • I'm not an expert at configuring IIS for name-based virtual hosts, but you can use the IIS administration tool to check all the hosts are correctly spelled, have the correct web roots, etc.
Shaw Terwilliger
SourceGear LLC
`echo sterwill5sourcegear6com | tr 56 @.`

Post Reply