Re: Outlook 2003 can't see Exch 2003 over RPC
- From: "John Oliver, Jr. [MVP]" <jcoliverjr@xxxxxxxxxxx>
- Date: Mon, 16 Oct 2006 12:44:03 -0400
Jeff,
Check your event log on the SBS server for any related errors when client
tries to open RPC over HTTP connection. You also never stated if you are
using HTTPs, and if so, are you using a personal cert or public cert? Also,
rerun Internet and Mail Connection Wizard to create the necessary changes
for RPC over HTTPs on the SBS 2003 R2 server.
--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2007
Microsoft Certified Partner
"Jeff" <Jeff@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B242C061-1622-42AA-8CE5-6AD3516FD3D5@xxxxxxxxxxxxxxxx
John,
Followed the DNS article, also checked netdiag and dcdiag outputs and all
tests passed ok so guess that's fine. However, no joy from
Outlook/Exchange.
I even went the whole hog and made the SBS box the DHCP and DNS for the
LAN,
disabling the router's services. Same old response - seems unable to
resolve
the names. The SRV records in the DNS look fine, so no idea why.
Disk shares, net view, etc work between the same workstation and the
server,
and it logs in to the domain happily - all of which suggests that at least
some RPC calls are working just fine, but not the Outlook/Exchange ones.
Also
checked RPC protocol listing for Exchange in the registry on both
workstation
and server and as far as I can tell, it's ok (ip_tcp and local rpc are
both
there).
I did briefly get Outlook RPC over HTTP to work, but that seemed to stop
working as soon as I stopped SBS being the DHCP server (weird, given
RPC/HTTP
is meant to be used over the internet so I wouldn't expect SBS to be
either
DNS or DHCP in that situation).
Seriously baffled here! Do you have any more thoughts?
Thanks!
Jeff
"Jeff" wrote:
Thanks John. I'll give that a try - I reckon we can live with the thing
being the DNS server. The router should only get upset if it can't
control
DHCP, looking at what it's doing.
The misbehaviour was something to do with it losing sight of the network
interface card and the Sharepoint timer process going mad and eating up a
whole CPU core to itself. Had to do a repair from the setup CD in the end
and
all's well now. I'll keep an eye on that. Hardware spec is pretty high,
so
unless we had some temporary fault, I think it was the O.S.
Thanks again, will let you know how I get on.
Jeff
"John Oliver, Jr. [MVP]" wrote:
DNS is the backbone of Active Directory. Without a proper setup you
will
continue to have issues related to DNS. You could most likey can use
the
Router as DHCP Server but DNS must be handled by SBS Server for
everything
to work properly in SBS Domain. I found SBS to be very reliable but if
you
have inadequate hardware you could see issues. Below is link why DNS
is so
vital to Windows environment.
http://support.microsoft.com/default.aspx/kb/291382
--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2007
Microsoft Certified Partner
"Jeff" <Jeff@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D527231A-B780-4A9D-ABA2-38CEE8798DE2@xxxxxxxxxxxxxxxx
John,
Thanks for that... Does this also mean that the SBS server wants to
be the
DHCP source for the LAN too? I can live with it trying to be primary
DNS,
but the DHCP needs to be handled by the router or that'll get upset
about
access controls and probably UPnP too. This server is just another
box on
the
LAN, not the DMZ device.
I'd really rather not rely on SBS to do either job to be frank,
especially
as I've had some reliability problems with the OS (already had to
rebuild
once since I set it up two weeks ago and as I speak, it seems to be
misbehaving again - may have to try your solution after the next
repair or
rebuild :o( ).
Is there any way around this - when all's said and done, RPC is just
another
TCP/IP service, so I'm bemused as to why SBS needs all this special
treatment. Nothing else using RPC seems to.
Thanks!
Jeff
"John Oliver, Jr. [MVP]" wrote:
Your problem in this setup is that DNS must be handled by the SBS
Server
and
the clients must use the SBS Server IP as the Primary DNS Server.
Set
the
ISP's DNS Servers as Forwarders in your DNS Console on your SBS
Server
then
update the DHCP Scope of the SBS Server to make the DNS Server the
internal
IP of the SBS Server.
--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2007
Microsoft Certified Partner
"Jeff" <Jeff@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1AC3612B-C844-49DE-9249-79DF962D3B56@xxxxxxxxxxxxxxxx
Bit of a long post, but as you'll see, I've tried to check out as
much
as
I
could before posting!
I've just completed setup of a SBS2003 R2 server and I'm having a
big
problem with getting Outlook 2003 clients to connect to the
Exchange
server
in its native (RPC) mode.
Outlook web access is fine for all users, the users can map drives
to
the
server, etc - no problems. The client PCs are one which is a
member of
the
domain and authenticates against the SBS server and one which is
configured
in a workgroup so only connects to pick up email. I checked IMAP
access
to
the mailboxes also works fine, except I don't like Outlook's
handling
of
IMAP
so I'd rather use a proper Exchange server setup.
I tell Outlook to add a new account, MS Exchange Server. Enter the
server
name and the user name and click Next. Outlook then complains "The
action
could not be completed. The connection to the Microsoft Exchange
server
is
unavailable. Outlook must be online or connected to complete this
action"
and
won't go any further.
I've tried the short name <server>, the FQDN <server.domain.local>
and
even
the internet equivalent <www.server.net>, all with the same
result.
The
setting of "Use Cached Exchange mode" also makes no difference.
I thought this might be an authentication issue, so I tried
setting
"Always
prompt for user name and password" under More Settings/Security.
That
lets
me
create the email account and demands a login when I start Outlook,
but
then
comes up with "Outlook could not log on.. The connection to the
server.
etc
etc"
Trying to set Outlook up for RPC over HTTP also doesn't get me
far. So,
I'm
guessing it's something about the server's security or RPC, but 4
hours
of
digging around on the web later and I'm none the wiser. Especially
as I
would
expect a default Exchange server config to talk to Outlook.
I've tried deleting the Outlook profile and even setting up a
fresh
user
ID
on the client PC to test from. Same results each time.
If I have "Always prompt for user/password" ticked, then running
Outlook
/rpcdiag initially shows two lines - Directory (no server
name)/connecting
and Referral (SBS server name)/Connecting. If that's not set, it
clears
the
diag list too fast for me to see anything at all! Anyone know
whether
the
diags are captured in a file someplace?
For reference, both machines are on the same internal subnet and
in the
interests of ensuring no interference, the client PCs have their
firewalls
disabled ("allow all traffic") temporarily. The server isn't
running
Windows
firewall anyway (single network machine, not in the DMZ). Clients
can
all
get to the server by hostname for web and other access, so the DNS
appears
to
be working (DNS is managed by the network router, not the Windows
server).
Help!
.
- Follow-Ups:
- References:
- Re: Outlook 2003 can't see Exch 2003 over RPC
- From: John Oliver, Jr. [MVP]
- Re: Outlook 2003 can't see Exch 2003 over RPC
- From: Jeff
- Re: Outlook 2003 can't see Exch 2003 over RPC
- From: John Oliver, Jr. [MVP]
- Re: Outlook 2003 can't see Exch 2003 over RPC
- From: Jeff
- Re: Outlook 2003 can't see Exch 2003 over RPC
- From: Jeff
- Re: Outlook 2003 can't see Exch 2003 over RPC
- Prev by Date: ActiveSync and Treo 700p
- Next by Date: OWA frontend server(maybe not call this)
- Previous by thread: Re: Outlook 2003 can't see Exch 2003 over RPC
- Next by thread: Re: Outlook 2003 can't see Exch 2003 over RPC
- Index(es):
Relevant Pages
|
Loading
