[ExchangeList] Re: Outlook unable to logon to Exchange

  • From: Sture Lygren <sture@xxxxxxxxxxxxxx>
  • To: exchangelist@xxxxxxxxxxxxx
  • Date: Tue, 23 May 2006 15:06:38 +0200

http://www.msexchange.org
-------------------------------------------------------No TCP/IP Port Value 
there. So - what next?

Sture

Foote, Eric wrote:
> http://www.msexchange.org
> -------------------------------------------------------Stu,
> Check HKLM\System\CCS\Services\MSExchangeIS\ParametersSystem 
> 
> See if you have a TCP/IP Port Value.
> 
> Eric
> 
> -----Original Message-----
> From: exchangelist-bounce@xxxxxxxxxxxxx
> [mailto:exchangelist-bounce@xxxxxxxxxxxxx]On Behalf Of Sture Lygren
> Sent: Tuesday, May 23, 2006 2:23 AM
> To: exchangelist@xxxxxxxxxxxxx
> Subject: [ExchangeList] Outlook unable to logon to Exchange
> 
> 
> http://www.msexchange.org
> -------------------------------------------------------Hi,
> 
> Situation:
> 
> We have an Exchange 2003 Enterprise server on a Windows 2003 server
> acting as PDC (not an ideal solution I know, but beeing a small org I
> guess the server will handle the load just fine).
> 
> Problem:
> 
> Outlook clients cannot connect to the exchange server if the machine is
> not part of the domain housing the exchange server.
> 
> Is there a smart fix for this?
> 
> Thanks in advance!
> 
> Sture

-- 
Sture Lygren
Computer Systems Administrator
Andoya Rocket Range
Work: +4776144451 / Fax: +4776144401
-------------------------------------------------------
List Archives: http://www.freelists.org/archives/exchangelist/  
MSExchange Newsletter: http://www.msexchange.org/pages/newsletter.asp 
MSExchange Articles and Tutorials: 
http://www.msexchange.org/articles_tutorials/ 
MSExchange Blogs: http://blogs.msexchange.org/ 
-------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com 
-------------------------------------------------------
To unsubscribe visit http://www.msexchange.org/pages/exchangelist.asp
Report abuse to listadmin@xxxxxxxxxxxxxx 

Other related posts: