The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Lost Internet connection via wireless ad hoc

    Discussion in 'Networking and Wireless' started by ATG, Nov 2, 2008.

  1. ATG

    ATG 2x4 Super Moderator

    Reputations:
    3,306
    Messages:
    4,461
    Likes Received:
    344
    Trophy Points:
    151
    Hi all

    I have two laptops with wireless ad hoc connection. One of them("sever") is connected directly to Internet(ADSL) using a router. The second laptop connects to the Internet using the wireless connection.

    Today, looking at my "Event Viewer" on my "server" laptop I noticed a lot of errors - "The ICS_IPV6 failed to configure IPv6 stack". And because lately I have troubles with Internet and I didn't know(still don't know) if this error can somehow be related I looked it over in Google and I saw a suggestion to reinstall IPv6. I did that, restarted and I never seen the IPv6 error for a whole day so I guess this is solved.
    Just know however I tried to use my another laptop to connect to Internet and it seems that I can't. Tried to created another wireless connection didn't solve the issue. Reactivated ICS(got a few "The service cannot accept control messages at this time" messages) - I got nothing. I checked again the "Event Viewer" on the server and guess what new type of network errors:

    - The ICS_IPV6 was unable to allocate bytes of memory. This may indicate that the system is low on virtual memory, or that the memory manager has encountered an internal error.

    - The DHCP allocator has disabled itself on IP address 169.254.219.17, since the IP address is outside the 192.168.0.0/255.255.255.0 scope from which addresses are being allocated to DHCP clients. To enable the DHCP allocator on this IP address, change the scope to include the IP address, or change the IP address to fall within the scope.

    The problem is only Internet, I have several folders shared on the server and I can access them and run files from them via the wireless connection.

    The "server" is using Vista Home Basic 32bit, the "client" - Windows Xp SP3.

    I'm downloading Wireshark now, and I'll try to post some diagnostic...

    Wireshark running on the server, monitoring the attempt of the "client" to access www.microsoft.com:
    -------------------------------------------------------------------------------------------------------------------------------
    "No", "Time", "Source", "Destination", "Protocol", "Info"
    -------------------------------------------------------------------------------------------------------------------------------
    "4","1.010059","192.168.0.24","192.168.0.1","DNS","Standard query A www.microsoft.com"

    "5","1.056335","192.168.0.1","192.168.0.24","DNS","Standard query response CNAME toggle. www.ms.akadns.net CNAME g. www.ms.akadns.net CNAME lb1. www.ms.akadns.net A 207.46.193.254 A 207.46.19.254 A 207.46.19.190 A 207.46.192.254 A 65.55.12.249 A 65.55.21.250"

    "6","24.813442","192.168.0.24","192.168.0.1","TCP","search-agent > icslap [RST, ACK] Seq=1 Ack=1 Win=0 Len=0"
    -------------------------------------------------------------------------------------------------------------------------------
    192.168.0.24 <---- "client" IP
    192.168.0.1 <---- "client" Getaway & DNS
    Monitoring stopped when the "client" get browser's error message: "The server is taking too long to respond".
     
  2. makaveli72

    makaveli72 Eat.My.Shorts

    Reputations:
    1,235
    Messages:
    2,108
    Likes Received:
    0
    Trophy Points:
    55
    Okay, here are my suggestions.

    IMO you do not need IPv6 running at this moment...your computer uses IPv4 as of now and is being assigned IPv4 addresses. The first thing I would do is disable IPv6 on both computers...It is not needed!

    Find your network connections folder on both computers; Do a Start--> Run and type ncpa.cpl and hit enter. Right click on all the Network Adapters you have, select Properties and take out all checks that relates to IPv6. Click ok and restart the computers.

    After the computers restarts

    The next step I would do is check that the required services are started. Do a Start--> Run and type services.msc and hit enter. Look for the DNS and DHCP Client services, the Windows Firewall/Internet Connection Sharing Service, WorkStation and Wireless Zero Configuration Services and set all of them to Automatic and Start them.
     
  3. ATG

    ATG 2x4 Super Moderator

    Reputations:
    3,306
    Messages:
    4,461
    Likes Received:
    344
    Trophy Points:
    151
    Thank you for your response.

    IPv6 - disabled

    All services are running and set to "Automatic", but I don't see "Wireless Zero Configuration Services" in the list. Is that normal?

    Forgot to mention - the "server" laptop has Atheros 5007EG and the "client" has ASUS Wireless(it's on a almost 4 years old ASUS laptop)
     
  4. makaveli72

    makaveli72 Eat.My.Shorts

    Reputations:
    1,235
    Messages:
    2,108
    Likes Received:
    0
    Trophy Points:
    55
    Okay, you're doing these steps for Both computers.

    .Vista will say WLAN AutoConfig as the Service name.

    And it's okay if you don't see IPv6 on the XP Machine.
     
  5. ATG

    ATG 2x4 Super Moderator

    Reputations:
    3,306
    Messages:
    4,461
    Likes Received:
    344
    Trophy Points:
    151
    OK done.

    All is running and set to "Automatic" on both laptops. Just notices that the "client" cannot ping the "server". But the "server" can ping the "client". File sharing still working..
     
  6. makaveli72

    makaveli72 Eat.My.Shorts

    Reputations:
    1,235
    Messages:
    2,108
    Likes Received:
    0
    Trophy Points:
    55
    Ad-Hoc working again?

    The pinging issue may be due to a firewall/antivirus program on the client machine blocking ping packets.
     
  7. ATG

    ATG 2x4 Super Moderator

    Reputations:
    3,306
    Messages:
    4,461
    Likes Received:
    344
    Trophy Points:
    151
    Ad-Hoc, yes.

    There is no firewall/antivirus software on the client laptop. Even Windows Firewall is turned off.
     
  8. flipfire

    flipfire Moderately Boss

    Reputations:
    6,156
    Messages:
    11,214
    Likes Received:
    68
    Trophy Points:
    466
    IPv6 is for the future, when we run out of addresses.

    No need for it now ;)
     
  9. ATG

    ATG 2x4 Super Moderator

    Reputations:
    3,306
    Messages:
    4,461
    Likes Received:
    344
    Trophy Points:
    151
    Yeah I know IPv6 is the future successor of IPv4 but Vista had it installed by default and all my troubles started when I reinstalled IPv6(actually what I did is uncheck the box of IPv6, click OK, then check the box again, click OK I don't know if this counts as reinstalling). I guess it was just a coincidence I lost internet connection..
     
  10. ATG

    ATG 2x4 Super Moderator

    Reputations:
    3,306
    Messages:
    4,461
    Likes Received:
    344
    Trophy Points:
    151
    Ok problem source detected.

    Yesterday I updated my Comodo firewall on the server laptop. All my settings are fine but I guess it did something to my wireless network. I'm sure because when I turn the firewall off I do have an internet connection.

    Honestly I didn't expect a firewall upgrade could do that.....
    Trying to fix it now.....
     
  11. makaveli72

    makaveli72 Eat.My.Shorts

    Reputations:
    1,235
    Messages:
    2,108
    Likes Received:
    0
    Trophy Points:
    55
    Yea Comodo could be a pain in the @** sometimes when you want to do certain networking stuff. For ex. Remote Desktop, File Sharing and trusting other computers on the network. I've had my share of headaches w/ it but I still like it nonetheless.

    * And BTW I was suppose to ask you what firewall/antivirus is on the Server computer instead of the Client...seeing that it's the Client that couldn't ping the Server. But you've figured out the issue now so....
     
  12. vinumsv

    vinumsv MobileFreak™

    Reputations:
    502
    Messages:
    1,238
    Likes Received:
    0
    Trophy Points:
    55
    try using a proxy server instead of ICS mate
     
  13. ATG

    ATG 2x4 Super Moderator

    Reputations:
    3,306
    Messages:
    4,461
    Likes Received:
    344
    Trophy Points:
    151
    How? And why is that better? :)


    Btw, I'm diggin in Comodo's setting for 20minutes now and I cannot solve this out :mad:
     
  14. makaveli72

    makaveli72 Eat.My.Shorts

    Reputations:
    1,235
    Messages:
    2,108
    Likes Received:
    0
    Trophy Points:
    55
    Yea I know...it could be very difficult to work w/ sometimes. And i've personally haven't got the hang of it yet. IDK, try messing with the Advanced settings under the Firewall section...try setting an IP Scope.

    Best of luck w/ it. I'm actually having an issue trying to Remote Desktop into a computer at home; Comodo seems to be blocking it, but I can use the same said computer to Remote into another machine on the network. I've tried all kinda things, adding rules etc. but it still wouldn't allow access. I think it's a glitch in the software maybe. But yea...it can be very un-cooperative sometimes.

    You may want to uninstall it completely and then re-install, when it detects the network allow it. Just a suggestion...something I may have to do.
     
  15. ATG

    ATG 2x4 Super Moderator

    Reputations:
    3,306
    Messages:
    4,461
    Likes Received:
    344
    Trophy Points:
    151
    Yeah I think reinstallation is my best shot although I'll have to train Comodo again.

    Thank you very much for all your help.
     
  16. ATG

    ATG 2x4 Super Moderator

    Reputations:
    3,306
    Messages:
    4,461
    Likes Received:
    344
    Trophy Points:
    151
    Update and closure;

    After 1,5 hours of trying to reconfigure Comodo, uninstall/install Comodo I gave up. Comodo Firewall is gone now, Online Armor installed.
    No connection problems so far but that could mean low protection level by OA...
     
  17. makaveli72

    makaveli72 Eat.My.Shorts

    Reputations:
    1,235
    Messages:
    2,108
    Likes Received:
    0
    Trophy Points:
    55
    :D Hehe...I wouldn't go so far as to uninstall it for good. But you gotta do what ya gotta do.
     
  18. Hiker

    Hiker Notebook Deity

    Reputations:
    448
    Messages:
    1,715
    Likes Received:
    1
    Trophy Points:
    56
    For such issues you's really be better off asking on the Comodo forums.
     
  19. Shyster1

    Shyster1 Notebook Nobel Laureate

    Reputations:
    6,926
    Messages:
    8,178
    Likes Received:
    0
    Trophy Points:
    205
    Not only is there no need for it, but since IPv6 as currently implemented tunnels through IPv4, it can actually pose a security threat since not all security apps know to check IPv6 packets properly.

    It was rather ... thoughtless of MS to have IPv6 enabled by default on _Vista; best for now to just keep it disabled.