I have a windows 7 laptop that has both a wired and wireless connection. The wired is plugged into an internet connection. I've setup the wireless to be the ad hoc network connection. I can connect, but it does not serve out any IP Addresses or DNS. Is that normal or be design? I can configure that information on the clients connecting and it works fine, but why doesn't it automatically assign the information needed? Or am I missing something?Jeff

Hi, Ad hoc network should provide IP address. Right-click on your Internet connection's icon. Do not click on the icon for your ad-hoc network. Click "Properties." The "Status" window that appears will display your Internet connection's IP address, which will also be the IP address that your ad-hoc network is using. Furthermore, you can type ipconfig /all in command prompt to check if your pc get IP address from ad hoc network. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks for the reply. Here is my network information. My wireless is being used for the ad hoc connection. It does not server up IP addreses. I've set this up on my computer and another computer and got the same results. What am I missing? Wireless LAN adapter Wireless Network Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Linksys WUSB600N Wireless-N USB Network dapter with Dual-Band ver. 2 Physical Address. . . . . . . . . : 68-7F-74-75-FE-E4 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::6da1:3c0f:14b6:adc6%21(Preferred) IPv4 Address. . . . . . . . . . . : 169.254.173.198(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : DHCPv6 IAID . . . . . . . . . . . : 359169908 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-D6-8C-BC-B8-AC-6F-AB-BC-C DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%2 fec0:0:0:ffff::2%2 fec0:0:0:ffff::3%2 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) 82578DM Gigabit Network Connect on Physical Address. . . . . . . . . : B8-AC-6F-AB-BC-C2 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 10.200.9.2(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : 10.200.2.25 DNS Servers . . . . . . . . . . . : 10.200.2.12 10.200.2.1 10.201.2.1 NetBIOS over Tcpip. . . . . . . . : Enabled Jeff

Hi, Right-click on your Internet connection's icon. Do not click on the icon for your ad-hoc network. Click "Properties." The "Status" window that appears will display your Internet connection's IP address, which will also be the IP address that your ad-hoc network is using. Furthermore, you can type ipconfig /all in command prompt to check if your pc get IP address from ad hoc network. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, I find a similar thread: http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/2fbef216-19e8-4862-893f-fb3c8ae669ea/ You can try the suggestion form Arthur. Also this case may helpful to you: http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/652643ed-c43d-463b-a437-93e7007836f1 Hope that helps. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I have a windows 7 laptop that has both a wired and wireless connection. The wired is plugged into an internet connection. I've setup the wireless to be the ad hoc network connection. I can connect, but it does not serve out any IP Addresses or DNS. Is that normal or be design? I can configure that information on the clients connecting and it works fine, but why doesn't it automatically assign the information needed? Or am I missing something? Jeff Hi, this is b'cos without DHCP server, PC can't have any ip. DHCP server is not installed in Windows XP/Vista/7, but can be configured in Windows server. You have to Provide manually IP to Wireless NIC TCP/IPv4. remember two or more NIC installed in same PC can't be in a same Network/SubNet. here, use this ip range - 192.168.137.1/255.255.255.0 for wireless card (as you have shared internet connection from wired LAN) for Client PC having wireless card & will be using this Ad Hoc server must have ip starting from 192.168.137.2 to 192.168.137.254 subnet 255.255.255.0 (same) & use Default gateway - 192.168.137.1 & DNS Servers - 192.168.137.1 Harjit

I have seen both of these links, but the first one indicates installing an intel driver. The card I am using is for ad hoc is a linksys? Or does the intel driver help with the nic connected to the internet?Jeff

I'm not sure what you mean by this? If I configure the IP Addresses manually I can get out to the internet. I'm trying to get windows 7 to hand out the addresses. Are you saying windows 7 does not do that? I would agree from what I've seen, but others have suggested that Windows 7 does hand out IP addresses.Jeff

Hi, I found an article about IP address from Ad hoc network in Windows XP but I think it should the same principle in Windows 7: http://www.microsoft.com/windowsxp/using/networking/expert/bowman_02april08.mspx Instant Private Networking Not only does ad hoc wireless networking provide a lower cost method to share an Internet connection than a more expensive wireless router/router plus separate access point solution, but it affords a fast and simple way of establishing a means to share data and documents for groups with no external LAN or Internet connection. With no available DHCP server, Windows XP provides an automatic private IP address between 169.254.0.0 and 169.254.255.255 to network adapters. So the IP address on your PC 169.254.173.198 seems provide from Ad hoc. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

The problem is when I let the client computer try to obtain an IP Address it does, but not from the host. It just eventually times out and selects a 169.254 address. The difference is if the host was handing out the 169.254 address it would also hand out a Gateway. My client does not receive a gateway or dns.Jeff

Hi, I have tested on my machine, and seem ad hoc does not provide IP address. In An ad-hoc network is a direct connection between two computers, there is no DHCP server to give out IP addresses. Therefore, you will get an auto-assigned IP address of 169.254.x.x. So that’s not a problem, it’s by design. Seven

Hi Jeff, Did your problem solved by the suggestion of Seven Matin? Please feel free to give me any update. Thanks. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I guess if that is the answer. I figured that out already, I was just surprise to realize that MS didn't setup DHCP for adhocs. I was checking into to see if there was something I was missing. I guess not.Jeff