RPC over HTTP not working

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

The serviced offices where a client of mine work has the building
configured through a firewall that maps external IP addresses to
internal ones. This has created havoc with our standard SBS 2003
server setup. The building IT people assure me all the right ports are
open.

Our office has it's own little network on the internal NIC. The
external NIC had to be set up to talk to the buildings firewall/router
at 10.32.11.10 (external NIC)

However, when accessing the server from outside, I have to access it
via 82.110.241.nnn

This IP mapping has confused the hell out of the standard
http://mycomputer.com/remote autocreation tools and the standard
remote desktop.

When SBS creates an authentification certificate, the issuer is
10.32.11.10. However, as the browser on the client side thinks it's
talking to 82.110.241.nnn, the security settings throws a strop and
says the name on my certificate is invalid.

How do I get around this? From what I gather RPC over HTTP requires a
valid certificate to work. Is there a way I can get the server produce
a certificate with the 82.110.241.nnn IP address as the issuer?

Aside from that, how do I set up 'RPC over HTTP' with this IP mapping
getting in the way?

I've got a mycompany.dyndns.org ip address mapped to 82.110.241.nnn
which gets me into the admin website and OWA fine but what about the
rest? Some functions require a certificate. I cannot get remote
desktop to work directly (but it does from
http://mycomputer.com/remote) and VPN is also stuffed.

However, the most pressing thing is getting Outlook 2003 to see the
exchange server.

Let me know if I've got this wrong....

I'm assuming that the Exchange server is still 'max-server' (the
internal name of the server)

Username = dale

Exchange proxy settings:
URL for proxy server to exchange : mycompany.dyndns.org
Principle name for proxy server : msstd:mycompany.dyndns.org

But here's where I'm confused. could either of these just be
10.32.11.10 (the ip address the server thinks it is)?

This IP mapping is driving me nuts. It was all working fine before
they came up with this lame scheme.

---
Dale Walker
London Techno Events
dale@sorted,org
http://london.sorted.org