James: --- "Ashe, James P." wrote: We are starting to consolidate some web servers onto a new windows server 2003 machine running IIS6. However, the HTTP probe always returns an error 400 when monitoring these migrated webs. Has anyone been able to get the HTTP probe to talk to IIS6? --- end of quote ---
A couple questions: - What version of InterMapper are you using? What platform (Mac, Windows, Unix)? - I looked up the 400 error, and it simply says "Bad request", and something about a syntax error. To debug this, I would construct a URL in your web browser consisting of the "Host name" and "URL Path" specified in the probe's configuration window. If that doesn't work, the error message you see a sense of what is wrong. If it seems fine, then a finer-grained test would be to emulate InterMapper's query via a telnet session. Telnet to the web server on the proper port, and then type the following, substituting the host name and URL Path as needed (case is important): GET <URL Path> HTTP/1.0<return> Host: <Host Name><return> User-Agent: InterMapper<return><return> The response from the server may give you a clue as to what's wrong. Please get back to me if you have further questions. Thanks. Rich Brown [EMAIL PROTECTED] Dartware, LLC http://www.dartware.com 10 Buck Road, PO Box 130 Telephone: 603-643-2268 Hanover, NH 03755-0130 USA Fax: 603-643-2289 ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [EMAIL PROTECTED]
