Re: Outlook 2003 won't verify Exchange account
From: Gary (tuffboystl_at_hotmail.com)
Date: 06/25/04
- Next message: Kevyn Pietsch[MSFT]: "RE: OWA questions"
- Previous message: David: "OWA Blank Message Body"
- In reply to: JV: "Re: Outlook 2003 won't verify Exchange account"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 25 Jun 2004 16:55:03 -0500
Hmm,
I've removed all other protocols...maybe it is the DNS...I'm just not sure
how to fix it. Our's is not very complex...pretty much the default
installation. I've looked at a few servers with a similar installation.
They all kind of react the same.
Is there some basic typical setup of DNS that I should employ?
Thanks for your help.
Gary
"JV" <jv@nospam.com> wrote in message
news:%23GJExAEWEHA.3120@TK2MSFTNGP12.phx.gbl...
> Have you got any other network protocols installed other than TCP/IP, if
so
> make sure that the bindings for TCP/IP are located before any other
> protocols. If you open the 'Network Connections' folder then select the
> 'Advanced' option from the list at the top of the window. Select 'Advanced
> Settings' from the menu. On the 'Adapters and Bindings' tab ensure that
> TCP/IP is bound first. then on the 'Provider Order' tab under 'Network
> Provider' move the MS Windows Network up to the top of the list.
>
>
> Bit off topic now but just for your info.
> If you run the NSLOOKUP command you should get a reply from the DNS server
> that shows the FQDN of the server and the IP address, this should reply
> quickly. The NSLOOKUP tool is used for querying DNS servers for instance
> after typing in NSLOOKUP you enter into a session as indicated by the >
> prompt. If you were to type the following commands:
>
> set q=mx
> set debug
> mydomain.com
>
> you should have a reply that shows the details of where the MX records for
> the mail server for the domain are set to.
> The web has plenty of info for using this command as its not a Microsoft
> specific tool.
>
> Hope that helps
>
> JV
>
>
> "Gary" <tuffboystl@hotmail.com> wrote in message
> news:uv7k0o7VEHA.2696@TK2MSFTNGP09.phx.gbl...
> > I've even tried configuring it by IP address...shouldn't that imply that
> > it's not a DNS issue?
> >
> > Thanks,
> > Gary
> >
> > "JV" <jv@nospam.com> wrote in message
> > news:ODekOO6VEHA.2408@tk2msftngp13.phx.gbl...
> > > Gary,
> > > is the DNS lookup for the server working properly? When Outlook checks
> the
> > > name of the server it will use DNS first to resolve the name. Try
> pinging
> > > the exchange server by name from a DOS box, if the reply comes back
fast
> > > then DNS is ok, if it takes about 10 seconds to start to reply, then
> > chances
> > > are that DNS has failed and its resolving the name using WINS.
> > >
> > > Is the client machine running WIndows 98? is the IP information set
via
> > DHCP
> > > or static?
> > >
> > > Remember that for a Windows 2000/2003 network to run properly DNS
should
> > be
> > > configured and tested properly, have you run the NSLOOKUP command from
> DOS
> > > to ensure that DNS is setup properly?
> > >
> > > Hope that helps.
> > >
> > > JV
> > >
> > >
> > > "Gary" <tuffboystl@hotmail.com> wrote in message
> > > news:uJdndryVEHA.3696@TK2MSFTNGP10.phx.gbl...
> > > > Is there anything I can do or check when an individual PC won't
verify
> > the
> > > > accounts on the exchange server?
> > > >
> > > > I actually have two PC's that I'm having problems with, but when I
> > create
> > > a
> > > > new profile and add Exchange Server and then try to verify that I
have
> > the
> > > > right name, I get an error saying that the Exchange server is
> > unavailable.
> > > >
> > > > Any help would be appreciated.
> > > >
> > > > Thanks,
> > > > Gary
> > > >
> > > >
> > >
> > >
> >
> >
>
>
- Next message: Kevyn Pietsch[MSFT]: "RE: OWA questions"
- Previous message: David: "OWA Blank Message Body"
- In reply to: JV: "Re: Outlook 2003 won't verify Exchange account"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
