Test failed in netdiag.exe

S

Steven T

We are running a MS Exchange Server 2000 in a Windows 2000 Native Domain.
Recently, we've changed the network topology and once this is set up,
clients are experiencing problems using outlook to connect to
Exchange. Clients using Outlook regularly receive prompts saying that
"Outlook is retrieving data from the Microsoft Exchange Server MAIL. You can
cancel the request or minimize this message to the Windows taskbar until
Outlook
closes the message automatically" I know this may be caused by RPC delays.

The original site has 2 subnets A and B. The DC, GC, Exchange Server and
most
clients reside on Subnet A. Then we carry out the change. We've created a
new
Subnet C and Exchange server is the only computer in that subnet. Other DC
and
clients remains unchanged.

I ran the netdiag.exe on the Exchange server and found that the following
test failed.

Redir and Browser test . . . . . . : Failed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{A762B705-7D98-45B0-926F-FEB19BB916CE}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{A762B705-7D98-45B0-926F-FEB19BB916CE}
The browser is bound to 1 NetBt transport.
[FATAL] Cannot send mailslot message to
'\\MYDOMAIN*\MAILSLOT\NET\NETLOGON' vi
a redir. [ERROR_BAD_NETPATH]

In the System Event log, I occationally receive error logs of event id 5783
The event source is from NETLOGON
Description:
The session setup to the Windows NT or Windows 2000 Domain Controller
\\dc1.mydomain.com for the domain MYDOMAIN is not responsive. The
current RPC call from Netlogon on \\MAIL to \\dc1.mydomain.com has been
cancelled.

Sometimes it's saying DC1 is not reponsive, sometimes it's saying DC2 is not
reponsive. I don't know if this is related to the Outlook delay problem we
experience. Also, I am not sure about the cause of this. Is it a Network
problem
or I have to tweak with the AD or Exchange server to get it working. Thank
you.
 
J

John M

make sure you can ping everything from the exchange server, and use nslookup
to check the names and ip address of the DC and global catalogs
 
S

Steven T

The ping test for every server is successful.
And in nslookup, I can get the correct DC and GC entrys
_ldap._tcp.gc._msdcs.mydomain.com
_ldap._tcp.dc._msdcs.mydomain.com

John M said:
make sure you can ping everything from the exchange server, and use nslookup
to check the names and ip address of the DC and global catalogs

Steven T said:
We are running a MS Exchange Server 2000 in a Windows 2000 Native Domain.
Recently, we've changed the network topology and once this is set up,
clients are experiencing problems using outlook to connect to
Exchange. Clients using Outlook regularly receive prompts saying that
"Outlook is retrieving data from the Microsoft Exchange Server MAIL. You can
cancel the request or minimize this message to the Windows taskbar until
Outlook
closes the message automatically" I know this may be caused by RPC delays.

The original site has 2 subnets A and B. The DC, GC, Exchange Server and
most
clients reside on Subnet A. Then we carry out the change. We've created a
new
Subnet C and Exchange server is the only computer in that subnet. Other DC
and
clients remains unchanged.

I ran the netdiag.exe on the Exchange server and found that the following
test failed.

Redir and Browser test . . . . . . : Failed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{A762B705-7D98-45B0-926F-FEB19BB916CE}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{A762B705-7D98-45B0-926F-FEB19BB916CE}
The browser is bound to 1 NetBt transport.
[FATAL] Cannot send mailslot message to
'\\MYDOMAIN*\MAILSLOT\NET\NETLOGON' vi
a redir. [ERROR_BAD_NETPATH]

In the System Event log, I occationally receive error logs of event id 5783
The event source is from NETLOGON
Description:
The session setup to the Windows NT or Windows 2000 Domain Controller
\\dc1.mydomain.com for the domain MYDOMAIN is not responsive. The
current RPC call from Netlogon on \\MAIL to \\dc1.mydomain.com has been
cancelled.

Sometimes it's saying DC1 is not reponsive, sometimes it's saying DC2 is not
reponsive. I don't know if this is related to the Outlook delay problem we
experience. Also, I am not sure about the cause of this. Is it a Network
problem
or I have to tweak with the AD or Exchange server to get it working. Thank
you.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top