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

On Apr 19, 5:15 pm, "kj" <k...@xxxxxxxxxxx> wrote:
serge wrote:
On Apr 19, 4:34 pm, serge <ser...@xxxxxxxxx> wrote:
On Apr 19, 4:00 pm, "SBS2K3 Admin" <bogus...@xxxxxxxxxxxxxxx> wrote:

Well according to the inofrmation you posted it does seem to be
isolated to the particular workstations. My first plan of action
would be to compare an ipconfig /all on a working and non working
workstation.

"serge" <ser...@xxxxxxxxx> wrote in message

news:1177007976.592061.326020@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Please help,

I've been through numerous kb articles and posts on the newsgroups.
None of the solutions have helped so far.
It seems that 4 of the 30 computers on the network refuse to
connect to Exchange using Outlook 2003. 3 are XP Professional SP2
fully patched and one is Windows 2000 SP4 fully patched. Clients
also cannot connect tohttp://companyweb/whileeveryoneelse is
fine, although
they can browse documents and connect to network shares. Pinging
the name of SBS2k3 server just fine.
I get the following error when opening Outlook:
"The connection to the Microsoft Exchange Server is unavailable.
Outlook must be online or connected to complete this action."
In addition, applying computer settings and applying user settings
seem to take extremely long time. Things I've tried or solutions
followed.
1. Mainly the KB article
here:http://support.microsoft.com/kb/325930. Checked all the
registry settings to no avail.
2. System Restore prior to the problem happening. Nothing changes.
3. Reset TCP/IPhttp://support.microsoft.com/kb/299357;also
reinstalled the tcp/ip
4. Refreshed IPSettings, flushed dns, re-registered dns
5. followed this article as well:
http://www.123together.com/Support/error_outlook_your_exchange_server...
6. When the users log in to other computers they are able to
connect to Exchange just fine, so it's just the 4 comptuers.
7. The client computers have a common error: "Windows cannot
determine the user or computer name. (The RPC server is
unavailable) Group Policy processing aborted.

Thank you,

Serge

SERVER:

Windows IP Configuration

Host Name . . . . . . . . . . . . : SERVERNAME
Primary Dns Suffix . . . . . . . : DOMAIN.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : DOMAIN.local

Ethernet adapter Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II
GigE (NDIS
VBD Client)
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.111.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.111.1
DNS Servers . . . . . . . . . . . : 10.10.15.2
Primary WINS Server . . . . . . . : 10.10.15.2
NetBIOS over Tcpip. . . . . . . . : Disabled

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 PT Server
Adapter #2
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.15.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 10.10.15.2

------------------------------------------------------------------------------------------------------------------------
WORKSTATION:
Windows IP Configuration

Host Name . . . . . . . . . . . . : COMPUTERNAME
Primary Dns Suffix . . . . . . . : DOMAIN.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : DOMAIN.local
DOMAIN.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : DOMAIN.local
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx
Gigabit Cont
roller
Physical Address. . . . . . . . . : 00-11-11-5A-59-6A
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.10.15.16
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.15.2
DHCP Server . . . . . . . . . . . : 10.10.15.2
DNS Servers . . . . . . . . . . . : 10.10.15.2
Primary WINS Server . . . . . . . : 10.10.15.2
Lease Obtained. . . . . . . . . . : Thursday, April 19, 2007
8:36:28 AM
Lease Expires . . . . . . . . . . : Friday, April 27, 2007
8:36:28 AM

When opening netdiag.exe, I get the error: "The procedure entry point
DnsGetPrimaryDomainName_UTF8 could not be located in the dynamic link
library DNSAPI.dl"
The ipconfig /all settings are exactly the same as the ones on the
working computers.
Perhaps I should give this piece of information as well: Last night
the server crashed, It restarted w/o really any reason. I went
through the Logs but didn't have time to really pinpoint the
problem. As a result of the crash, the Local Area Network NIC lost
the IP address(It said it had limited connectivity).I have an extra
NIC, so I disabled the other Broadcom NIC that had lost the
connection, Enabled the Intel Pro 1000 one, put in the manual IP of
10.10.15.2. Then re-ran the Internet Connection Wizard. Everything
started working again perfectly. I've figured out that the
problematic workstations were the ones that had Outlook open during
the time I reran the Internet Connection Wizard. Hope this piece of
info helps.

Thank you.

could this be tied in to the latest RPC DNS vulnerability? I did the
suggested fix 2 days ago. I followed Susan Bradley's blog suggestion.

The workaround maybe effecting the netdiag results. I'll have to try this
our somewhere.

Nothing in the server event logs? The broadcoms stick out, but I haven't
followed the driver problems close enough recently. I think it was Les that
was atop the Broadcom Driver issues and workarounds.

Was the netdiag error from the server or a workstation? Also, I'd probably
run a dcdiag /c on the SBS server at this point (and netdiag if not
already).

--
/kj

the netdiag results checked out on the server and on the "bad"
workstations. no errors really. about dcdiag, i thought it was only
for 2000 servers and not 2003. im really at a loss of what to do now.
i think i may just end up reinstalling the operating systems on all
the computers. really wouldn't want to do that but it looks like thats
where its heading to.

.

Relevant Pages

  • Re: Im Stumped...
    ... I attempt to access the server via the UNC path. ... On 6 workstations I had no problems but 2 of ... involved plus I didnt feel the problem was the account I was using since ... I tried renaming on of the computers, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Im Stumped...
    ... I attempt to access the server via the UNC path. ... On 6 workstations I had no problems but 2 of ... involved plus I didnt feel the problem was the account I was using since ... I tried renaming on of the computers, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Cant browse across subnets
    ... I was trying to get RWW working externally, ... Computer Browser services on the SBS server, no errors, no ... All workstations can resolve all computernames via nslookup. ... All computers are available from either subnet using Remote ...
    (microsoft.public.windows.server.sbs)
  • Re: Im Stumped...
    ... I attempt to access the server via the UNC path. ... involved plus I didnt feel the problem was the account I was using since it ... still do not see objects in the Computer container for the two workstations, ... I tried renaming on of the computers, ...
    (microsoft.public.windows.server.active_directory)
  • Re: SBS 2003 Misconfigured?
    ... up one of the workstations via remote web connection, ... but why are you looking at the server rather than the workstation? ... (this will show you the DHCP lease info). ... The Netgear, or whatever you use as your gateway to get out to the Internet. ...
    (microsoft.public.windows.server.sbs)