Problems with WEBDav

[Brett Smith]

I know that this probably isn't the best place to post this but I already
posted it in the exchange.devolopment group, and have not gotten any
responces, so I thought that I would post it here.

I am having trouble accessing exchange via a WEBDav SEARCH query. I am
getting the OWA Frameset page back instead of a XML dataset.

This only happens for one of the Exchange servers that I query. the server
is SBS2000, and OWA works properly. When I run my SEARCH request against
other SBS2000 and SBS2003 Exchange servers I get the XML results, but with
one perticular machine I only get the frameset page

I am setting the header info per the exch docs

HttpWRequest.KeepAlive = False
HttpWRequest.Headers.Set("Pragma", "no-cache")
HttpWRequest.Headers.Set("Translate", "f")
HttpWRequest.Headers.Set("Depth", "0")
HttpWRequest.ContentType = "text/xml"
HttpWRequest.ContentLength = sQuery.Length
HttpWRequest.Timeout = 300000
HttpWRequest.Method = "SEARCH"

What am I doing wrong, or is there something that I need to change on the
Exchange server

 

[Brett Smith]

OK I will answer my own question. The Exchange server in question had OWA
running on a non standard port. Because of this the query was getting messed
up. If i opened port 443 the query worked perfectly.

This begs the question why can't I webdav query this server on a non
standard port?

 

[Brett Smith]

Answer: I was using an alias that redirected requests to the the
non-standard port rather than using the IPort format. this caused a
problem with the TRAVERSAL portion of my Search Query. passing the request
as IPort worked properly.

I now have to resolve the address programatically, and then pass the proper
ipaddress and port to the query.

How would I from within VB determine the ip AND port of a FQDN?