Re: Outlook 2003 can't see Exch 2003 over RPC

Tech-Archive recommends: Fix windows errors by optimizing your registry

Thanks for the follow-up. I have heard and seen strange issues before but
this is one I will not forget anytime soon!

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2007
Microsoft Certified Partner

"Jeff" <Jeff@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:96D5CDC8-BC20-40D7-A904-49DB25DC02A7@xxxxxxxxxxxxxxxx
And it was... just completed a basic rebuild and tried out Outlook,
forcing
the install across from the server when the workstation joined the domain.
All's well - Outlook connected first time.

What on earth was the original problem, I've not a clue. Laptop still
won't
talk to the Exchange server even though it's been joined to the domain and
all the necessary. I'm going to try uninstalling Outlook on there and
forcing
the install from the SBS server as with the other workstation - my
suspicion
here is that the Outlook install from my Office CDs is in some
(imperceptible
but vital) way different to that from the SBS CDs.

Thanks for your help along the way, John!


Jeff


"John Oliver, Jr. [MVP]" wrote:

Sounds more and more like the workstation at this point.

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2007
Microsoft Certified Partner

"Jeff" <Jeff@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:38E9E90A-D6E3-4612-B326-529982AC8BCD@xxxxxxxxxxxxxxxx
Thanks John, I'll give the MS toolkit and ethereal a go. I rebuilt
the
SBS
server over the weekend but it's not changed the problem at all, so I
suspect
it may be at the workstation end, given the freshly-built default
settings
of
SBS should allow Excahnge to work!

I'll let you know what I find out!

Cheers


Jeff


"John Oliver, Jr. [MVP]" wrote:

Wow, at this point I would start sniffing traffic between the
workstation
and SBS Server to insure RPC traffic is passing. I like Ethereal
which
is
a free a download. Other than that, might last resort would be to
setup
a
test SBS box to see if the workstation can connect with Exchange
Server.
You could use a regular comptuer to install SBS Sever on a separate
lan
or
switch. This would at least tell you if maybe the workstation or SBS
box
is the problem child. Short of this, a call to Microsoft PSS but this
will
cost $245. Sorry I could not be of more help but this ones seems very
difficult to diagnose.

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2007
Microsoft Certified Partner

"Jeff" <Jeff@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1CA4CA21-5DFE-4E03-A020-F36AE620BD06@xxxxxxxxxxxxxxxx

Hi John,

Yes, problem workstation #1 is joined to the SBS server's domain and
uses
SBS as its DNS server. W/station's getting its IP address from DHCP
on
the
router, but I've manually set up DNS servers for it to ensure that
the
SBS
server is used as DNS. I've checked that in nslookup and ipconfig
and
it's
definitely going to SBS for its lookups. The server FQDN pings just
fine
from
the w/station, as does the short name of the server. Web pages on
the
server,
including web Outlook, are fine too.

I've done all my diagnosis so far with the client firewall
(F-Secure)
set
to
allow everything and SBS was built without firewall active (machine
had
only
one LAN connection when built, so firewall didn't want to install
itself
anyway).

Cheers,


Jeff

"John Oliver, Jr. [MVP]" wrote:

Understand, so lets get back to basics on Outlook to Exchange
connection
on
the local LAN. Back to your original post, am I correct in saying
the
the
computer that is joined to the domain is the one that is having
issue
with
Outlook connection to Exchange? I can understand the Workgroup
mode
computer having some issue if the host file is not configured
correctly
with
SBS Server name. Again, verify the computer that is joined to the
domain
has the DNS Server Primary address as the SBS Server. Ping the SBS
Server
by FQDN with success? Do not recall if I mentioned this before,
make
sure
that the Windows Firewall and any Firewall Client is disabled for
troubleshooting Outlook to Exchange connection.

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2007
Microsoft Certified Partner

"Jeff" <Jeff@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:502D9921-C4B8-48C4-B1A2-B2D65AA3464F@xxxxxxxxxxxxxxxx
Simple answer, John... I don't !!

As I think I said in one of my earlier posts, I only tried the
RPC/HTTPS
option as part of the diagnosis when the normal RPC/TCP route
didn't
work.
It's the latter I want working really.

I've tried RPC ping before but the results seemed inconclusive.
I'll
check
out that article in case it's offering anything different to the
one
I
read.

Thanks for that!

Jeff


"John Oliver, Jr. [MVP]" wrote:

Can I ask a simple question, why are you wanting to run RPC over
HTTPs
on
the LAN? Its more suited or designed for external access. Just
curious.

To help you troubleshoot RPC try RPC Ping,

http://support.microsoft.com/Default.aspx?kbid=831051

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2007
Microsoft Certified Partner

"Jeff" <Jeff@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D66F2048-A79D-4F5A-8BF3-38E600030CDB@xxxxxxxxxxxxxxxx
It worked briefly, though I can't seem to repeat that now!

I'll try testing from an external link as you suggest,
although
getting
it
working on the LAN side is my priority rather than the
external
HTTPS
link,
which was more a case of "try it and see" for diagnostic
purposes!

Part of the problem here for me is that I can't see what it's
doing.
Do
you
know of anything in the MS toolkits which will track RPC calls
at
client
and
server endpoints and let me see what it's trying to do and
perhaps
what's
failing or not getting through?

Thanks!


J


"John Oliver, Jr. [MVP]" wrote:

Jedf,

You stated you did get RPC over HTTP to work for a while when
the
SBS
Server
was DHCP server, is this still the case? As for the cert,
here
is
link
explaining the proper setup but it sounds like you have this
configured
correctly,
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B555261.
I
would
also try to troubleshoot while you computer is not connected
locally
to
your
network. Since you will using RCP over HTTPs over the
internet,
its
best
to
troubleshoot over the internet I have found myself. Try
plugging
your
laptop or computer on your Routers external interface to test
or
try
from
outside your network, say at home. Test with outlook
/rpcdiag
switch.

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2007
Microsoft Certified Partner

"Jeff" <Jeff@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B11FB28D-48CE-48E4-BAB4-ECD54A1E3F8D@xxxxxxxxxxxxxxxx
John,

Thanks for sticking with this!

Re-ran the internet & email wizard. No change to behaviour.

Oddly, there's nothing in the event logs at all. Checked
App,
Sys,
Sec
and
DS and nothing gets added when I try Outlook either over
TCP
or
HTTP.
I've
got all the DS, LDAP and RPC-related diagnostics for the
Exchange
server
instance set to maximum logging. There are a few 0x51 &
0x52
LDAP
informationals in the DS log, but all sources suggest those
are
harmless.

The RPC/HTTP attempt was over HTTPS but I've also now tried
RPC
over
vanilla
HTTP and that was no different.

Makes me wonder whether the traffic is even leaving the
workstation,
but
the
HTTPS version does prompt for user id and password and
seems
to
do
something
with the login, so I'm guessing it is connecting or at
least
trying
to
connect.

The server certificate, I generated locally during the SBS
install.
The
root
authority is my server and I've already told the client
machines
to
install
the cert when I first browsed the server's HTTPS websites
from
them.
The
only
possible issue I can think of there is that the cert is
issued
for
our
external FQDN (www.something.net) rather than the internal
server
name
(sbs_box.domain.local)... would that screw it up without
reporting
any
sort
of error?

Thanks,


Jeff

"John Oliver, Jr. [MVP]" wrote:

Jeff,

Check your event log on the SBS server for any related
errors
when


.

Quantcast