Exchange Server Forums

Event ID 1706 on exchange 2000 server

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2000] >> Server Security >> Event ID 1706 on exchange 2000 server

Page: [1]

Message

<< Older Topic Newer Topic >>

Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM

TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!

Event ID 1706 on exchange 2000 server - 18.Mar.2002 5:10:00 PM

siavashm

Posts: 1
Joined: 18.Mar.2002
From: Toronto, Canada
Status: offline

x2k server is running on a w2k domain controller. users are on a separate NT40 domain and use POP3 and SMTP protocol to access the mail server.
we see the following warning in application log on exchange server 2000(x2K server). i can also see a corresponding logon failure in the security log.

Category: SMTP Protocol
Event: 1706
Source: MSExchangeTransport
EXPS is temporarily unable to provide protocol security with "workstation1". "CSessionContext::OnEXPSInNegotiate" called "HrServerNegotiateAuth" which failed with error code 0x8009030c ( i:\transmt\src\smtpsink\exps\expslib\context.cpp@1462 ).

if you know anything about this problem please send me a note.
Thanks, Siavash.

Post #: 1

Featured Links*

RE: Event ID 1706 on exchange 2000 server - 21.Mar.2002 11:49:00 AM

10dago

Posts: 3
Joined: 20.Mar.2002
From: xxx
Status: offline

I have Event ID 1706 + 1707
My Description of Event ID 1707 says "EXPS is temporarily uable to provide protocol security. This is usually due to DS network problems or low system resources ..."

I can reproduce this when an exchange 5.5 tries to send mails to my exchange 2000 server.

dagmar

(in reply to siavashm)

Post #: 2