Greetings, Although *portforward* worked it won't run as a service and won't automatically load its configuration. Although the source code was available I was not prepared to learn just enough C to customise it.
I finally stumbled across some good advice that was be applicable to our environment. < http://www.aftershell.com/2011/11/05/port-forwarding-as-a-windows-service/> The *netsh* commands can proxy ports using the *portproxy *interface and once configured the proxied ports persist between reboots. For our Windows XP host:- 1. Ensure that Microsoft's IPV6 Protocol is installed on the network adapter. <http://support.microsoft.com/kb/555744> 2. To forward connections from port 1389 on the host to the default AD LDAP Port on the guest run the following at the command prompt:- "netsh interface portproxy add v4tov4 listenport=1389 connectaddress=10.0.0.10 connectport=389" 3. Modify the XP Firewall settings to allow external connections to port 1389 4. Wonder why it was so hard in the firat place :-/ -- Regards, noonie On 8 February 2012 07:37, noonie <[email protected]> wrote: > Just in case anyone is interested in the resolution of this question... I > found a small app, with source code, called portforward > <http://www.quantumg.net/portforward.php>and > it seems to be working fine. > > -- > noonie > > > On 6 February 2012 16:57, noonie <[email protected]> wrote: > >> Greetings, >> >> We have created a web-based user management system that works with Active >> Directory however the development time has been greatly increased by not >> having a local environment to develop and test against. >> >> I have managed to get a copy of the remote domain brought into our >> network with he following config:- >> >> Windows XP workstation (on our domain) hosting Microsoft Virtual Server >> containing Windows Server™ 2003 Service Pack 2 as the guest O/S. >> >> The guest is configured as a domain controller and contains a close copy >> of the remote AD. >> >> The guest O/S is configured to use the host loop-back network adapter and >> is completely isolated from the host's domain. >> >> What I want to do is be able to configure the application under >> development to use LDAP connections and point them at the "replica" domain >> controller. The fact that this is hosted on XP is giving me a headache but >> this configuration is not open for negotiation. >> >> I assume that I need a port forwarding solution but XP doesn't appear to >> have one built in and Fpipe, which works fine for port 8080 --> 80 mapping >> appears to choke when I connect using an LDAP browser (ADAM ADSI Edit) >> mapping 1389 --> 389. I can connect and display the schema root but >> drilling into the directory returns errors at the client and logs errors in >> the Fpipe command window. I suspect that I've just chosen the wrong tool to >> do the forwarding. >> >> Has anyone had any success with this type of configuration and what >> recommendations do you guys have for port forwarding/mapping utilities that >> will work for me on XP? >> >> -- >> Regards, >> noonie >> > >
