Announcement

Collapse
No announcement yet.

rpc on exchange 2003 sp2 with MailMarshal

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • rpc on exchange 2003 sp2 with MailMarshal

    Hi All,

    I have a server.
    Win 2003 Std SP2 with Exchange 2003 sp2, also install MailMarshal software for anti-spam

    I enabled rpc and test , got "server name can't be resolved" error
    use microsoft CA and already issued SAN cert, enabled ssl for rpc

    i think there's an issue in name resolution as
    my AD domain name = intra.mydomain.com
    my server fqdn = server.intra.mydomain.com

    when emails pass through mailmarshal they go out as po.mydomain.com
    and my owa address is webmail.mydomain.com
    my public mx record points to po.mydomain.com
    but there is no mx record in my internal dns server

    kindly help me how to get rpc done!!!

  • #2
    Re: rpc on exchange 2003 sp2 with MailMarshal

    Is this internal or external RPC?
    if external, go to www.testexchangeconnectivity.com and run the tests, then give a full report back here.

    In general, your SAN certificate needs:
    public name (po.mydomain.com)
    server fqdn and netbios names

    You should not need internal MX records.

    IMHO, get a commercial cert ($75 per year from godaddy.com, for example) and save a lot of hassle
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Re: rpc on exchange 2003 sp2 with MailMarshal

      Originally posted by lwelyoo View Post
      Hi All,

      I have a server.
      Win 2003 Std SP2 with Exchange 2003 sp2, also install MailMarshal software for anti-spam

      I enabled rpc and test , got "server name can't be resolved" error
      use microsoft CA and already issued SAN cert, enabled ssl for rpc

      i think there's an issue in name resolution as
      my AD domain name = intra.mydomain.com
      my server fqdn = server.intra.mydomain.com

      when emails pass through mailmarshal they go out as po.mydomain.com
      and my owa address is webmail.mydomain.com
      my public mx record points to po.mydomain.com
      but there is no mx record in my internal dns server

      kindly help me how to get rpc done!!!
      http://www.petri.com/how-can-i-confi...r-scenario.htm

      This is all you require. The premise is effectively the same for a single server or FE/BE deployment. Just ensure the name in your cert is the same name you use to connect Outlook to from the internet. As already stated though if you are going to use an internal CA ensure the certificate is installed in the trusted root or the certificate chain goes back up to a trusted root.
      Last edited by scurlaruntings; 10th November 2011, 09:52.

      Comment


      • #4
        Re: rpc on exchange 2003 sp2 with MailMarshal

        i've issued a new san cert and after i enable the ssl, can't open the webmail
        without ssl can open
        i've tried
        1) enable ssl on rpc and without ssl on default website: owa can open, rpc can't open (The connection was interrupted)

        2) enable ssl on both default website and rpc, can't open owa or rpc, same error

        Already restart the server, still same issue

        Comment

        Working...
        X