Remote Desktop via Ad-Hoc on Windows 7

Is there a way to connect two PCs running Windows 7 via a wifi ad-hoc network and then use Remote Desktop from one of the PCs to the other? In addition to this the Remote Desktop host PC should still be able to connect to the internet via a separate ethernet adapter, allowing the client to use the internet via the remote host screen.

asked Mar 4 '13 at 5:21

Kyle V.

631212

add a comment |

asked Mar 4 '13 at 5:21

Kyle V.

631212

add a comment |

asked Mar 4 '13 at 5:21

Kyle V.

631212

windows-7 networking wireless-networking remote-desktop ad-hoc-network

asked Mar 4 '13 at 5:21

Kyle V.

631212

asked Mar 4 '13 at 5:21

Kyle V.

631212

asked Mar 4 '13 at 5:21

Kyle V.

631212

asked Mar 4 '13 at 5:21

Kyle V.

631212

asked Mar 4 '13 at 5:21

Kyle V.

631212

add a comment |

2 Answers
2

active

oldest

votes

I believe that the wired and wireless networks should stay separate, with different
IP segments per each network.

You should then bridge the two adapters on the PC that has the Internet access.

See How to Bridge From a Wireless to a Hard-Wired LAN.

This should enable the client PC to use the Internet connection of the other one.

I am not too clear about using Remote Desktop in this setup, so just try and see.

answered Mar 9 '13 at 8:56

harrymc

252k11259560

I tried bridging the adapters, setting up the Ad-Hoc network, and connecting the client PC to the network. I was able to connect to the network and use the internet from the client PC but as soon as I tried to connect Remote Desktop the ad-hoc network shut down and the connection was lost on the client.
– Kyle V.
Mar 12 '13 at 5:00

Ad-hoc is defined as a temporary connection, but I believe that RDP should still work. Are you getting an error message with the disconnect? Anything in the Event Viewer? Are you using only Windows or 3rd-party software? Try also using static IP addresses for both computers.
– harrymc
Mar 12 '13 at 7:18

How do I use static IP addresses?
– Kyle V.
Mar 15 '13 at 1:45

Here is a tutorial. Choose values that are in the right segment - use ipconfig in a command prompt on both computers to find out which is the segment to use.
– harrymc
Mar 15 '13 at 8:29

add a comment |

-1

This should absolutely be possible. Just set the ad-hoc network on a different IP range (for example, use 192.168.2.1 and 192.168.2.2 as the IPs for the two computers, and set the subnet mask to 255.255.255.0). The host must be able to run a Remote Desktop server (which I believe is restricted to Pro and up), but you can have a computer connected to two networks.

answered Mar 4 '13 at 5:25

cpast

2,11621325

I would describe that as a different IP, rather than a different IP range.
– Austin ''Danger'' Powers
Mar 4 '13 at 5:49

@Dan I meant "use the range 192.168.2.x" (as opposed to 192.168.1.x). The right term would be "different network" or "different subnet", but "different range" is less confusing.
– cpast
Mar 4 '13 at 5:52

This is promising but could you be more specific, How do I set these IP parameters?
– Kyle V.
Mar 4 '13 at 18:55

@StickFigs In Windows, under "Network Connections", right click the wireless interface, and hit "Properties". Click "TCP/IP version 4", and hit the configure button. Then, select "Manual IP" and enter these.
– cpast
Mar 4 '13 at 19:23

@cpast I tried setting the host IP to 192.168.2.1 but when I connect the other PC to the ad-hoc network it resets to the default IP 192.168.137.Something. You said to set the IP on both PCs? Before or after connecting/creating the network?
– Kyle V.
Mar 6 '13 at 23:02

|
show 4 more comments

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f560449%2fremote-desktop-via-ad-hoc-on-windows-7%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

I believe that the wired and wireless networks should stay separate, with different
IP segments per each network.

You should then bridge the two adapters on the PC that has the Internet access.

