Hi Jeff,
I would like to check how things are going. If you have any other
questions, please do not hesitate to let me know. I look forward to your
further updates.
Sincerely,
Emily Lin,
Microsoft Online Partner Support
Get Secure! -
www.microsoft.com/security
======================================================
PLEASE NOTE:
The newsgroup SECURE CODE and PASSWORD will be updated on August 20, 2007.
Please complete a re-registration process by entering the secure code
mmpng2007 when prompted. Once you have entered the secure code mmpng2007,
you will be able to update your profile and access the partner newsgroups.
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
--------------------
| X-Tomcat-ID: 68344097
| References: <
[email protected]>
<
[email protected]>
<
[email protected]>
<
[email protected]>
<
[email protected]>
<
[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: (e-mail address removed) (Emily Lin [MSFT])
| Organization: Microsoft
| Date: Mon, 13 Aug 2007 06:30:33 GMT
| Subject: RE: Outlook Exchange Server Name Resolution
| X-Tomcat-NG: microsoft.public.outlook.general
| Message-ID: <
[email protected]>
| Newsgroups: microsoft.public.outlook.general
| Lines: 188
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.outlook.general:64082
| NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
|
| Hi Jeff,
|
| Nice to learn that you have fixed the Outlook issue.
|
| By default Outlook 2003 will resolve the Exchange server's NetBIOS name
to
| FQDN (Fully Qualified Domain Names) name. This is different from Outlook
| 2000/2002.
|
| Related KB article.
|
| 831609 How to Change the Method That Outlook 2003 Uses to Resolve Server
| Names
|
http://support.microsoft.com/?id=831609
|
| If you have any other concerns, please don't hesitate to contact me.
|
| Regards,
|
| Emily Lin
|
| Microsoft Online Partner Support
| Get Secure! -
www.microsoft.com/security
| ====================================================
| When responding to posts, please "Reply to Group" via your newsreader so
| that others may learn and benefit from your issue.
| ====================================================
| This posting is provided "AS IS" with no warranties, and confers no
rights.
|
|
|
|
| --------------------
| | Thread-Topic: Outlook Exchange Server Name Resolution
| | thread-index: AcfbsHAbI/oUNlaIT0a+vZtX49dwBg==
| | X-WBNR-Posting-Host: 207.46.192.207
| | From: =?Utf-8?B?SkU=?= <
[email protected]>
| | References: <
[email protected]>
| <
[email protected]>
| <
[email protected]>
| <
[email protected]>
| <
[email protected]>
| | Subject: RE: Outlook Exchange Server Name Resolution
| | Date: Fri, 10 Aug 2007 17:42:04 -0700
| | Lines: 123
| | Message-ID: <
[email protected]>
| | MIME-Version: 1.0
| | Content-Type: text/plain;
| | charset="Utf-8"
| | Content-Transfer-Encoding: 7bit
| | X-Newsreader: Microsoft CDO for Windows 2000
| | Content-Class: urn:content-classes:message
| | Importance: normal
| | Priority: normal
| | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| | Newsgroups: microsoft.public.outlook.general
| | Path: TK2MSFTNGHUB02.phx.gbl
| | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.outlook.general:63812
| | NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| | X-Tomcat-NG: microsoft.public.outlook.general
| |
| | Kathleen,
| | Thanks for your help!
| | I found the problem. THe DNS Server was set to Listen on All
Interfaces,
| | which included the PPP Adapter for RAS at 192.168.16.59. When I changed
| the
| | setting to Listen On: "Only the following IP addresses" and removed
| | 192.168.16.59 leaving 192.168.16.2, everything worked fine.
| |
| | My Outlook problem cleared up, I was able to remove the line from the
| HOSTS
| | file pointing to 192.168.16.2 and all of the pings succeeded and the
name
| | resolved to the correct address.
| |
| | In addition, the MPSREPORT_Network diagnostics no longer had the
| anomalies
| | in the DNS Section that I listed in the post.
| |
| | My question now is, with the entry in the HOSTS file, why was Outlook
| still
| | querying DNS to resolve the Exchange server name? I understand now why
it
| | would succeed after the rery. It was as I originaly expected, it was
| querying
| | 192.168.16.59, timing out, then querying 192.168.16.2 after the retry.
| But,
| | why was it going to DNS in the first place?
| |
| | Please let me know your thoughts.
| |
| | Thanks!
| | --
| | JE
| |
| |
| | "JE" wrote:
| |
| | > I've posted a question in the DNS newsgroup as well, but what appears
| to be
| | > happening is that the DNS Server has two IP's, one static, the other
| for use
| | > with RRAS and assigned through DHCP.
| | >
| | > When Outlook queries the DNS for the server address, it Queries the
DNS
| | > Server using the address that is used by RRAS. Since these particular
| | > workstations that are having the problem are on the same network as
the
| | > "Real" address for the DNS Server, and are not connected via VPN,
this
| | > address doesn't work and times out. When you hit retry, however,
| Outlook
| | > knows it was unable to reach the DNS server at the first IP, so it
| tries the
| | > second and succeeds.
| | >
| | > I've already added the correct entry to the HOSTS file, as well as
| LMHOSTS
| | > and all pings etc... work. I did notice that even if I put the
correct
| IP in
| | > for the Exchange Server when setting up a new Outlook Profile, it
| converts it
| | > to the FQDN of the server. Sometimes this conversion triggers the
same
| | > Exchange Server Unavailable message with the Retry option. If the
Retry
| | > Option is used, it resolves and allows you to continue.
| | >
| | > I used the /RPCDIAG switch starting Outlook to observe what was
| happening
| | > when the problem occurred. To start, when it was in the Connecting
| Status,
| | > the server name was displayed in FQDN, but after it connected it
| changed to
| | > just server name. I thought that that was odd.
| | >
| | > After the connection timed out and required me to hit retry, the RPC
| status
| | > window had the following entries:
| | >
| | > Type - Directory, Conn - TCP/IP, REQ/Fail - 2/1, Avg. Response - 16
| | > Type - Mail, Conn - TCP/IP, REQ/Fail - 106/1, Avg. Response - 2
| | > Type - Directory, Conn - TCP/IP, REQ/Fail - 2/1, Avg. Response - 0
| | >
| | > I'm concerned about the numbers in the REQ/Fail column, but haven't
| been
| | > able to find a description of what they mean yet.
| | >
| | > Thanks
| | >
| | > --
| | > JE
| | >
| | >
| | > "K. Orland" wrote:
| | >
| | > > As far as I know, Outlook locates the Exchange server by hostname
and
| uses
| | > > the transport that is provided to communicate. If Outlook can't
find
| the
| | > > Exchange server by name then normally it can't communicate even if
| the
| | > > transport is available. Say you have a LAN connection and fail to
| provide
| | > > either a HOSTS file, WINS, or DNS you'll likely find that you may
be
| able to
| | > > ping the Exchange server but not transfer mail. DNS is what is
| normally used
| | > > for local clients. For those idrtd who have to travel and use VPN
or
| RAS
| | > > (old), in addition you would want to add the entries to your HOSTS
| file.
| | > >
| | > > --
| | > > Kathleen Orland - MVP Outlook
| | > >
| | > >
http://www.howto-outlook.com/
| | > >
| | > >
| | > >
| | > > "JE" wrote:
| | > >
| | > > > No, sorry no router. There may be DNS issues though, that's why I
| was
| | > > > wondering how Outlook resolved the names.
| | > > > --
| | > > > JE
| | > > >
| | > > >
| | > > > "K. Orland" wrote:
| | > > >
| | > > > > Is there a router between you and the Exchange server? I've
seen
| this happen
| | > > > > when the polling times out.
| | > > > >
| | > > > > --
| | > > > > Kathleen Orland - MVP Outlook
| | > > > >
| | > > > >
http://www.howto-outlook.com/
| | > > > >
| | > > > >
| | > > > >
| | > > > > "JE" wrote:
| | > > > >
| | > > > > > How does Outlook 2003 resolve the Microsoft Exchange server
| name?
| | > > > > >
| | > > > > > I'm having a problem when starting Outlook where a dialog box
| appears and
| | > > > > > says that the Exchange Server is unavailable with Work
Offline,
| Cancel and
| | > > > > > Retry Options.
| | > > > > >
| | > > > > > When you select Retry, the connection goes through. The
| Exchange Server is
| | > > > > > SBS 2003, and all other connections work without problems. I
| ran
| | > > > > > MPSRPT_Network and found some inconsistencies in the DNS
| section, everything
| | > > > > > else looked OK.
| | > > > > >
| | > > > > > Thanks.
| | > > > > > --
| | > > > > > JE
| |
|
|
