adhoc resets itself?

[prominence]

hello there

i have two workstations, a desktop and a laptop. both are running win 7 ultimate x86. however, only my desktop is able to connect to the internet via a modem (wired network) and i need the laptop to be online as well. desktop is equipped with a tp-link wn321g usb wireless modem to transmit adhoc.

i searched around and chanced upon ad hoc connections, so i tried making one. while ad hoc connections are working, they sort of reset themselves after i close all the computers, and ad hoc won't work anymore. for example, i create an adhoc network, named HAUZ, and i saved the network. i will be able to connect via the laptop. if i close the desktop, or restart it, the adhoc connection can be connected, but there is no internet connection anymore.

if i recreate the adhoc, it will work as normal again. funny :/

i tried "hostednetwork" before, and strange, although "netsh wlan show drivers" shows that "hostednetwork" is supported, there is still some problems. so i decide to stick with adhoc...

so right now, i need to recreate an adhoc connection every time i need internet on my laptop. any solution to this?

thanks in advance

tldr; ad hoc doesn't work after close desktop

 

[whest]

Below is from the help file - it seems like recreating the adhoc makes sense - whats wrong with homegroup - normal - guess i need you to explain it more clearly- anyhow with my pc and laptop i set up homegroup plus live imesh, imesh will let you have access the same as remote control - since yours are ultimate - pro the prerequisite for remote you could just use remote with your 2 ultimate systems - setup a remote connection or use imesh to connect them if this suits - imesh requires you to have windows live essentials installed on both systems:
Set up a computer-to-computer (ad hoc) network
An ad hoc network is a temporary connection between computers and devices used for a specific purpose, such as sharing documents during a meeting or playing multiplayer computer games. You can also temporarily share an Internet connection with other people on your ad hoc network, so those people don’t have to set up their own Internet connections. Ad hoc networks can only be wireless, so you must have a wireless network adapter installed in your computer to set up or join an ad hoc network.
Click to open Network and Sharing Center.
Click Set up a new connection or network.
Click Set up a wireless ad hoc (computer-to-computer) network, click Next, and then follow the steps in the wizard.
Notes
If one or more of the networked computers is joined to a domain, each person using the network will need to have a user account on that computer to see and access shared items on it.
If the networked computers aren't joined to a domain, but you want to require people to have a user account on your computer to access shared items, turn on password-protected sharing in Advanced sharing settings.
To turn on password protected sharing
Click to open Advanced sharing settings.
Click the chevron to expand the current network profile.
If password-protected sharing is off, click Turn on password protected sharing, and then click Save changes. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
An ad hoc network is automatically deleted after all users disconnect from the network or when the person who set up the network disconnects and goes out of range of the other users of the network, unless you choose to make it a permanent network when you create it.
If you share your Internet connection, Internet connection sharing (ICS) will be disabled if you disconnect from the ad hoc network, you create a new ad hoc network without disconnecting from the old ad hoc network for which you enabled ICS, or you log off and then log back on (without disconnecting from the ad hoc network).
If you set up an ad hoc network and share your Internet connection, and then someone logs on to the same computer by using Fast User Switching, the Internet connection will still be shared, even if you didn't intend to share it with that person.

 

[prominence]

lol the whole thing bout the help file, i've been through that a lot of times ^^; i would explain everything in reference to the help file, but that'd be a long post lol

it seems like recreating the adhoc makes sense - whats wrong with homegroup - normal - guess i need you to explain it more clearly- anyhow with my pc and laptop i set up homegroup plus live imesh, imesh will let you have access the same as remote control - since yours are ultimate - pro the prerequisite for remote you could just use remote with your 2 ultimate systems - setup a remote connection or use imesh to connect them if this suits - imesh requires you to have windows live essentials installed on both systems:
Set up a computer-to-computer (ad hoc) network

and what's with all the "-"? i don't even understand your message @_@
i'm not really a fan of win live essentials... any other solutions?

 

[whest]

Whats the purpose for your adhoc ? have you thought about an wireless access point modem or just a new wireless modem - onboard lan to modem router to access point wireless - all wired then you create a network.

 

[whest]

The purpose of imesh or remote connection is you get your pc's desktop with full acess to everything on your laptop and you can run everything on the pc - to work on the laptop just minimise the window and then work on your laptop -its cool if you have sound on the PC you can open media player and play anything you like while you work he he

I should add its limited to internet's connection speed - also it would probably run slowly on poor spec machines - my pc has 4gb of memory and dual core processor and my laptop has a core i7 2630qm with 4gb of memory.

CONNECT FROM YOUR LAPTOP TO YOUR PC FROM WORK is the big advantage.

 

[whest]

 

[prominence]

Whats the purpose for your adhoc ? have you thought about an wireless access point modem or just a new wireless modem - onboard lan to modem router to access point wireless - all wired then you create a network.

my adhoc is to share internet connection between my desktop and laptop. yes, i know a wireless router made more sense, but i don't have the money
laptop is used upstairs while desktop stays immobile downstairs. a wire all the way up will be tough :/

The purpose of imesh or remote connection is you get your pc's desktop with full acess to everything on your laptop and you can run everything on the pc - to work on the laptop just minimise the window and then work on your laptop -its cool if you have sound on the PC you can open media player and play anything you like while you work he he

I should add its limited to internet's connection speed - also it would probably run slowly on poor spec machines - my pc has 4gb of memory and dual core processor and my laptop has a core i7 2630qm with 4gb of memory.

CONNECT FROM YOUR LAPTOP TO YOUR PC FROM WORK is the big advantage.

i see. i'll check imesh some time later
but i prefer a workaround on the adhoc... coz seems like the easiest solution at the moment. plus, i want to know why the adhoc connection acts this way :/

 

[whest]

Have you tried to keep it going by changing the power settings when you close the lid - thats whats diconnecting it i thought - just change sets to do nothing and likewise for the pc - it will waste money but i think thats it - or just change advanced power sets so the hard drives keep on, and the monitor is turned off.

 

[prominence]

Have you tried to keep it going by changing the power settings when you close the lid - thats whats diconnecting it i thought - just change sets to do nothing and likewise for the pc - it will waste money but i think thats it - or just change advanced power sets so the hard drives keep on, and the monitor is turned off.

the laptop has been already set to do nothing when it closes the lid. btw, i will need to shutdown both of the computers at the end of the day. but i saved the adhoc. but it still does not work after a shutdown or restart... i think its something to do with my desktop instead :/

 

[logicearth]

The adhoc network is temporary, not permanent. And there is no way to make it as such. You will always have to remake it everytime. It was never meant to be used as a permanent solution.

 

[prominence]

The adhoc network is temporary, not permanent. And there is no way to make it as such. You will always have to remake it everytime. It was never meant to be used as a permanent solution.

then a question...
why the option to save the network when creating the adhoc connection?

and, quoted from the help file courtesy of whest

An ad hoc network is automatically deleted after all users disconnect from the network or when the person who set up the network disconnects and goes out of range of the other users of the network, unless you choose to make it a permanent network when you create it.

saving the network does not mean making it a permanent network now?