See How to Bridge From a Wireless to a Hard-Wired LAN.

This should enable the client PC to use the Internet connection of the other one.

I am not too clear about using Remote Desktop in this setup, so just try and see.

answered Mar 9 '13 at 8:56

harrymc

252k11259560

I tried bridging the adapters, setting up the Ad-Hoc network, and connecting the client PC to the network. I was able to connect to the network and use the internet from the client PC but as soon as I tried to connect Remote Desktop the ad-hoc network shut down and the connection was lost on the client.
– Kyle V.
Mar 12 '13 at 5:00

Ad-hoc is defined as a temporary connection, but I believe that RDP should still work. Are you getting an error message with the disconnect? Anything in the Event Viewer? Are you using only Windows or 3rd-party software? Try also using static IP addresses for both computers.
– harrymc
Mar 12 '13 at 7:18

How do I use static IP addresses?
– Kyle V.
Mar 15 '13 at 1:45

Here is a tutorial. Choose values that are in the right segment - use ipconfig in a command prompt on both computers to find out which is the segment to use.
– harrymc
Mar 15 '13 at 8:29

add a comment |

I believe that the wired and wireless networks should stay separate, with different
IP segments per each network.

You should then bridge the two adapters on the PC that has the Internet access.

See How to Bridge From a Wireless to a Hard-Wired LAN.

This should enable the client PC to use the Internet connection of the other one.

I am not too clear about using Remote Desktop in this setup, so just try and see.

answered Mar 9 '13 at 8:56

harrymc

252k11259560

I tried bridging the adapters, setting up the Ad-Hoc network, and connecting the client PC to the network. I was able to connect to the network and use the internet from the client PC but as soon as I tried to connect Remote Desktop the ad-hoc network shut down and the connection was lost on the client.
– Kyle V.
Mar 12 '13 at 5:00

Ad-hoc is defined as a temporary connection, but I believe that RDP should still work. Are you getting an error message with the disconnect? Anything in the Event Viewer? Are you using only Windows or 3rd-party software? Try also using static IP addresses for both computers.
– harrymc
Mar 12 '13 at 7:18

How do I use static IP addresses?
– Kyle V.
Mar 15 '13 at 1:45

Here is a tutorial. Choose values that are in the right segment - use ipconfig in a command prompt on both computers to find out which is the segment to use.
– harrymc
Mar 15 '13 at 8:29

add a comment |

I believe that the wired and wireless networks should stay separate, with different
IP segments per each network.

You should then bridge the two adapters on the PC that has the Internet access.

See How to Bridge From a Wireless to a Hard-Wired LAN.

This should enable the client PC to use the Internet connection of the other one.

I am not too clear about using Remote Desktop in this setup, so just try and see.

answered Mar 9 '13 at 8:56

harrymc

252k11259560

I believe that the wired and wireless networks should stay separate, with different
IP segments per each network.

You should then bridge the two adapters on the PC that has the Internet access.

See How to Bridge From a Wireless to a Hard-Wired LAN.

This should enable the client PC to use the Internet connection of the other one.

I am not too clear about using Remote Desktop in this setup, so just try and see.

answered Mar 9 '13 at 8:56

harrymc

252k11259560

answered Mar 9 '13 at 8:56

harrymc

252k11259560

answered Mar 9 '13 at 8:56

harrymc

252k11259560

answered Mar 9 '13 at 8:56

harrymc

252k11259560

I tried bridging the adapters, setting up the Ad-Hoc network, and connecting the client PC to the network. I was able to connect to the network and use the internet from the client PC but as soon as I tried to connect Remote Desktop the ad-hoc network shut down and the connection was lost on the client.
– Kyle V.
Mar 12 '13 at 5:00

Ad-hoc is defined as a temporary connection, but I believe that RDP should still work. Are you getting an error message with the disconnect? Anything in the Event Viewer? Are you using only Windows or 3rd-party software? Try also using static IP addresses for both computers.
– harrymc
Mar 12 '13 at 7:18

