Are the arp requests from the affected workstations completing? Are
the entries on the arp table on the FW and on the workstation? What
does a wireshark sniff say?

Vista did the same behavior reaching out to a web site to determine if
the Internet was available. I believe there is an option or a regedit
to turn it off...

On Sat, Sep 11, 2010 at 3:33 PM,  <hay...@sages.us> wrote:
> Thanks for the info, Tom.  This will help.
>
>
> Quoting "Steele, Thomas C" <tste...@manteno5.org>:
>
>> We have been seeing something similar off and on with our Win7 machines -
>> the network & sharing center would show that we did not have a connection to
>> the Internet, even though everything looked good in ipconfig /all and the
>> system tray would have a warning symbol on the network icon.  After some
>> extensive internet research via google, I found a lot of possible causes...
>>
>> 1) It seems Vista and Win7 have some kind of "phone home" pinging
>> mechanism that the OS uses to determine if it is reaching the Internet.  If
>> the sites or at least responses from those sites that the OS is looking for
>> do not get returned to the workstation, then the OS assumes that it has no
>> connection to the Internet, though internal connections to the LAN are fine.
>>  It is conceivable that a firewall/filter (such as IPCop) might be blocking
>> the sites the OS is trying to hit to determine if it has Internet
>> connectivity.  If this is the case, it should show up in a wireshark trace
>> but I have not tried it to confirm.
>>
>> 2) Some reported a specific issue with Symantec Endpoint Security (again,
>> possibly related to Symantec's local firewall - we don't use Symantec so
>> that was not our issue).
>>
>> 3) Apple's Bonjour service has been reported to cause this kind of
>> activity (though it was not installed on the machines we were having issues
>> with that I am aware of)
>>
>> 4) Problems with older versions of Intel's NIC drivers (ours were most
>> recent, though)
>>
>> 5) Problems with IPv6.  By default Vista and Win 7 have native support for
>> both IPv6 and IPv4.  If the rest of the network is only configured for IPv4
>> some have suggested disabling IPv6 on the client.  This did the trick for us
>> on one problematic workstation (running our access control software, which
>> may also have been part of the problem).
>>
>> In our case this is very sporadic and seems to have pretty much gone away
>> (maybe something fixed in a Windows update?).  When it does occur, I have
>> found that disabling and re-enabling the network connection seems to work.
>>
>> -TS
>>
>>
>> -----Original Message-----
>> From: tech-geeks-boun...@tech-geeks.org
>> [mailto:tech-geeks-boun...@tech-geeks.org] On Behalf Of hay...@sages.us
>> Sent: Saturday, September 11, 2010 10:07 AM
>> To: Tech-Geeks Mailing List
>> Subject: Re: [tech-geeks] Vista/7 not connecting to network
>>
>> For those of us who are using IPCop, it looks like it is time that we
>> either find a solution for this issue - it arose in our district again
>> last week with two new laptops running Windows 7 - or find a
>> replacement for IPCop that does not have this issue.
>>
>> Now, if one of us comes up with a solution we need to agree so
>> share........
>>
>>
>> Quoting Charlie Niehaus <cnieh...@altamont.k12.il.us>:
>>
>>> I have (soon had I hope) the same issue with Windows 7 and IPCop.
>>> Never did find a solution.  There are tohers that did not see the
>>> issue with IPCop and Windows 7 - so I am assuming it is either a
>>> configuration issue with IPCop (Best Bet) or somthing with a switch
>>> along the way.  i was lucky enough to solve it by giving the
>>> computer in question an external IP and trusting the user (My
>>> Superintendent) to not break any AUP rules.  Not sure how that is
>>> going though.
>>>
>>> ----- Original Message ----- From: "Jared Lynn" <jl...@porta202.org>
>>> To: "Tech-Geeks Mailing List" <tech-geeks@tech-geeks.org>
>>> Sent: Friday, September 10, 2010 12:19 PM
>>> Subject: [tech-geeks] Vista/7 not connecting to network
>>>
>>>
>>>> I'm hoping somebody on here has experienced this and has a solution
>>>> to this very annoying problem. I have a couple of newly purchased
>>>> windows 7 machines and a single vista machine that are trying to
>>>> connect to get past my Router. DHCP hands out a valid IP and points
>>>> to the right places but from there, the Default Gateway doesn't
>>>> acknowledge that the machine exists. I can ping and access all
>>>> internal servers but can not ping the Default Gateway. FYI, the
>>>> Default Gateway is our CIPAFilter that has no problems with XP or
>>>> OS X 10.6. Any comments or thoughts as to what might be occurring
>>>> would be greatly appreciated.
>>>>
>>>> As always, You stay Classy Internet.
>>>> Thanks,
>>>> Jared Lynn
>>>> PORTA CUSD #202 Technology Coordinator
>>>> Email: jl...@porta202.org
>>>> Phone: 217-501-4920
>>>>
>>>> | Subscription info at http://www.tech-geeks.org |
>>>>
>>>
>>> | Subscription info at http://www.tech-geeks.org |
>>>
>>
>>
>>
>>
>> | Subscription info at http://www.tech-geeks.org |
>> | Subscription info at http://www.tech-geeks.org |
>>
>
>
>
>
> | Subscription info at http://www.tech-geeks.org |
>



-- 
"Don't ask yourself what the world needs. Ask yourself what makes you
come alive and then go do that. Because what the world needs is people
who have come alive." -Dr. Howard Thurman

******************************
Aaron Keith Hackney
aa...@aaronkeithstudios.com
Cell 210.325.2196
******************************
| Subscription info at http://www.tech-geeks.org |

Reply via email to