ad hoc vs. infrastructure connection for new printer?

drpepper · 23 Dec 2012

I have read the Networking Posting Instructions. The ipconfig /all data returned is too long for an image; so I am attaching a txt file for inspection. I will flush the DNS cache after completing this post. In an effort to keep this post from being too long, I will reserve hardware and OS details for a later post.

The bottom line is I want pros, cons, and "is it possible" answers for a new addition to my home computer stuff. A newly remodeled study is about 30' away and has three walls between it and the original room used for computer work.

The original room has a desktop machine, router hardwired to the computer, and printer hardwired to the computer. The router serves as the access point for two laptops for printer and file sharing. One is in the new study.

The new study has a laptop which doubles as a desktop and a new wireless printer. The laptop currently shares the old printer and is hardwired to the new wireless printer. My desire is for the new printer to be used exclusively by the computer in the study. I have made an unsuccessful attempt to establish an ad hoc connection to the printer. (The manuals for the printer indicate that it is possible to do this.)

so:

Can I use an ad hoc connection for the wireless printer and maintain the existing network connection at the same time? I have read a couple of articles which indicate that the use of a virtual network connection will allow this with only one NIC. I have Microsoft Virtual WiFi Miniport Adapter showing in Device Manager.
Should I set up a WLAN connection instead using the existing sharing through the router and configure the permissions to allow only the computer in the study to use the wireless computer?
Do I need to manually set the IP address for the wireless computer?
I am sure that I will need some step-wise instructions for configuring everything to work in reliably.

Thanks for your help.
drpepper

drpepper · 24 Dec 2012

I spent a couple of days trying to install and debug an ad hoc printer connection without success. An infrastructure connection works fine.

chev65 · 24 Dec 2012

With 3 walls the wireless signal will usually not be very good depending on many factors. Most printers, like mine, can only be set up to use one connection at a time.

Ad Hoc is only for sharing a wireless connection, wireless to wireless, not wired to wireless, which makes it rather useless in most scenarios.

My thought being that if you already have a wireless connection available then why would anyone need to create a hot spot in the first place?

The only reason I can think of is to create a private wireless network which is outside the regular network. Or you could use it as a wireless repeater to increase signal strength for other machines that are too far away from the router to obtain a good connection. Or possibly if someone only had a wireless modem to create a wireless access point so others could use the connection.

Yes the Msoft Virtual WiFi miniport adaptor is for creating a hosted wireless network but like I mentioned earlier, it's only meant to create a hosted wireless network or wireless A/P, wireless to wireless is supported, wired to wireless is not supported.

Only the machine with drivers for the new printer can be used to print on that printer. So not installing the printer drivers on the other machines would prevent them from using that printer.

The link below has more links to websites that show a few different ways that you can create a hosted wireless network using the command prompt or connectify software.

One of the links is for a virtual router.

Turn Windows 7 laptop into a wifi hotspot

drpepper · 24 Dec 2012

My initial reasoning for attempting an ad hoc connection was two-fold.

The first was throttled by explicit warnings in the setup guide about distance and walls, furniture, etc. It even said that a couch or desk between the printer and the router may cause problems. I was scratching my head about this because file and printer sharing with the same layout did not pose a problem. Too many times I have been tripped up by not paying attention to the instructions; so I put the infrastructure connection on the back burner.

The second was that I have never attempted an ad hoc connection. My planned connection fit the definition well. Use a wireless connection between a computer and a printer. What a no-brainer??!! Once I had finished the installation, the printer was off line. No attempts to change that status succeeded. I thought it would be a good experience to try it.

With our other printer, I shared it with the desktop computer and two desktops. That printer is connected by USB to the desktop. I did not need to load any drivers to the laptops.

Printer access was too easy. During the installation I had an opportunity to disable sharing.