| Author |
Message |
eceen
Guest
|
 Posted:
Thu Nov 24, 2005 5:58 pm Post subject:
Only Outlook2k unable access E2K? |
|
|
We have Exchange 2000 servers in a Windows 2003 AD domain, with Win2k/XP
clients, and mixture of Outlook 2000/2003 users.
Users can connect to their mailbox via Outlook (Either LAN or VPN) and OWA.
Recently, we encounter that some users were unable to access their mailbox
via Outlook using VPN connection only, LAN connection was fine.
Outlook 2003 users were ok, only Outlook 2000 users have this problem. But
they still can access by OWA.
No traffic seems to be blocked from the Firewall end.
The Outlook client is able to checkname, but will get time-out connecting to
the Exchange server, thus unable to open their mailbox.
The only significant change to the infrastructure was introducing new
Exchange 2003 servers into the same Administrative Group.
But all mailboxes still remains in the old Exchange 2000 servers.
Any ideas?
|
|
| Back to top |
|
 |
neo [mvp outlook]
Guest
|
| Posted:
Fri Nov 25, 2005 5:58 pm Post subject:
Re: Only Outlook2k unable access E2K? |
|
|
Based on the description, I would guess that the Outlook 2000 client is
having troubles locating the server(s) by name resolution. Have you tried
modifying the host and lmhosts files to rule out DNS/WINS name resolution
issues?
"eceen" <eceen@discussions.microsoft.com> wrote in message
news:9633B1A3-0428-4EBE-967C-23027E0B74AD@microsoft.com...
| Quote: | We have Exchange 2000 servers in a Windows 2003 AD domain, with Win2k/XP
clients, and mixture of Outlook 2000/2003 users.
Users can connect to their mailbox via Outlook (Either LAN or VPN) and
OWA.
Recently, we encounter that some users were unable to access their mailbox
via Outlook using VPN connection only, LAN connection was fine.
Outlook 2003 users were ok, only Outlook 2000 users have this problem. But
they still can access by OWA.
No traffic seems to be blocked from the Firewall end.
The Outlook client is able to checkname, but will get time-out connecting
to
the Exchange server, thus unable to open their mailbox.
The only significant change to the infrastructure was introducing new
Exchange 2003 servers into the same Administrative Group.
But all mailboxes still remains in the old Exchange 2000 servers.
Any ideas?
|
|
|
| Back to top |
|
|
eceen
Guest
|
| Posted:
Sun Nov 27, 2005 5:58 pm Post subject:
Re: Only Outlook2k unable access E2K? |
|
|
No problem pinging netbios or dns names of the DCs and Exchange servers,
though there's no lmhosts/hosts files defined.
"neo [mvp outlook]" wrote:
| Quote: | Based on the description, I would guess that the Outlook 2000 client is
having troubles locating the server(s) by name resolution. Have you tried
modifying the host and lmhosts files to rule out DNS/WINS name resolution
issues?
"eceen" <eceen@discussions.microsoft.com> wrote in message
news:9633B1A3-0428-4EBE-967C-23027E0B74AD@microsoft.com...
We have Exchange 2000 servers in a Windows 2003 AD domain, with Win2k/XP
clients, and mixture of Outlook 2000/2003 users.
Users can connect to their mailbox via Outlook (Either LAN or VPN) and
OWA.
Recently, we encounter that some users were unable to access their mailbox
via Outlook using VPN connection only, LAN connection was fine.
Outlook 2003 users were ok, only Outlook 2000 users have this problem. But
they still can access by OWA.
No traffic seems to be blocked from the Firewall end.
The Outlook client is able to checkname, but will get time-out connecting
to
the Exchange server, thus unable to open their mailbox.
The only significant change to the infrastructure was introducing new
Exchange 2003 servers into the same Administrative Group.
But all mailboxes still remains in the old Exchange 2000 servers.
Any ideas?
|
|
|
| Back to top |
|
|
neo [mvp outlook]
Guest
|
| Posted:
Mon Nov 28, 2005 1:17 am Post subject:
Re: Only Outlook2k unable access E2K? |
|
|
A ping does not test netbios name resolution. To test netbios name
resolution, one would have to use nbtstat -a <server_name> and nbtstat -A
<ip_address_of server>
"eceen" <eceen@discussions.microsoft.com> wrote in message
news:F910B8D6-D6DE-407A-92D7-DF393DBF4DD9@microsoft.com...
| Quote: | No problem pinging netbios or dns names of the DCs and Exchange servers,
though there's no lmhosts/hosts files defined.
"neo [mvp outlook]" wrote:
Based on the description, I would guess that the Outlook 2000 client is
having troubles locating the server(s) by name resolution. Have you
tried
modifying the host and lmhosts files to rule out DNS/WINS name resolution
issues?
"eceen" <eceen@discussions.microsoft.com> wrote in message
news:9633B1A3-0428-4EBE-967C-23027E0B74AD@microsoft.com...
We have Exchange 2000 servers in a Windows 2003 AD domain, with
Win2k/XP
clients, and mixture of Outlook 2000/2003 users.
Users can connect to their mailbox via Outlook (Either LAN or VPN) and
OWA.
Recently, we encounter that some users were unable to access their
mailbox
via Outlook using VPN connection only, LAN connection was fine.
Outlook 2003 users were ok, only Outlook 2000 users have this problem.
But
they still can access by OWA.
No traffic seems to be blocked from the Firewall end.
The Outlook client is able to checkname, but will get time-out
connecting
to
the Exchange server, thus unable to open their mailbox.
The only significant change to the infrastructure was introducing new
Exchange 2003 servers into the same Administrative Group.
But all mailboxes still remains in the old Exchange 2000 servers.
Any ideas?
|
|
|
| Back to top |
|
|
Dave Mills
Guest
|
| Posted:
Mon Nov 28, 2005 5:58 pm Post subject:
Re: Only Outlook2k unable access E2K? |
|
|
On Sun, 27 Nov 2005 11:17:01 -0800, "neo [mvp outlook]"
<neo@online.mvps.org> wrote:
| Quote: | A ping does not test netbios name resolution. To test netbios name
resolution, one would have to use nbtstat -a <server_name> and nbtstat -A
ip_address_of server
It does. The name is a simple Netbios name if WINS or Broadcast |
resolved the name and a FQDN if DNS resolved it.
--
Dave Mills
There are 10 type of people, those that understand binary and those that don't. |
|
| Back to top |
|
|
neo [mvp outlook]
Guest
|
| Posted:
Tue Nov 29, 2005 1:58 am Post subject:
Re: Only Outlook2k unable access E2K? |
|
|
oh jeez... and how many of us today don't list servers in dns? ;)
"Dave Mills" <News@nospam.djmills.co.uk> wrote in message
news:u5gmo15p70cs00jm39491rjn4o8kgtsrou@4ax.com...
| Quote: | On Sun, 27 Nov 2005 11:17:01 -0800, "neo [mvp outlook]"
neo@online.mvps.org> wrote:
A ping does not test netbios name resolution. To test netbios name
resolution, one would have to use nbtstat -a <server_name> and nbtstat -A
ip_address_of server
It does. The name is a simple Netbios name if WINS or Broadcast
resolved the name and a FQDN if DNS resolved it.
--
Dave Mills
There are 10 type of people, those that understand binary and those that
don't. |
|
|
| Back to top |
|
|
neo [mvp outlook]
Guest
|
| Posted:
Wed Nov 30, 2005 1:58 am Post subject:
Re: Only Outlook2k unable access E2K? |
|
|
maybe... or you are just being nice not saying i'm a pain in the tush. i
don't trust testing netbios with ping for the little difference you describe
since most don't catch it. me, i like using nbtstat to test netbios name
resolution.
"Dave Mills" <News@nospam.djmills.co.uk> wrote in message
news:h6ipo1h5t1210hh1vi2avf7scdi7n098c5@4ax.com...
| Quote: | On Mon, 28 Nov 2005 12:35:20 -0800, "neo [mvp outlook]"
neo@online.mvps.org> wrote:
oh jeez... and how many of us today don't list servers in dns? ;)
or get the client DNS settings wrong so only do Netbios lookup.
Maybe I have not understood what you are trying to test.
"Dave Mills" <News@nospam.djmills.co.uk> wrote in message
news:u5gmo15p70cs00jm39491rjn4o8kgtsrou@4ax.com...
On Sun, 27 Nov 2005 11:17:01 -0800, "neo [mvp outlook]"
neo@online.mvps.org> wrote:
A ping does not test netbios name resolution. To test netbios name
resolution, one would have to use nbtstat -a <server_name> and
nbtstat -A
ip_address_of server
It does. The name is a simple Netbios name if WINS or Broadcast
resolved the name and a FQDN if DNS resolved it.
--
Dave Mills
There are 10 type of people, those that understand binary and those that
don't.
--
Dave Mills
There are 10 type of people, those that understand binary and those that
don't. |
|
|
| Back to top |
|
|
Dave Mills
Guest
|
| Posted:
Wed Nov 30, 2005 1:58 am Post subject:
Re: Only Outlook2k unable access E2K? |
|
|
On Mon, 28 Nov 2005 12:35:20 -0800, "neo [mvp outlook]"
<neo@online.mvps.org> wrote:
| Quote: | oh jeez... and how many of us today don't list servers in dns? ;)
|
or get the client DNS settings wrong so only do Netbios lookup.
Maybe I have not understood what you are trying to test.
| Quote: |
"Dave Mills" <News@nospam.djmills.co.uk> wrote in message
news:u5gmo15p70cs00jm39491rjn4o8kgtsrou@4ax.com...
On Sun, 27 Nov 2005 11:17:01 -0800, "neo [mvp outlook]"
neo@online.mvps.org> wrote:
A ping does not test netbios name resolution. To test netbios name
resolution, one would have to use nbtstat -a <server_name> and nbtstat -A
ip_address_of server
It does. The name is a simple Netbios name if WINS or Broadcast
resolved the name and a FQDN if DNS resolved it.
--
Dave Mills
There are 10 type of people, those that understand binary and those that
don't.
-- |
Dave Mills
There are 10 type of people, those that understand binary and those that don't. |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in