Member Avatar for overlook
overlook 0 Newbie Poster

Hi,

I have 2 notebooks, one using vista and one using 7. I just set up the ad-hoc (win 7) and connected sucessfully using other notebook (vista)

I set up the IP for wireless in win-7using subnet and the client(vista) using subnet 255.255.255.0. The win7 is connected to the internet using LAN, and I am hoping that the vista that is already connected to win7 via ad-hoc also can connect to the internet.

What additional configuration that I can use so both notebooks can browse to the internet?

Thank you

--
solved
I used dhcp, and I go through share internet options but for LAN. Previously, I did it for wlan, that's why it did not work.

Edited by overlook because: solved
  • 1 Contributor
  • 0 Replies
  • 120 Views

Dani AI

Generated

A short expert follow-up to ’s thread with a compact checklist and an alternative so the same setup works reliably long after this thread was posted.

Common checklist for ad‑hoc Internet sharing

  • On the machine that has Internet, enable Internet Connection Sharing on the adapter that actually provides the Internet (the wired NIC when using a LAN uplink). Sharing the wrong adapter is the usual cause of “connected but no Internet.”
  • On the client, set IPv4 to obtain IP and DNS automatically so the host can assign addresses. Verify the client receives an IP, gateway and DNS from the host.
  • If it still fails, temporarily disable firewalls/third‑party security on the host to rule out blocked forwarding. Confirm the Windows service named Internet Connection Sharing (SharedAccess) is running.
  • Test in stages: ping the host’s shared‑adapter IP from the client, then ping a public IP (for example 8.8.8.8) to separate DNS problems from routing problems.

A more reliable alternative to legacy ad‑hoc: create a software access point on the Windows 7 host (if the wireless driver supports it). Example commands (run in an elevated prompt):

netsh wlan set hostednetwork mode=allow ssid=MyHotspot key=MyPassword
netsh wlan start hostednetwork

After starting the hosted network, share the Internet connection to the newly created virtual adapter from Network Connections. The virtual AP approach behaves more like an infrastructure AP and often avoids quirks of peer‑to‑peer ad‑hoc mode.

Troubleshooting notes

  • Use ipconfig /all on both machines to inspect IP/gateway/DNS.
  • If the client can ping IPs but not resolve names, fix DNS on the host or set a public DNS on the client.
  • For persistent use, a real wireless router/AP or a USB travel hotspot is simpler and more robust than ad‑hoc.
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.