How do I use static IP addresses?
– Kyle V.
Mar 15 '13 at 1:45

Here is a tutorial. Choose values that are in the right segment - use ipconfig in a command prompt on both computers to find out which is the segment to use.
– harrymc
Mar 15 '13 at 8:29

add a comment |

I tried bridging the adapters, setting up the Ad-Hoc network, and connecting the client PC to the network. I was able to connect to the network and use the internet from the client PC but as soon as I tried to connect Remote Desktop the ad-hoc network shut down and the connection was lost on the client.
– Kyle V.
Mar 12 '13 at 5:00

Ad-hoc is defined as a temporary connection, but I believe that RDP should still work. Are you getting an error message with the disconnect? Anything in the Event Viewer? Are you using only Windows or 3rd-party software? Try also using static IP addresses for both computers.
– harrymc
Mar 12 '13 at 7:18

How do I use static IP addresses?
– Kyle V.
Mar 15 '13 at 1:45

Here is a tutorial. Choose values that are in the right segment - use ipconfig in a command prompt on both computers to find out which is the segment to use.
– harrymc
Mar 15 '13 at 8:29

I tried bridging the adapters, setting up the Ad-Hoc network, and connecting the client PC to the network. I was able to connect to the network and use the internet from the client PC but as soon as I tried to connect Remote Desktop the ad-hoc network shut down and the connection was lost on the client.
– Kyle V.
Mar 12 '13 at 5:00

Ad-hoc is defined as a temporary connection, but I believe that RDP should still work. Are you getting an error message with the disconnect? Anything in the Event Viewer? Are you using only Windows or 3rd-party software? Try also using static IP addresses for both computers.
– harrymc
Mar 12 '13 at 7:18

How do I use static IP addresses?
– Kyle V.
Mar 15 '13 at 1:45

Here is a tutorial. Choose values that are in the right segment - use ipconfig in a command prompt on both computers to find out which is the segment to use.
– harrymc
Mar 15 '13 at 8:29

add a comment |

-1

answered Mar 4 '13 at 5:25

cpast

2,11621325

I would describe that as a different IP, rather than a different IP range.
– Austin ''Danger'' Powers
Mar 4 '13 at 5:49

@Dan I meant "use the range 192.168.2.x" (as opposed to 192.168.1.x). The right term would be "different network" or "different subnet", but "different range" is less confusing.
– cpast
Mar 4 '13 at 5:52

This is promising but could you be more specific, How do I set these IP parameters?
– Kyle V.
Mar 4 '13 at 18:55

@StickFigs In Windows, under "Network Connections", right click the wireless interface, and hit "Properties". Click "TCP/IP version 4", and hit the configure button. Then, select "Manual IP" and enter these.
– cpast
Mar 4 '13 at 19:23

@cpast I tried setting the host IP to 192.168.2.1 but when I connect the other PC to the ad-hoc network it resets to the default IP 192.168.137.Something. You said to set the IP on both PCs? Before or after connecting/creating the network?
– Kyle V.
Mar 6 '13 at 23:02

|
show 4 more comments

-1

answered Mar 4 '13 at 5:25

cpast

2,11621325

I would describe that as a different IP, rather than a different IP range.
– Austin ''Danger'' Powers
Mar 4 '13 at 5:49

@Dan I meant "use the range 192.168.2.x" (as opposed to 192.168.1.x). The right term would be "different network" or "different subnet", but "different range" is less confusing.
– cpast
Mar 4 '13 at 5:52

This is promising but could you be more specific, How do I set these IP parameters?
– Kyle V.
Mar 4 '13 at 18:55

@StickFigs In Windows, under "Network Connections", right click the wireless interface, and hit "Properties". Click "TCP/IP version 4", and hit the configure button. Then, select "Manual IP" and enter these.
– cpast
Mar 4 '13 at 19:23

