Wingate and Back to my Mac

[hvd]

Has anyone been able to configure their wingate to handle back to my mac? If so, how?

[genie]

What kind of problem are you seeing? We have tested quite a lot of Mac-related scenarious and found no particular problems with Wingate handling their traffic.

[hvd]

What I want to do is using "Back to My Mac" from my office iMac, through WinGate, to access my remote iMac at home. BTMM is a new feature in Mac OS X Leopard to let you access your remote computer over the internet. There're 2 steps to do this: (1) signing on to .Mac account, then (2) enable the BTMM service, and you'll able to control your remote screen, or access remote files. I was able to BTMM when I connected my office iMac to the internet directly, but not when it's behind WinGate.

My NIC has this configuration:
IP Address: 192.9.200.101
Subnet Mask: 225.255.255.0
Router: 192.9.200.48
DNS Server: 209.236.128.128, 209.236.128.129
Search Domains: (empty)

Router 192.9.200.48 is our Wingate internal IP (for NAT), and DNS’s IPs are our ISP’s DNS.

When I enabled my office BTMM, DNS/WINS Resolver's log showed a reverse lookup using my internal ip (192.9.200.101) as below:
11/28/07 07:47:59 Request: request [032af008] PTR lookup "101.200.9.192.in-addr.arpa."
11/28/07 07:47:59 Debug: bounce request [032af008]<0> to try 1 (nothing useful in cache)
11/28/07 07:47:59 Debug: selected 209.236.128.128 <user input> for request [032af008]<1> (best looking)
11/28/07 07:47:59 Debug: request [032af008](ID 63481) sent to 209.236.128.128 <user input> (44 bytes)
11/28/07 07:48:00 Debug: received block [101] (server 209.236.128.128, port 53)
11/28/07 07:48:00 Debug: no such domain [032af008](ID 63481)

My iMac system.log was:
Nov 28 07:42:47 Macintosh mDNSResponder[23]: *** Keychain Changed *** KeychainEvent=3 kSecAddEvent
Nov 28 07:42:47 Macintosh mDNSResponder[23]: Setting up AutoTunnel address FD83:C0C1:D68F:BC6D:0217:F2FF:FEDE:4D14
Nov 28 07:42:47 Macintosh mDNSResponder[23]: Advertising hostname AutoTunnel-02-17-F2-FF-FE-DE-4D-14.gey.members.mac.com. IPv4 192.9.200.101
Nov 28 07:42:47 Macintosh mDNSResponder[23]: AutoTunnel server listening for connections on AutoTunnel-02-17-F2-FF-FE-DE-4D-14.gey.members.mac.com.[192.9.200.101]:4500:Macintosh.gey.members.mac.com.[FD83:C0C1:D68F:BC6D:0217:F2FF:FEDE:4D14]
Nov 28 07:42:47 Macintosh mDNSResponderHelper[5384]: racoon (pid=5385) started
Nov 28 07:42:48 Macintosh mDNSResponder[23]: ConstructServiceName: Application protocol name must be underscore plus 1-14 characters: ._EB932BC41E495D5FEA4965BF878559FD608E00F9._udp.gey.members.mac.com.
Nov 28 07:42:48 Macintosh mDNSResponder[23]: Error -65540 for registration of service in domain gey.members.mac.com.
Nov 28 07:42:48 Macintosh mDNSResponder[23]: Adding registration domain gey.members.mac.com.

The one missing final line from a successful BTMM when on a direct internet connection was:
Nov 16 07:46:01 Macintosh mDNSResponder[21]: Registered hostname AutoTunnel-02-17-F2-FF-FE-DE-4D-14.gey.members.mac.com. IP 209.236.202.23

As I understand it, that was a registration of the "hostname" for this AutoTunnel after registered the "domain".

Here is a piece from a Macworld article:
When you enable Back to My Mac, your computer:
- Starts advertising the service on the local network using Bonjour;
- Requests a NAT-PMP or PnP connection from the router; and
- publishes the port and IP address information it gets from the router to .Mac?s DDNS server as a wide-area Bonjour record associated with the domain

[logan]

BTMM requires a UPnP or NAT-PMP enabled router to work. WinGate doesn't do PnP so BTMM won't work properly behind WinGate.

You might want to look at an alternative solution like VNC, which is free and doesn't rely on PnP or the dotmac subscription.