Re: Plz help- tried all possible solutions- Outlook does not connect to Exchange

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



serge wrote:
On Apr 20, 11:20 am, serge <ser...@xxxxxxxxx> wrote:
On Apr 20, 10:53 am, "kj" <k...@xxxxxxxxxxx> wrote:

Some comments inline and suggestions at the bottom.


kj,
my apologies. i was wrong about the netdiag results. i ran the
netdiag on the machine i disconnected from the Domain. When running
netdiag on a XP machine still on domain, the DC list test FAILED.
[WARNING] Cannot call DsBind to nhmsbs.nhmny.local (10.10.15.2).
[RPC_S_SERVER_UNAVAILABLE].

So if you can't bind to the domain controller, you are going to have lots of
issues, Exchange would be one of them.
But the workstation is able to locate and resolve the DC (10.10.15.2) ( btw,
there really isn't anthing in any of these results that would compromise
your security, little need to edit out internal domain and mac addresses.)


here is the full log:

Host Name. . . . . . . . . : COMPUTERNAME.DOMAIN.local
IP Address . . . . . . . . : 10.10.15.33
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 10.10.15.2
Primary WINS Server. . . . : 10.10.15.2
Dns Servers. . . . . . . . : 10.10.15.2

Your workstation has the proper WINS server....

NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service',
<03> 'Messenger Service', <20> 'WINS' names is missing.

....but the WINS entries for this workstation are missing. The workstation is
unable to register it's entries with WINS and may not be able to do WINS
lookups for other systems & servers.

WINS service test. . . . . : Passed


DC list test . . . . . . . . . . . : Failed
[WARNING] Cannot call DsBind to SERVER.DOMAIN.local (10.10.15.2).
[RPC_S_SERVER_UNAVAILABLE]

This is probably the issue to persue.


Starting test: Services
IsmServ Service is stopped on [SERVER]
TrkWks Service is stopped on [SERVER]
TrkSvr Service is stopped on [SERVER]

Don't rememeber off the top of my head what the "TrkWks" and "TrkSvr"
services are.... might want to check into those.

Starting test: FsmoCheck


......................... DOMIAN.local passed test FsmoCheck

So the workstation(s) are having RPC problems to the server, but only a few
not all. Are you sure that there is no firewall configured on those
workstations? Did these workstation previous work correctly and if so, what
has changed recently?

I'd also check the Server Event logs particularly around WINS as well as
looking the WINS entries for the workstations in question. Perhaps a clue or
lead to the solution.

--
/kj


.



Relevant Pages

  • Re: Netdiag Kerberos Fail
    ... > Upgraded our windows nt domain to windows server 2003 active directory. ... Ran netdiag on workstation with a failure on kerberos and ... This has solved our event id errors and the ldap failure in ...
    (microsoft.public.win2000.active_directory)
  • Re: Plz help- tried all possible solutions- Outlook does not connect to Exchange
    ... netdiag on the machine i disconnected from the Domain. ... Your workstation has the proper WINS server.... ... IsmServ Service is stopped on [SERVER] ... portqry -n computername -e 135 ...
    (microsoft.public.windows.server.sbs)
  • Re: Make XP Workstation Settings (internet and desktop) for all users.
    ... what "entries" are you referring to? ... I have set up my first XP workstation (to use the NT 4 Domain and to ... > connect to the internet). ... When another user logs on (via the server) XP ...
    (microsoft.public.windowsxp.network_web)
  • Re: shared fax client crashes
    ... what O/S on the client, any entries in the ... event log on the workstation or server, what program are you doing the ...
    (microsoft.public.windows.server.sbs)
  • Need Help w/ NetDiag errors
    ... When I ran NetDiag on my workstation, I got a couple of NetDiag errors. ... brief info on the network: This is a brand new W2K3 network I'm ... GateKeeper - Member server running ISA 2004 w/ internal, ...
    (microsoft.public.win2000.networking)