@cpast I tried setting the host IP to 192.168.2.1 but when I connect the other PC to the ad-hoc network it resets to the default IP 192.168.137.Something. You said to set the IP on both PCs? Before or after connecting/creating the network?
– Kyle V.
Mar 6 '13 at 23:02

|
show 4 more comments

-1

answered Mar 4 '13 at 5:25

cpast

2,11621325

answered Mar 4 '13 at 5:25

cpast

2,11621325

answered Mar 4 '13 at 5:25

cpast

2,11621325

answered Mar 4 '13 at 5:25

cpast

2,11621325

answered Mar 4 '13 at 5:25

cpast

2,11621325

I would describe that as a different IP, rather than a different IP range.
– Austin ''Danger'' Powers
Mar 4 '13 at 5:49

@Dan I meant "use the range 192.168.2.x" (as opposed to 192.168.1.x). The right term would be "different network" or "different subnet", but "different range" is less confusing.
– cpast
Mar 4 '13 at 5:52

This is promising but could you be more specific, How do I set these IP parameters?
– Kyle V.
Mar 4 '13 at 18:55

@StickFigs In Windows, under "Network Connections", right click the wireless interface, and hit "Properties". Click "TCP/IP version 4", and hit the configure button. Then, select "Manual IP" and enter these.
– cpast
Mar 4 '13 at 19:23

@cpast I tried setting the host IP to 192.168.2.1 but when I connect the other PC to the ad-hoc network it resets to the default IP 192.168.137.Something. You said to set the IP on both PCs? Before or after connecting/creating the network?
– Kyle V.
Mar 6 '13 at 23:02

|
show 4 more comments

I would describe that as a different IP, rather than a different IP range.
– Austin ''Danger'' Powers
Mar 4 '13 at 5:49

@Dan I meant "use the range 192.168.2.x" (as opposed to 192.168.1.x). The right term would be "different network" or "different subnet", but "different range" is less confusing.
– cpast
Mar 4 '13 at 5:52

This is promising but could you be more specific, How do I set these IP parameters?
– Kyle V.
Mar 4 '13 at 18:55

@StickFigs In Windows, under "Network Connections", right click the wireless interface, and hit "Properties". Click "TCP/IP version 4", and hit the configure button. Then, select "Manual IP" and enter these.
– cpast
Mar 4 '13 at 19:23

@cpast I tried setting the host IP to 192.168.2.1 but when I connect the other PC to the ad-hoc network it resets to the default IP 192.168.137.Something. You said to set the IP on both PCs? Before or after connecting/creating the network?
– Kyle V.
Mar 6 '13 at 23:02

I would describe that as a different IP, rather than a different IP range.
– Austin ''Danger'' Powers
Mar 4 '13 at 5:49

@Dan I meant "use the range 192.168.2.x" (as opposed to 192.168.1.x). The right term would be "different network" or "different subnet", but "different range" is less confusing.
– cpast
Mar 4 '13 at 5:52

This is promising but could you be more specific, How do I set these IP parameters?
– Kyle V.
Mar 4 '13 at 18:55

@StickFigs In Windows, under "Network Connections", right click the wireless interface, and hit "Properties". Click "TCP/IP version 4", and hit the configure button. Then, select "Manual IP" and enter these.
– cpast
Mar 4 '13 at 19:23

@cpast I tried setting the host IP to 192.168.2.1 but when I connect the other PC to the ad-hoc network it resets to the default IP 192.168.137.Something. You said to set the IP on both PCs? Before or after connecting/creating the network?
– Kyle V.
Mar 6 '13 at 23:02

|
show 4 more comments

draft saved

draft discarded

Thanks for contributing an answer to Super User!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

Some of your past answers have not been well-received, and you're in danger of being blocked from answering.

Please pay close attention to the following guidance:

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Jtdylktuy