[ previous ] [ next ] [ threads ]
 From:  "Quark IT - Hilton Travis" <Hilton at QuarkIT dot com dot au>
 To:  "David Kitchens" <spider at webweaver dot com>, "m0n0wall -" <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] Connecting to Exchange via vpn
 Date:  Tue, 30 Sep 2008 15:55:58 +1000
Hi Dave,

We do a fair bit of SBS 2003 (and maybe soon some SBS 2008 now that MS
has raised the price - so it will be less of this than we'd hoped for).
I know we spoke about the ConnectComputer issue and needing IIS to be
configured to accept the IPs on the remote subnet, however I've not seen
the issue you had here, nor have I needed to Google for mapisvc.ini
before!  :)

There seems to be a lot of info about issues caused by this file either
being there or not being there, so it seems it is a somewhat common
cause of consternation with Outlook/Exchange configuration.  I guess
we've just been lucky here!  :)

Anyway, glad to know you got this sorted and that it wasn't a m0n0wall
problem.  Speaking of m0n0wall, can m0n0wall do an OpenVPN bridged VPN?
I know it can't now as OpenVPN has been pulled from the released images,
but I'm wondering if this will be possible once it is again reintroduced
to the image - the bridged OpenVPN settings in DD-WRT work really well
in the few cases we've deployed this config.  I'd rather do it on
m0n0wall, however.




Hilton Travis                       Phone: +61 (0)7 3105 9101
(Brisbane, Australia)               Phone: +61 (0)419 792 394
Manager, Quark IT                   http://www.quarkit.com.au
         Quark Group                http://www.quarkgroup.com.au

     Microsoft SBSC PAL (Australia) http://www.sbscpal.com/

War doesn't determine who is right.  War determines who is left.

This document and any attachments are for the intended recipient 
  only.  It may contain confidential, privileged or copyright 
     material which must not be disclosed or distributed.

                    Quark Group Pty. Ltd.
      T/A Quark Automation, Quark AudioVisual, Quark IT

> -----Original Message-----
> From: David Kitchens [mailto:spider at webweaver dot com]
> Sent: Tuesday, 30 September 2008 5:58 AM
> Fixed! Google to the rescue again, guess I didn't see it the first
> time...
> Search the drive for mapisvc.inf, delete both files, open Outlook
> again,
> enter credentials and poof! It works! Time for a beer, lol.
> -----Original Message-----
> From: David Kitchens [mailto:spider at webweaver dot com]
> Sent: Monday, September 29, 2008 3:44 PM
> Well I just tried unchecking Allow DNS server list to be overridden by
> DHCP/PPP on WAN and setting the primary dns to the sbs server and
> ipconfig
> still shows 26.1 as the primary. Manually setting the computer dns to
> 25.10
> (sbs) does not help either, I get the same error. At a cmd prompt on
> the
> remote workstation now and nslookup goes right to to the sbs server as
> I
> expect with the manual settings. So it seems dns is right, yet still
> joy
> with outlook. I tried both the server ip and name, both resolve fine
> their own, in the Connect to Exchange wizard but it still can't list
> the
> users. Frustrating... I know this is not a monowall issue and I
> appreciate
> the help guys.
> -----Original Message-----
> From: Paul Rae [mailto:paul at impacttrainingsolutions dot co dot uk]
> Sent: Monday, September 29, 2008 1:49 PM
> For things to play nicely, you need to set the remote machines to use
> the
> SBS machine as their primary DNS.
> Either that, or if their is another server at the remote site set it
> to
> be a secondary DNS server for the SBS domain.
> On 29/09/2008 18:25, "David Kitchens" <spider at webweaver dot com> wrote:
> > Currently the primary dns gets the mono ip which is what I suspect
> > the issue. Mono ip is at remote, SBS server is
> > at main office. I couldn't figure out the hidden dhcp
> options to set.
> >
> > -----Original Message-----
> > From: Paul Rae [mailto:paul at impacttrainingsolutions dot co dot uk]
> > Sent: Monday, September 29, 2008 1:16 PM
> >
> > On the remote machines, what do you have the dns resolvers set to?
> >
> >
> > On 29/09/2008 17:59, "David Kitchens" <spider at webweaver dot com> wrote:
> >
> >> Hello everyone, I've got a problem connecting to Exchange thru an
> >> ipsec
> > vpn.
> >> I'm using 1.3b14 on both ends and the vpn is working fine. Remote
> >> office has
> >> 3 computers, main office has the SBS2003 server running as a DC. I
> >> first tried to join the 3 computers at the remote office to the
> >> domain itself, DNS is fully working, I can ping all main office
> >> machines by computer name and can get to the servers
> /connectcomputer
> >> webpage but when attempting to join I get an error about can't list
> >> users or computers. I manually joined the domain on one machine the
> >> old way, right click My Comp, join domain, and that worked fine but
> >> the logon was extremely slow. Discussing these limitations with the
> >> owner, we decided to leave the remote computers unjoined. I can map
> >> drives so those users can access the server and I can get to
> >> https://server/exchange
> > to use OWA but the users want to use Outlook.
> >> When opening Outlook and attempting to configure the users account,
> I
> >> am getting "There was an error locating one of the items needed to
> >> complete the operation. It may have been deleted." I get this when
> >> entering the username and hitting Check Name. I have pass rules for
> >> all on both monowalls IPSEC Rules page. Can someone give me a clue
> >> what else I may need please? I've googled myself to death on this.
> >> I've tried setting a static route on the remote monowall to the
> other
> >> subnet but that hasn't seemed to help. I suspect that Outlook is
> >> trying to do something else that is getting blocked but nothing is
> >> showing
> > in the logs of either monowall.
> >>
> >> Dave