Exchange Server

Will James · Guest

I inherited support for a company that has four remote locations
participating in an active directory domain. All PCs use WinXP fully
patched and Office 2003.

Each location has its own Win2k server running DNS and Wins.

When we took over, we had to migrate all the new users to our e-mail server,
Exchange 5.5.

They can ping our server all day long. Just for good measure I added an
entry in their DNS server, and created a host file on each machine. Pinging
and name resolution through ping is absolutely not a problem. All clients
look to their local server for DNS.

I had some problems initially. Outlook clients would get to the logon
screen and then just hang, eventually timing out with a "network problems
exchange server unavailable" error. Of course, pinging worked great. Not
sure why Outlook can't find the server.

On a whim, I removed all Outlook profiles and re-created them. I also made
enabled NetBIOS over TCP/IP on each machine. This seemed to work for a
while.

But now every machine is unable to reach the Exchange server.

I took my own machine out to one of the sites and was able to connect with
no problem.

I am convinced the problem lies with some Active Directory / Name Resolution
/ Outlook Client setting, but I can't find anything to support this theory.

Does Outlook use some special way of name resolution?

Thanks for any help. I am completely at a loss here.

Tim Hackbart [MSFT] · Guest

To be specific, Outlook queries the Exchange server for its NetworkAddress
attribute when it is created in the Check Name process. This attribute of
the Exchange server stores the RPC Protocol Names for the server, such as
ncacn_ip_tcp for RPC connections TCP-IP.
This information is then written into the clients machine registry with its
Outlook Profile Information

Go to your client machine and then Regedit
HKCU\Software\Microsoft\WindowsNT\CurrentVersion\Windows Messaging
Subsystem\Profiles\"profile name"
then look for a Ken that starts with "13dbb..."
then a REG_BINARY Value "101e6613"
You must double click on that value as the info is in Hex, the Edit Binary
Value Window will then convert it to ASCII for you.
There you should see all the ncacn... values.
Note the ncacn_ip_tcp value, as this is the preferred protocol.

Hope this helps.

--
Tim Hackbart M.C.S.E.
This posting is provided "AS IS" with no warranties, and confers no rights.

Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Will James" <wjames@willwillwilljamesjamesjames.com> wrote in message
news:csjgcb$s31@library1.airnews.net...

Transam388 · Guest

What you may also do is set a secondary zone on those clients computers that
points to your domain and recieves updates from your DNS server and do the
vice versa on your side. When going across different IP's and domains many
times DNS will be used to resolve the machine names even if they are on the
network. A secondary zone in DNS will keep the SOA start of Authority on the
primary DNS server that the domain you are creating lives on. You should
then also go ahead and create the secondary reverse lookups for the IP's of
those domains. This may sound like a lot but it is not to bad to do and will
be faster than going to each computer and editing the registry. One other to
watch for is if you are running 2000 or higher DNS that you allow either
dynamic updates or that you specify the name servers you will send updates to
and again vice versa on the other system. Again, hope this gives you some
help.

"Tim Hackbart [MSFT]" wrote:

	Exchange Server Forum Index -> Connectivity	All times are GMT
Page 1 of 1