Hey folks,
I need a loopback IP on windows (other than 127.0.0.1) so that when a connection is made to it, it is sent back as though it is a connection being made from another machine.
I looked into using the Microsoft Loopback Adapter, but I don't think this is what I want as you assign an IP to the adapter - and it does loopback... but since the adapter (configured with the IP) can be seen by Windows... the service I'm trying to connect perceives this as a connection from localhost and denies it.
So I'm after recommendations on how to perform a real loopback on windows that will work... I'm thinking maybe create a fake network of 172.16.255.252 with netmask of 255.255.255.252, put my machine on 172.16.255.253 and target a fake machine on 172.16.255.254 which will just forward data to 172.16.255.253... somehow?
--- For those of you who want to know why... but it doesn't matter... but some of you may ask ---
Cutting a long story short... I tunnel a remote desktop (RDP) session in to my windows box via SSH. But the "Terminal Server" service won't accept incoming connections that look like it's coming from localhost.
So instead of targeting my tunnel at localhost/127.0.0.1/own ip/own hostname/etc... (none of which work), I'd like to target it at this pseudo fake IP that will loopback making it look like it came from another machine not from itself.
I do not require alternative recommendations on remotely accessing this machine or tunnelling techniques.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I loves me some good security as well.
Try following the instructions here:
http://www.mydigitallife.i
Your best and easiest bet would be to just change the local port you'd be connecting to.
or download the file from here::
http://support.microsoft.c
I am doing exactly as I have wrote. But I am not after advise on tunelling RDP via SSH, I'm just explaining the purpose. Most of the guides (such as the one linked to) on the Internet are defunct for my purpose due to either the service pack running or the way around the connection is being performed.
A virtual NIC and LAN is needed at this point to simulate data coming in from something that couldn't possibly be considered localhost.
Windows considers any IP address that is assigned to any/all NIC's as being "local". Windows does not support a 'virtual' network that is not considered local.
About the only way you could do this is to use VirtualPC/VMWare and have a virtual Windows system running on your normal Windows system. Then communicate between the virtual host and the real host.
There is no way under Window OS to have a local IP address not appear to be local. The reason is that the IP addressing must be handled by the IP stack and there is only one IP stack under Windows.
In fact the only OS that I am aware of that allows multiple IP stacks is IBM z/OS, which can have up to 8 independet IP stacks. So each stack looks like a different host to each of the other stacks.
Windows only allows a single stack and I am fairly sure that all *nix variants only allow a single stack also.
However virtualizing an OS on that OS will do what is needed... so that to me says this can be done.
After all that process is just a matter of running software on top of Windows... Windows itself is oblivious to that fact it's virtualizing anything...
So it must be possible to some extent, but I appreciate that such software would have to directly create a new IP stack... so it's unlikely anyone has probably made this!
Virtuizing a OS is different as you are creating a whole virtual machine. The virtual machine has its own IP stack.
However, I am playing around with two things that MIGHT be able to do this.
As part of VirtuaPC MS has bundled the vmnet driver that is supposed to create a "virtual network" that allows the host OS and a virtual OS to talk to each other as if the are on isolated network. This function along with the virtual device emulator (a separate download) seem to allow you to create a virtual network within the host OS.
I am not 100% sure it will do what you want, as it is still a single IP stack, that stack must know all IP addresses and thus they may still all appear locally.
However, based on everything I have read, this is designed to allow the host OS to talk to a virtual OS.
Business Accounts
Answer for Membership
by: giltjrPosted on 2009-09-29 at 06:16:15ID: 25448605
Try using 127.0.0.2 as the IP address.
Found on http://www.engr.wisc.edu/c