Re: Outlook 2007 can't connect to exchange 2000
- From: "Ed Crowley [MVP]" <curspice@xxxxxxxxxx>
- Date: Thu, 4 Jun 2009 22:06:07 -0700
You have some kind of networking problem with the workstation in question, I suppose.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..
"Buttnuts" <leaderbuilder@xxxxxxxxx> wrote in message news:6ae05115-be14-4278-a828-bbf99bbb761c@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jun 4, 6:01 pm, "Ed Crowley [MVP]" <cursp...@xxxxxxxxxx> wrote:
Your problem appears to be a name resolution issue. Have you verified your
WINS and DNS settings?
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
.
"Buttnuts" <leaderbuil...@xxxxxxxxx> wrote in message
news:25f89c81-450b-4072-a568-fa109c4016b3@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jun 3, 6:59 pm, "Ed Crowley [MVP]" <cursp...@xxxxxxxxxx> wrote:
> I would look at the main shipping software.
> --
> Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
> .
> "Buttnuts" <leaderbuil...@xxxxxxxxx> wrote in message
>news:0d287e94-04a5-4020-bc48-2ac3a2417f0e@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >I have one desktop out of 20 that all of a sudden cannot connect to
> > the exchange server. This workstation happens to have our main
> > shipping software installed that has a bunch of ODBC connections
> > configured so it will be a REAL pain to 'wipe and start over'.
> > What happens is this.
> > When you try and check the configuration it says the 'name cannot be
> > resolved' when entering the Microsoft Exchange Server. This happens
> > whether I use the FQDNS name, the NetBIOS name, or the IP address.
> > The thing that stands out most for me about this problem is that the
> > error is instant. You click on the "Check Names" button - the error is
> > straight up - no delay. It is as if it isn't even trying to connect to
> > the server, the same sort of behaviour I would expect if there was a
> > firewall blocking it or something.
> > This is the only machine having this issue.
> > Things I've checked or tried.
> > No software firewalls installed.
> > Windows firewall disabled.
> > Cached, non-cached mode, doesn't matter.
> > Remove exchange and add the correct type of account.
> > Remove/rename .ost file(s)
> > The user account is valid. I am able to have that person log into
> > another machine and create an Outlook profile that works.
> > We can connect via Outlook Web Access on this machine to the account
> > and send and receive mail!
> > There are no other network issues with this machine - that I can tell.
> > All other network shares, connections and applications work.
> > I can browse to the exchange server via name in windows explorer on
> > said machine.
> > I can browser via IE and fire fox via name to mail server on said
> > machine.
> > I have put the exchange server name in both host file and in lmhost
> > file and vice versa and removed/switched etc.
> > I have re-installed the NIC drivers.
> > I have added the RPC DefConnectOpts key etc.
> > Any help would be greatly appreciated. Dying here.
> > I am ready with a big hammer.
> > Thanks
What?
The shipping software (UPS Worldship) has been on the system for
months and has not been updated.
This issue with Outlook has just occurred in the past week.
If anyone has any ideas involving XP or Outlook settings or
configurations (beyond what I have done), please let me know.
I actually have WINS installed on the DC (Win2k3 Ent.) and it is
working. As is DNS.
Like I said I can ping the Exchange server via netbios name, full dns
name, or ip.
I can browse to the mail server in windows explorer using any of the
same.
I can also do the same through an internet browser.
I can even connect to OWA via browser using either simple computer
name or full dns name.
I went to another machine today and logged in as the user I started
having issues with, opened up Outlook and was able to 'find' the mail
server and 'check' the name and create the account. Then had full
access to the mailbox.
I believe some has/is blocking Outlook specifically but cant for the
life of me find it.
I have run spyware scans (multi-vendor), AV scans(also multi-vendor),
re-applied Office 2007 SP2, gone to Windows update, re-installed the
NIC drivers, cleared out the host and lmhost files and then 're-set'
them with all network info, flushed the dns and arp cache, tried
dynamic vs. static ip (with reservation in dhcp), and all to no avail.
Think I may try re-installing XP SP3 again. I don't know. Running out
of things to try.
Any Ideas?
.
- References:
- Outlook 2007 can't connect to exchange 2000
- From: Buttnuts
- Re: Outlook 2007 can't connect to exchange 2000
- From: Ed Crowley [MVP]
- Re: Outlook 2007 can't connect to exchange 2000
- From: Buttnuts
- Re: Outlook 2007 can't connect to exchange 2000
- From: Ed Crowley [MVP]
- Re: Outlook 2007 can't connect to exchange 2000
- From: Buttnuts
- Outlook 2007 can't connect to exchange 2000
- Prev by Date: Re: Outlook 2007 can't connect to exchange 2000
- Next by Date: Re: Allow per domain relay (on send connector) like on Exchange 2003
- Previous by thread: Re: Outlook 2007 can't connect to exchange 2000
- Next by thread: Firewall and Exchange 2007 (Which is better)
- Index(es):
Relevant Pages
|
