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

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!






.

Relevant Pages

  • RE: login and email problems
    ... I am glad to know the DNS issue is resolved-). ... Client workstations's gateway should be the SBS server internal IP address. ... Does the outlook issue happen on only two client workstations? ... >> - If Microsoft Exchange Server does not appear in the list, ...
    (microsoft.public.windows.server.sbs)
  • Re: Adding domain users to local Administrator group
    ... Outlook configurations suddenly don't work (at least insofar as receiving ... IP address of the POP server into the Outlook configuration should work ... > I would speculate then that any amount of DNS changing is ... > "Brad Leppla" wrote in message ...
    (microsoft.public.windowsxp.security_admin)
  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... button, more button, the "Primary DNS suffix of this computer", it should ... The Security System could not establish a secured connection with the server ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
Loading