Connecting Outlook to Exchange 2007 - STRANGE BEHAVIOR

[Jeff]

Hello,

I recently migrated from Exchange 2003 SBS to Exchange 2007. At the time
when my SBS was still up and running, I could connect an Outlook client to
Exchange without any problem.

Now, that I have retired my SBS, when I go to connect Outlook and enter the
server name and user ID it gives me a message that there is no Exchange
server or it is unavailable. It DOES however work if I use the Domain
Controller server name and it resolves to the Exchange Server and resolves
the account then everything works fine.

I know what you are thinking...it's a DNS problem right? I Don't think so,
because I can ping the IP and name of my mail server and it always comes back
correct! I looked in my DNS records to make sure there are no rouge DNS
entries for the IP Addess of my mail server and there are not. I even peform
an NSLOOKUP and it comes back FINE!

HELP What is going on here!??????

[John Oliver, Jr. [MVP]]

So are you creating a new Outlook Profile or connecting to Outlook Anywhere?
Excatly why are you needing to input the server name and user id? What
version of the Outlook Client? If you have OL2007 then run Test Email
Configuration from OL 2007.

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2008
Microsoft Certified Partner

"Jeff" <Je...@discussions.microsoft.com> wrote in message
news:B5925DB6-E980-4DD6...@microsoft.com...

[Jeff]

John,

This is connecting to an already existing Exchange mailbox.

I am using Outlook 2003. The place where I'm having a problem is when I open
up Outlook for the first time and then I go through the wizard, choosing
setup a new account, exchange, etc....

Then I get to the part where you have to put in the name of the exchange
server and the person's name. When I hit the "check name" button that's when
I get the error message that it could not connect to an exchange server or it
is not available. Then, I can input the name of my domain controller (GC) and
it resolves the name and no problems!!!!!

[John Oliver, Jr. [MVP]]

So once you input the DC name in the Server Name field it resolves? I
assume you cannot proceed with creating the OL profile and open your mailbox
since you cannot resolve to your Exchange 2007 Server? Did you create
Public Folder Store on the Exchange 2007 Server? If you are running OL2003
or earlier clients you must have a PF Store.

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2008
Microsoft Certified Partner

"Jeff" <Je...@discussions.microsoft.com> wrote in message

news:F382A198-8337-468B...@microsoft.com...

[Jeff]

Yes it will resolve if I put the DC name in the server field and when it
resolves it resolves to the MAIL SERVER name. VERY STRANGE. I just found out
that it will resolve if I enter the complete internal mail server name. This
is confusing because I've setup many exchange 2003 servers in the past and I
only had to put the server name, not the rest of the domain in. This is my
first Exchange 2007 setup.

And yes once the name resolves Outlook will open and function properly
without any problems.

Yes there is a public folder store and it is mounted. Workstations that
already had outlook 2003 installed are working fine.

BTW - OWA works great and I have no problems

[John Oliver, Jr. [MVP]]

Hmm, sounds like DNS. So when you do ping the Exchange Server does is
resolve to the FQDN?

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2008
Microsoft Certified Partner

"Jeff" <Je...@discussions.microsoft.com> wrote in message

news:D9F7F9D1-1817-42C2...@microsoft.com...

[Jeff]

It does sound like a dns issue but ping replies the correct name/address,
NSLOOKUP gives the correct reply as well. This is what is making it very
fustrating.

[John Oliver, Jr. [MVP]]

Yes, but does it resolve by FQDN, e.g., exchangeservername.yourdomain.local

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2008
Microsoft Certified Partner

"Jeff" <Je...@discussions.microsoft.com> wrote in message

news:89A4CBB9-5A60-41D0...@microsoft.com...

[zack...@comcast.net]

let me make sure i understand this correctly.

when you populate the SHORT name of the DC it resolves to the mail
server
when you populate the SHORT name of the mail server it fails
when you populate the FQDN of the mail server it works.

are you running a WINS server. since NSLookup is resolving the name
correctly it wounds like the problem is related to short name
resolution. Especially since it works if you use the FQDN and fails
with the short name.

Check your WINs server to make sure everything is okay there. Also
there is the cance that you have some bad data cached in the netbios
name cache, so try to clear that as well. use: nbtstat -R

yes the R is case sensative...

check your lmhosts and hosts file to make sure there are no entries in
there, or that the entries are correct. NSLookup actually tests the
name server, but it doesn;t check local name cache or hosts/lmhosts
file. that maybe why nslookup works fine but the process still fails.