Windows 7 Pro when working with ISA Server 2004 shows network error (yellow exclamation mark and X red cross)
Hello at all.
I think the problem is in windows 7 but It involves Isa server; I hope not to be off topic.
My network is a SBS 2003 domain with 40 PC all with Windows XP Pro SP3.
The network uses ISA 2004 SBS server (4.0.2167.909 SP3 version) and all PCs use the ISA Firewall Client (latest version 4.0.3442.654 downloaded from Microsoft). For some time I have installed in this network 2 PCs with Win7 x86 Pro Sp1. On these 2 PC
I always had the message "no internet access" (yellow triangle with exclamation mark) and X red on the network view. Until now I had not been important attention to this warning because the web browsing worked well.
Now I needed to configure on this 2 pc Outlook 2010 to use an external mail provider and I know that I cannot reach the external server. If I do "ping external_mail_name_server" get "could not find
host ...." and I have not the ip resolution. (NSLookup it get the resolution IP). I have activate the monitoring in ISA server but does not have any drop, and no block of packets.
If I configure the 2 PCs so that they do not use ISA server as a gateway (but I use another ADSL connectivity in my company that does not use the ISA server,
but only by the perimetral firewall) everything works perfectly (that exclude implications of the embedded windows 7 firewall )
All the other PCs with Windows XP + Isa firewall client that using ISA server does not have any problems and outlook2010 works without problems to external SMTP or POP3 server; when I ping the external server,
always I get the ip resolution.
On these 2 PCs whit Windows 7 I have: uninstalled the antivirus software (Symantec SEP 11.0.6300), I disabled IPV6 (by protocol on network configuration), I
uninstalled ISA Firewall Client, and I set IE to have the ISA proxy server , but the problem remains (network with yellow exclamation mark and red cross and the inability to use other services like pop3 and smtp, only http works)
At this point it seems that the problem is when use of win7 with ISAServer 2004.
Can You help my t resolve this problem?
Thanks a lot
March 7th, 2012 10:04am
ISA client seems to be very old.Update your client
http://www.microsoft.com/download/en/details.aspx?id=10193Regards, Kalyan.
Free Windows Admin Tool Kit Click here and download it now
March 9th, 2012 9:49am
Maybe that my post was too
long but if you read well I already use
the latest client (ver 4.0.3442.654 from Microsoft download)
for some time.
Moreover, the problem occurs even without the isa firewall client.In the
post I detailed the situation and the tests done
so far...
Thanks a lot
March 9th, 2012 5:04pm
Hi,
I would like to share the following information with you.
Network Connectivity Status Indicator (NCSI) is a feature since new Windows Vista.
It is designed to be responsive to network conditions, so it examines the connectivity of a network in a variety of ways. One test failed, NCSI may report a error, even if the networking actually can be accessed fully.
For example, NCSI tests connectivity by trying to connect to
http://www.msftncsi.com, a simple Web site that exists only to support the functionality of NCSI. Please try to manually visit the following website, you should see Microsoft NCSI.
http://www.msftncsi.com/ncsi.txt
For more information about NCSI, you can refer to the following article:
Appendix K: Network Connectivity Status Indicator and Resulting Internet Communication in Windows Vista
http://technet.microsoft.com/en-us/library/cc766017.aspx
Sometimes, we can access the http://www.msftncsi.com/ncsi.txt file in IE, but the NCSI still fails. It is because the NCSI traffic is not sent via IE but via WinHTTP component and use proxy specially. A proxy
server which requires user authentication won't allow it access Internet. Basically, NCSI must perform extra steps in an environment that has proxy servers. Web Proxy Automatic Discovery (WPAD) proxy detection is recommended. If WPAD is not used, configure
WinHTTP proxy settings to help NCSI:
netsh winhttp set proxy command
For more information:
TechNet article Automatic Discovery for Firewall and Web Proxy Clients
http://www.microsoft.com/technet/isa/2004/plan/automaticdiscovery.mspx
927551 Windows Vista Support WebCast: Troubleshooting Network Issues on Windows Vista - New Network Diagnostics
http://support.microsoft.com/default.aspx?scid=kb;EN-US;927551
937151 You cannot connect to the Internet from a Windows Vista-based computer that uses a local .pac file
http://support.microsoft.com/default.aspx?scid=kb;EN-US;937151
If you check the setting below and the problem still occurs. You could ask this question in Forefront TMG and ISA Server forum:
http://social.technet.microsoft.com/Forums/en-US/Forefrontedgegeneral/threads
Hope that helps
William Tan
TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
March 11th, 2012 10:20pm
Hi,
I would like to share the following information with you.
Network Connectivity Status Indicator (NCSI) is a feature since new Windows Vista.
It is designed to be responsive to network conditions, so it examines the connectivity of a network in a variety of ways. One test failed, NCSI may report a error, even if the networking actually can be accessed fully.
For example, NCSI tests connectivity by trying to connect to
http://www.msftncsi.com, a simple Web site that exists only to support the functionality of NCSI. Please try to manually visit the following website, you should see Microsoft NCSI.
http://www.msftncsi.com/ncsi.txt
For more information about NCSI, you can refer to the following article:
Appendix K: Network Connectivity Status Indicator and Resulting Internet Communication in Windows Vista
http://technet.microsoft.com/en-us/library/cc766017.aspx
Sometimes, we can access the http://www.msftncsi.com/ncsi.txt file in IE, but the NCSI still fails. It is because the NCSI traffic is not sent via IE but via WinHTTP component and use proxy specially. A proxy
server which requires user authentication won't allow it access Internet. Basically, NCSI must perform extra steps in an environment that has proxy servers. Web Proxy Automatic Discovery (WPAD) proxy detection is recommended. If WPAD is not used, configure
WinHTTP proxy settings to help NCSI:
netsh winhttp set proxy command
For more information:
TechNet article Automatic Discovery for Firewall and Web Proxy Clients
http://www.microsoft.com/technet/isa/2004/plan/automaticdiscovery.mspx
927551 Windows Vista Support WebCast: Troubleshooting Network Issues on Windows Vista - New Network Diagnostics
http://support.microsoft.com/default.aspx?scid=kb;EN-US;927551
937151 You cannot connect to the Internet from a Windows Vista-based computer that uses a local .pac file
http://support.microsoft.com/default.aspx?scid=kb;EN-US;937151
If you check the setting below and the problem still occurs. You could ask this question in Forefront TMG and ISA Server forum:
http://social.technet.microsoft.com/Forums/en-US/Forefrontedgegeneral/threads
Hope that helps
William Tan
TechNet Community Support
March 12th, 2012 5:16am
thanks this is very interesting about NCSI!!
I found something to work. I
found that manually setting the parameters
tcp/ip for the network adapter everything works
and I have not the red cross and not have the yellow exclamation mark.
Could it be a problem due to the dhcp
of domain?
In fact if I leave the automatic Ip settings(by dhcp) and view the ip parameters by
"ipconfig/ all" I see is not set
the default gateway parameter.
What do you think?
Thanks
Free Windows Admin Tool Kit Click here and download it now
March 13th, 2012 12:27pm
I think I foundthe solutionto the problem!
I realizedthat by doing"ipconfig/ all"on anynetwork client, thedefaultgatewayparameterhad no value.
By manually settingthe network parametersandby includingthegateways,PCswithWin7work properly andwithoutwarningnetworkor
theredcross.I checked thedhcp(dhcpsbs2003)and in factlacked the"scopeoptions"type"003router".Iset
thisadditionalscopeand nowthe clients receivethe valueof"defaultgateway"and thePC withwin7works
very wellwithout showinganywarningon the network.Probably thePC withwin7are moresensitive tonetwork parametersare
not perfectlycorrect andwarntheexclamtionmarkand /or theredcross.In conclusiondid not depend onISAorISAFirewallclient
or the windows
7 firewall but
the lack of default gateway (scope router)
in the DHCP network parameters.
Thank you all for your support.
March 17th, 2012 4:05am
I think I foundthe solutionto the problem!
I realized that by doing "ipconfig /all" on any network client, the default gateway parameter had no value.
By manually setting the network parameters and by including the gateways, PCs with Win7 work properly and without warning network or the red cross. I checked the dhcp (dhcp sbs 2003) and in fact lacked the "scopeoptions" type "003router". I set this additional
scope and now the clients receive the value of "defaultgateway" and the PC with win7 works very well without showing any warning on the network. Probably the PC with win7 are more sensitive to network parameters are not perfectly correct and warn the exclamtion
mark and/or the red cross. In conclusion did not depend on ISA or ISA Firewall client or the windows 7 firewall but the lack of default gateway (scope router) in the DHCP network parameters.
Thank you all for your support.
Free Windows Admin Tool Kit Click here and download it now
March 17th, 2012 11:00am
I think I foundthe solutionto the problem!
I realized that by doing "ipconfig /all" on any network client, the default gateway parameter had no value.
By manually setting the network parameters and by including the gateways, PCs with Win7 work properly and without warning network or the red cross. I checked the dhcp (dhcp sbs 2003) and in fact lacked the "scopeoptions" type "003router". I set this additional
scope and now the clients receive the value of "defaultgateway" and the PC with win7 works very well without showing any warning on the network. Probably the PC with win7 are more sensitive to network parameters are not perfectly correct and warn the exclamtion
mark and/or the red cross. In conclusion did not depend on ISA or ISA Firewall client or the windows 7 firewall but the lack of default gateway (scope router) in the DHCP network parameters.
Thank you all for your support.
Hello I am facing the same problem with Win7 Ult edition with yellow exclamation. I don't know what to do I am using ISA server 2006 and Win Server 2008 std 32 bit.
Clients accessing ISA gateway Internet through DHCP server Win 2008 the server working perfectly with out yellow exclamation mark, but client machines have this problem. Please help me what should I do in this case how to I resolved this
issue?
I really appreciate in advance for your cooperation.
Thanks,
Shajee
April 3rd, 2012 6:18pm
You have to verify the IPCONFIG /ALL result (all parameters are presents? There is the Ip of gateway?)
Set manually your IP client parameters. If it work with Ip parameters set manually then your dhcp do not send all parameters. Sorry for my bad english...
I do not know the isa 2006 but i think you have to install "isa firewall client" on pc win7 ...
Free Windows Admin Tool Kit Click here and download it now
April 4th, 2012 4:48pm