Then you need to get a packet capture to definitively find out how the client is resolving that name to an IP.
(that's not to say you won't have other issues, but like the OSI discussion has told us, you'll need to work up from the lowest level) Cheers Ken From: David Lum [mailto:david....@nwea.org] Sent: Friday, 28 May 2010 11:32 PM To: NT System Admin Issues Subject: RE: DNS alias change, no http to alias unless FQDN Q. Where does your client think that http://sharepointnew resolves to? A. The old server Dave From: Ken Schaefer [mailto:k...@adopenstatic.com] Sent: Friday, May 28, 2010 6:22 AM To: NT System Admin Issues Subject: RE: DNS alias change, no http to alias unless FQDN Where does your client think that http://sharepointnew resolves to? Does it resolve to the correct remote address? (if so, then you have a SharePoint or IIS configuration problem) If it doesn't resolve to the correct remote address, then perhaps a packet capture may tell you what's going on. Cheers Ken From: David Lum [mailto:david....@nwea.org] Sent: Friday, 28 May 2010 11:09 PM To: NT System Admin Issues Subject: DNS alias change, no http to alias unless FQDN I have an internal website we connect to by http://<DNSAlias<http://%3cDNSAlias>>. This morning I changed the alias to point to a new server, but while the http://FQDN of the alias works, using just http://hostname doesn't. Example: DNS alias is a CNAME of SharePointNew pointing to a host name of ServerA, and HTTP://SharePointNew.ourcompany.local works, but http://SharePointNew does not. That it would be a NetBIOS thing right? We use WINS, but I see no entry for COMMONS that would tell me something other than DNS is resolving that host name. David Lum // SYSTEMS ENGINEER NORTHWEST EVALUATION ASSOCIATION (Desk) 971.222.1025 // (Cell) 503.267.9764 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
