Member Avatar for jakesee

Hi all,

Hope you can help. Thanks.

I want to set up a network where:
1. a single host computer gets wireless internet connection from a office wireless access point.
2. the host computer broadcasts the wireless internet connection.
3. client computers can log on to the broadcasted wireless internet connection.

What are the network adapters and configuration required on the host computer? I think I have done something like that before using a single Wireless adapter and ICS on Windows XP, but I can't figure it out on Vista.

Which IP should I monitor if i want to set up a login page for the broadcasted signal?


Thanks!

  • 2 Contributors
  • 2 Replies
  • 188 Views
  • 3 Days Discussion Span
  • Latest Post Latest Post by jakesee

Dani AI

Generated

Short version: a PC can act as a gateway, but the reliable way on Vista is to give the host two network interfaces — one that stays joined to the office AP (internet-facing) and a second that advertises the guest network — or to use a single adapter only if its driver explicitly supports a “virtual AP”/SoftAP mode. ’s experience with XP fits this: XP drivers sometimes exposed SoftAP/ad‑hoc features that worked; Vista-era drivers are the usual limiting factor. is correct that normal AP hardware ordinarily does the broadcasting, but a host PC can do it when the adapter/driver or a second NIC makes an access point possible.

Practical steps (two‑adapter approach — the simplest, most compatible):

  • Install a second NIC (USB Wi‑Fi or wired to a small AP set as an AP).
  • Join the office wireless with the primary adapter.
  • In Network Connections, right‑click the internet-facing adapter → Properties → Sharing → enable “Allow other network users to connect…” and select the internal adapter. Windows ICS will usually set the shared adapter to 192.168.0.1 and provide DHCP to clients.
  • Confirm addresses with:
C:\> ipconfig /all

Which IP to monitor for a login page: monitor the host’s LAN/gateway IPv4 (the internal adapter); with ICS that is typically 192.168.0.1. A captive‑portal is usually implemented by hosting a web page on that IP and combining DNS hijack or firewall/NAT rules to redirect HTTP to the page. Note that HTTPS cannot be transparently redirected without certificate warnings, so for a robust, secure captive portal and true guest isolation a dedicated gateway/router or firmware with captive‑portal support is recommended.

Troubleshooting/security notes: single‑adapter setups fail when the driver lacks SoftAP; ad‑hoc is limited and often doesn’t support modern encryption; if clients get no IP, restart the host and re‑enable ICS; use Windows Firewall rules to block guest access to office subnets; verify corporate policy before sharing an office connection.

Recommended Answers

All 2 Replies

Member Avatar for hughv

Why would you want to do this?
Broadcasting the signal is handled by the hardware in the access point, and I don't see how a computer can do this. There are many things I don't know, but this sounds very strange to me.

Member Avatar for jakesee

Why would you want to do this?

Just exploring possibilities. One use could be that when visitors come to the office, I can let him connect through the host computer instead of directly to the office wireless network, so that there is an extra layer of protection from the office network and there is no need to reveal the WEP passcode.

Maybe I'll just wait for someone who knows alot to answer this problem. But ICS on XP definitely worked the other time I tried. I just could not do it on Vista.

Edited by jakesee because: n/a
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.