|
|
Here is the situation:
The domain controller was configured by somebody else, w2k3 with all Sp's.
I had to install exchange 2003 on that server.
The installation went fine, and exchange is working perfect ....BUT
The webmail is working fine, but the communication between exchange and
Outlook is a problem.
When I configure outlook to use exchange, and when i click on 'check name',
the DNS resolving is already slow, but it resolves .... .
Then, when I want to start outlook it says (on all clients) that there is no
communication possible with the Exchange server and outlook shuts down.
Things I've already done:
- rejoined a client to the domain .... already errors and DNS problems (the
domain dropdownbox on logon took ages to come up ...)
- uninstalled Norton, disabled win firewall rejoined the pc again, dns seems
fine now (dropdown box comes up fast now)
- there are still errors on the clients:
source: NETLOGON
event-ID: 5719
the is no domain controller available for the domain xxx
there are no logon servers available ....
another one:
source: DCOM
event-ID: 10006
user: NT AUTHORITY\SYSTEM
DCOM got the following error :'De RPC-server is not available. ' from the
computer Server.xxx.local during activation of the server
{D99E6E74-FC88-11D0-B498-00A0C90312F3}
So it seems like a basic communication problem with the AD and the DC, but
which one .......... .
I am mostly concerned about the communication problem between the outlook
client and the exchange server, although the other client errors could be
related to the same problem.
Can anybody help me on this one?
|
|
Hello Thomas,
Sounds like DNS problem. Please post an unedited ipconfig /all from the DC
and one problem client.
Running Exchange on Domain controllers is a not recommended configuration.
Exchange should always run on member servers because of performance reason.
Make sure that the DC is Global catalog server.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
[Quoted Text] > Here is the situation:
>
> The domain controller was configured by somebody else, w2k3 with all
> Sp's. I had to install exchange 2003 on that server.
>
> The installation went fine, and exchange is working perfect ....BUT
> The webmail is working fine, but the communication between exchange
> and
> Outlook is a problem.
> When I configure outlook to use exchange, and when i click on 'check
> name',
> the DNS resolving is already slow, but it resolves .... .
> Then, when I want to start outlook it says (on all clients) that there
> is no
> communication possible with the Exchange server and outlook shuts
> down.
> Things I've already done:
>
> - rejoined a client to the domain .... already errors and DNS problems
> (the
> domain dropdownbox on logon took ages to come up ...)
> - uninstalled Norton, disabled win firewall rejoined the pc again, dns
> seems
> fine now (dropdown box comes up fast now)
> - there are still errors on the clients:
> source: NETLOGON
> event-ID: 5719
> the is no domain controller available for the domain xxx
> there are no logon servers available ....
> another one:
>
> source: DCOM
> event-ID: 10006
> user: NT AUTHORITY\SYSTEM
> DCOM got the following error :'De RPC-server is not available. ' from
> the
> computer Server.xxx.local during activation of the server
> {D99E6E74-FC88-11D0-B498-00A0C90312F3}
> So it seems like a basic communication problem with the AD and the DC,
> but which one .......... .
>
> I am mostly concerned about the communication problem between the
> outlook client and the exchange server, although the other client
> errors could be related to the same problem.
>
> Can anybody help me on this one?
>
|
|
This is some more info:
Ipconfig server (it's a dutch one, I hate translated OS, but it wasn't my
setup :p)
Windows IP-configuratie
Hostnaam . . . . . . . . . . . . : Server
Primair DNS-achtervoegsel. . . . .: xxx.local
Knooppunttype . . . . . . . . . . : hybride
IP-routering ingeschakeld. . . . .: nee
WINS-proxy ingeschakeld . . . . . : nee
DNS-achtervoegselzoeklijst. . . . : xxx.local
Ethernet-adapter LAN-verbinding:
Verbindingsspec. DNS-achtervoegsel:
Beschrijving . . . . . . . . . . .: Intel(R) PRO/1000 EB Network
Connection
ith I/O Acceleration
Fysiek adres. . . . . . . . . . . : 00-15-17-5E-5F-FC
DHCP ingeschakeld:. . . . . . . . : nee
IP-adres. . . . . . . . . . . . . : 192.168.0.1
Subnetmasker. . . . . . . . . . . : 255.255.255.0
Standaard-gateway . . . . . . . . : 192.168.0.254
DNS-servers . . . . . . . . . . . : 192.168.0.1
Ipconfig client:
Windows IP-configuratie
Host-naam . . . . . . . . . . . .: DRIVE
Primair DNS-achtervoegsel. . . . .: xxx.local
Knooppunttype . . . . . . . . . . : hybride
IP-routering ingeschakeld. . . . .: nee
WINS-proxy ingeschakeld . . . . . : nee
DNS-achtervoegselzoeklijst. . . . : xxx.local
Ethernet-adapter LAN-verbinding:
Verbindingsspec. DNS-achtervoegsel:
Beschrijving . . . . . . . . . . .:
SiS 900 PCI Fast Ethernet Adapter
Fysiek adres. . . . . . . . . . . : 00-0A-E6-6C-A1-71
DHCP ingeshakeld. . . . . . . . . : ja
Autom. configuratie ingeschakeld. : ja
IP-adres. . . . . . . . . . . . . : 192.168.0.103
Subnetmasker. . . . . . . . . . . : 255.255.255.0
Standaardgateway. . . . . . . . . : 192.168.0.254
DHCP-server . . . . . . . . . . . : 192.168.0.1
DNS-servers . . . . . . . . . . . : 192.168.0.1
Primaire WINS-server. . . . . . . : 192.168.0.1
----------------------------------------
WINS is running on the DC (which is btw the only server and DC on the
domain) and is displaying the server correctly I assume:
server.xxx.local [192.168.0.1]
-----------------------------------------
dcdiag /fix results:
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Standaard-eerste-site\SERVER
Starting test: Connectivity
......................... SERVER passed test Connectivity
Doing primary tests
Testing server: Standaard-eerste-site\SERVER
Starting test: Replications
......................... SERVER passed test Replications
Starting test: NCSecDesc
......................... SERVER passed test NCSecDesc
Starting test: NetLogons
......................... SERVER passed test NetLogons
Starting test: Advertising
......................... SERVER passed test Advertising
Starting test: KnowsOfRoleHolders
......................... SERVER passed test KnowsOfRoleHolders
Starting test: RidManager
......................... SERVER passed test RidManager
Starting test: MachineAccount
......................... SERVER passed test MachineAccount
Starting test: Services
......................... SERVER passed test Services
Starting test: ObjectsReplicated
......................... SERVER passed test ObjectsReplicated
Starting test: frssysvol
......................... SERVER passed test frssysvol
Starting test: frsevent
......................... SERVER passed test frsevent
Starting test: kccevent
......................... SERVER passed test kccevent
Starting test: systemlog
......................... SERVER passed test systemlog
Starting test: VerifyReferences
......................... SERVER passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : xxx
Starting test: CrossRefValidation
......................... xxx passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... xxx passed test CheckSDRefDom
Running enterprise tests on : xxx.local
Starting test: Intersite
......................... xxx.local passed test Intersite
Starting test: FsmoCheck
......................... xxx.local passed test FsmoCheck
netdiag /fix results:
Computer Name: SERVER
DNS Host Name: Server.xxx.local
System info : Microsoft Windows Server 2003 R2 (Build 3790)
Processor : x86 Family 6 Model 23 Stepping 6, GenuineIntel
List of installed hotfixes :
KB924667-v2
KB925398_WMP64
KB925902
KB926122
KB927891
KB929123
KB930178
KB931784
KB932168
KB933729
KB933854
KB935839
KB935840
KB936021
KB936357
KB936782
KB938127-IE7
KB938464
KB941569
KB941693
KB942830
KB942831
KB943055
KB943460
KB943485
KB944338-v2
KB944653
KB945553
KB946026
KB948496
KB948590
KB948745
KB949014
KB950762
KB950974
KB951066
KB951072-v2
KB951698
KB951746
KB951748
KB952954
KB953838-IE7
KB953839
KB954211
KB956391
KB956803
KB956841
KB957095
KB958644
Q147222
Netcard queries test . . . . . . . : Passed
[WARNING] The net card 'RAS Async-adapter' may not be working because it
has
not received any packets.
GetStats failed for 'Direct parallel'. [ERROR_NOT_SUPPORTED]
[WARNING] The net card 'WAN-minipoort (PPTP)' may not be working because
it
has not received any packets.
[WARNING] The net card 'WAN-minipoort (PPPOE)' may not be working
because it
has not received any packets.
[WARNING] The net card 'WAN-minipoort (IP)' may not be working because
it ha
s not received any packets.
[WARNING] The net card 'WAN-minipoort (Network Monitor)' may not be
working
because it has not received any packets.
GetStats failed for 'WAN-minipoort (L2TP)'. [ERROR_NOT_SUPPORTED]
Per interface results:
Adapter : LAN-verbinding
Netcard queries test . . . : Passed
Host Name. . . . . . . . . : Server
IP Address . . . . . . . . : 192.168.0.1
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.0.254
Dns Servers. . . . . . . . : 192.168.0.1
AutoConfiguration results. . . . . . : Passed
Default gateway test . . . : Passed
NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenge
r Service', <20> 'WINS' names is missing.
WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.
Global results:
Domain membership test . . . . . . : Passed
NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{06AA48D2-116E-4808-860A-D84E014C2AE0}
1 NetBt transport currently configured.
Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Passed
NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation
Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.
Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server
'192.168.0.1'
..
Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{06AA48D2-116E-4808-860A-D84E014C2AE0}
The redir is bound to 1 NetBt transport.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{06AA48D2-116E-4808-860A-D84E014C2AE0}
The browser is bound to 1 NetBt transport.
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Passed
Trust relationship test. . . . . . : Skipped
Kerberos test. . . . . . . . . . . : Passed
LDAP test. . . . . . . . . . . . . : Passed
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
No active remote access connections.
Modem diagnostics test . . . . . . : Failed
[FATAL] Cannot initialize TAPI. Failed with error(0x80000048).
IP Security test . . . . . . . . . : Skipped
------------------------------------------------------
on a client:
nslookup 192.168.0.1
*** Can't find server name for address 192.168.0.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.1
*** UnKnown can't find 192.168.0.1: Non-existent domain
-------------------------------
ping server
Pingen naar Server.xxx.local [192.168.0.1] met 32
Antwoord van 192.168.0.1: bytes=32 tijd<1 ms TTL=128
Antwoord van 192.168.0.1: bytes=32 tijd<1 ms TTL=128
Antwoord van 192.168.0.1: bytes=32 tijd<1 ms TTL=128
Antwoord van 192.168.0.1: bytes=32 tijd<1 ms TTL=128
and on the server:
nslookup 127.0.0.1
*** cannot find servername for the address 192.168.0.1 :
Non-existent domain
Server: UnKnown
Address: 192.168.0.1
Naam: localhost
Address: 127.0.0.1
-------------------------------------------------------------
on a client:
nslookup 192.168.0.1
*** Can't find server name for address 192.168.0.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.1
*** UnKnown can't find 192.168.0.1: Non-existent domain
-------------------------------
ping server
Pingen naar Server.xxx.local [192.168.0.1] met 32
Antwoord van 192.168.0.1: bytes=32 tijd<1 ms TTL=128
Antwoord van 192.168.0.1: bytes=32 tijd<1 ms TTL=128
Antwoord van 192.168.0.1: bytes=32 tijd<1 ms TTL=128
Antwoord van 192.168.0.1: bytes=32 tijd<1 ms TTL=128
and on the server:
nslookup 127.0.0.1
*** cannot find servername for the address 192.168.0.1 :
Non-existent domain
Server: UnKnown
Address: 192.168.0.1
Naam: localhost
Address: 127.0.0.1
--------------------------------------------------
and in debug mode I'm getting these results:
[Quoted Text] > set debug
> xxx.local
Server: UnKnown
Address: 192.168.0.1
------------
Got answer:
HEADER:
opcode = QUERY, id = 2, rcode = NXDOMAIN
header flags: response, auth. answer, want recursion, recursion
avail.
questions = 1, answers = 0, authority records = 1, additional = 0
QUESTIONS:
xxx.local.xxx.local, type = A, class = IN
AUTHORITY RECORDS:
-> xxx.local
ttl = 3600 (1 hour)
primary name server = server.xxx.local
responsible mail addr = hostmaster
serial = 246
refresh = 900 (15 mins)
retry = 600 (10 mins)
expire = 86400 (1 day)
default TTL = 3600 (1 hour)
------------
------------
Got answer:
HEADER:
opcode = QUERY, id = 3, rcode = NOERROR
header flags: response, auth. answer, want recursion, recursion
avail.
questions = 1, answers = 1, authority records = 0, additional = 0
QUESTIONS:
xxx.local, type = A, class = IN
ANSWERS:
-> xxx.local
internet address = 192.168.0.1
ttl = 600 (10 mins)
------------
Name: xxx.local
Address: 192.168.0.1
---------------------------------------------------------
one thing I forgot to mention .... .
There was an error in the DNS logs on the server, but I forgot to save it
..... .
It was smth with .... there is an error in active directory .... .
Stupid me I forgot to write it down :/
This error doesn't return, but when it was there there were some logon
problems also ... .
I hope there is no AD corruption or smth like that .... .
Any other ideas on how to troubleshoot this issue?
"Thomas De Smet" <xxx[ at ]xxx.com> wrote in message
news:D9444CEF-5FA0-43C6-B538-4CF271F3B183[ at ]microsoft.com...
> Here is the situation:
>
> The domain controller was configured by somebody else, w2k3 with all Sp's.
> I had to install exchange 2003 on that server.
>
> The installation went fine, and exchange is working perfect ....BUT
> The webmail is working fine, but the communication between exchange and
> Outlook is a problem.
>
> When I configure outlook to use exchange, and when i click on 'check
> name', the DNS resolving is already slow, but it resolves .... .
> Then, when I want to start outlook it says (on all clients) that there is
> no communication possible with the Exchange server and outlook shuts down.
>
> Things I've already done:
>
> - rejoined a client to the domain .... already errors and DNS problems
> (the domain dropdownbox on logon took ages to come up ...)
> - uninstalled Norton, disabled win firewall rejoined the pc again, dns
> seems fine now (dropdown box comes up fast now)
> - there are still errors on the clients:
>
> source: NETLOGON
> event-ID: 5719
> the is no domain controller available for the domain xxx
> there are no logon servers available ....
>
> another one:
>
> source: DCOM
> event-ID: 10006
> user: NT AUTHORITY\SYSTEM
> DCOM got the following error :'De RPC-server is not available. ' from the
> computer Server.xxx.local during activation of the server
> {D99E6E74-FC88-11D0-B498-00A0C90312F3}
>
> So it seems like a basic communication problem with the AD and the DC, but
> which one .......... .
>
> I am mostly concerned about the communication problem between the outlook
> client and the exchange server, although the other client errors could be
> related to the same problem.
>
> Can anybody help me on this one?
>
>
|
|
Hello Meinolf,
the reverse lookup zone was already created, it looks fine.
Non errors at all.
Al records and ip's are there.
"Thomas De Smet" <xxx[ at ]xxx.com> wrote in message
news:D9444CEF-5FA0-43C6-B538-4CF271F3B183[ at ]microsoft.com...
[Quoted Text] > Here is the situation:
>
> The domain controller was configured by somebody else, w2k3 with all Sp's.
> I had to install exchange 2003 on that server.
>
> The installation went fine, and exchange is working perfect ....BUT
> The webmail is working fine, but the communication between exchange and
> Outlook is a problem.
>
> When I configure outlook to use exchange, and when i click on 'check
> name', the DNS resolving is already slow, but it resolves .... .
> Then, when I want to start outlook it says (on all clients) that there is
> no communication possible with the Exchange server and outlook shuts down.
>
> Things I've already done:
>
> - rejoined a client to the domain .... already errors and DNS problems
> (the domain dropdownbox on logon took ages to come up ...)
> - uninstalled Norton, disabled win firewall rejoined the pc again, dns
> seems fine now (dropdown box comes up fast now)
> - there are still errors on the clients:
>
> source: NETLOGON
> event-ID: 5719
> the is no domain controller available for the domain xxx
> there are no logon servers available ....
>
> another one:
>
> source: DCOM
> event-ID: 10006
> user: NT AUTHORITY\SYSTEM
> DCOM got the following error :'De RPC-server is not available. ' from the
> computer Server.xxx.local during activation of the server
> {D99E6E74-FC88-11D0-B498-00A0C90312F3}
>
> So it seems like a basic communication problem with the AD and the DC, but
> which one .......... .
>
> I am mostly concerned about the communication problem between the outlook
> client and the exchange server, although the other client errors could be
> related to the same problem.
>
> Can anybody help me on this one?
>
>
|
|
In news:D504B5C0-A900-406A-AF9D-83F2A359B2EA[ at ]microsoft.com,
Thomas De Smet <xxx[ at ]xxx.com> requesting assistance, typed the following:
[Quoted Text] > Hello Meinolf,
>
>
> the reverse lookup zone was already created, it looks fine.
> Non errors at all.
> Al records and ip's are there.
>
If the reverse zone exists, then nslookup will not give you an error when it
initializes with the following error message:
---------------------------
nslookup 127.0.0.1
*** cannot find servername for the address 192.168.0.1 :
Non-existent domain
Server: UnKnown
Address: 192.168.0.1
Naam: localhost
Address: 127.0.0.1
---------------------------
It's looking for a reverse entry for 192.168.0.1 in the reverse zone
192.168.0.0/24. Therefore, this means that there is either no reverse zone
for 192.168.0.0/24, or the reverse zone was not created correctly.
Also, if 192.168.0.1 is a WINS server, the WINS server MUST BE a client of
itself in order to register itself as the owner of all records on that
server. Please add itself in it's IP properties.
Curious, how did you enter the name of the Exchange server in the Outlook
profile setup? By FQDN or by single name?
Is there a duplicate entry, or an APIPA entry for the server's name in DNS?
Also, keep in mind, and I'm sure you don't want to hear this now, but it's
not recommended to install Exchange on a DC for a number of reasons. One is
performance, the other is a DC will automatically disable write-cache on the
drive controller. This is to save any possible corruption with the AD
database, but Exchange's database engine is different and the write cache is
actually an asset. No, if you try to change it on a DC, because it is a DC,
it will change itself back.
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT
Microsoft Certified Trainer
For urgent issues, you may want to contact Microsoft PSS directly.
Please check http://support.microsoft.com for regional support phone
numbers.
|
|
Thomas, this is going to be third time you will hear the same thing (-:
installing exchange on a domain controller is *** no, no, no for many
reasons, obvious one is the performance and unhappy clients and more work for
you. Complicating scenarios in such will make clients and business suffer in
my opinion.
Anyway the way Exchange application is build by design, will consume all
memory resources for instance ( Store.exe) and will let even your OS (
windows 2003) or your DC’s Lsas.exe not being so happy up front may cause
replication problems and lookup problems and performance problem soon or
later.
For future references please do not install exchange on a domain controller
“Since domain controllers busy they authenticate users, they deal with (.dit)
database and they don’t like sharing their resources with any other
applications as well as exchange.
In your case they even do more, they are GCs, WINS and who knows if you
have other services turned on.
Now for your outlook slowness problem let’s focus on the statement you made
“Communication between exchange and Outlook is a problem.â€
When you configure exchange for a client from outlook for the name of your
exchange servers and client name window on the setup, you can put there the
name of your domain controller instead of your exchange server.
This will trigger quick look up for the user mailbox location process the
request will go to AD database and locate the user object, and the attribute
called “ExchangeHomeDB†will be located and the name of the exchange server
will be placed into the outlook setup quickly.
Before I speculate more the problem can you please post some of the event
logs from your exchange server (application logs) if there is anything
interesting.
General questions I would ask
Does outlook client closes up on all the workstations? Try multiple
workstations and make sure this is not client side issue as wrong link speed
on the NIC, or bad switch etc.
Open outlook from one of the client with outlook /RPCdiag and observe the
window to see where outlook application is trying to connect?
As it was suggested before Since you have the exchange and DC/GC on the same
box this will generate stress on the DC and exchange lookup ups might be the
problem, poor performance from DC/GC to the exchange will cause slowness.
Are you seeing any errors “ Outlook is retrieving data from exchange serverâ€
the famous Christmas Balloon
Check this article it might give you an idea how outlook works
http://smtp25.blogspot.com/2007/05/outlook-is-retrieving-data-from_23.html
Remember
The server that Outlook queries for this information is either a “Microsoft
Exchange Server†or “Global catalog server†which is same box in your case
If the server name appears as a NetBIOS name, the data is being retrieved
from an Exchange Server computer. If the server name appears as a fully
qualified domain name (FQDN), the data is being retrieved from a global
catalog server.
You may have to turn on some of the performance counter on the exchange
server to indentify the bottleneck
On the bottom of this article
Troubleshoot performance issues
Physical disk ( all instance)
Avg Disk Sec/Read
Avg Disk Sec/Write
Current Disk Queue Length
MSExchangeIS
RPC Averaged Latency
RPC Requests
RPC Operations/Sec
Finally
Typically, it is a good idea for the RPC Requests counter to be lower than
10.
If it is higher than 25, this is an indicator of a resource bottleneck.
Only 100 requests can be handled at the same time.
If the RPC Requests reach 100, the client will experience refused connections
The recommended values for the Avg Disk Sec/Read counter and for the Avg
Disk Sec/Write disk counter are as follows:
Good < 20 msec
Fair < 30 msec
Poor < 40 msec
Cache/Exec < 1 msec
Cache/Good < 2 msec
Cache/Fair < 4 msec
You need to spent time to identify all these and come up with conclusion
Good luck
Oz
--
Oz Ozugurlu
MVP (Exchange)
MCITP (EMA), MCITP (EA),MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +
oz[ at ]SMTp25.org
http://smtp25.blogspot.com (Blog)
"Thomas De Smet" wrote:
[Quoted Text] > Here is the situation:
>
> The domain controller was configured by somebody else, w2k3 with all Sp's.
> I had to install exchange 2003 on that server.
>
> The installation went fine, and exchange is working perfect ....BUT
> The webmail is working fine, but the communication between exchange and
> Outlook is a problem.
>
> When I configure outlook to use exchange, and when i click on 'check name',
> the DNS resolving is already slow, but it resolves .... .
> Then, when I want to start outlook it says (on all clients) that there is no
> communication possible with the Exchange server and outlook shuts down.
>
> Things I've already done:
>
> - rejoined a client to the domain .... already errors and DNS problems (the
> domain dropdownbox on logon took ages to come up ...)
> - uninstalled Norton, disabled win firewall rejoined the pc again, dns seems
> fine now (dropdown box comes up fast now)
> - there are still errors on the clients:
>
> source: NETLOGON
> event-ID: 5719
> the is no domain controller available for the domain xxx
> there are no logon servers available ....
>
> another one:
>
> source: DCOM
> event-ID: 10006
> user: NT AUTHORITY\SYSTEM
> DCOM got the following error :'De RPC-server is not available. ' from the
> computer Server.xxx.local during activation of the server
> {D99E6E74-FC88-11D0-B498-00A0C90312F3}
>
> So it seems like a basic communication problem with the AD and the DC, but
> which one .......... .
>
> I am mostly concerned about the communication problem between the outlook
> client and the exchange server, although the other client errors could be
> related to the same problem.
>
> Can anybody help me on this one?
>
>
|
|
In news:C01B0AF8-5B92-415B-993D-5369120F2463[ at ]microsoft.com,
oz.ozugurlu <ozozugurlu[ at ]discussions.microsoft.com> requesting assistance,
typed the following:
[Quoted Text] > Thomas, this is going to be third time you will hear the same thing
> (-: installing exchange on a domain controller is *** no, no, no for
> many reasons, obvious one is the performance and unhappy clients and
> more work for you. Complicating scenarios in such will make clients
> and business suffer in my opinion.
>
<snipped>
Excellent post, Oz!!
Ace
|
|
|