Ping results again...
|
From: Tom on 27 Feb 2007 11:18 sorry about that... Pinging microsoft.com [207.46.232.182] with 32 bytes of data: Pinging lb1.www.ms.akadns.net [207.46.225.60] with 32 bytes of data: Pinging support.microsoft.akadns.net [207.46.248.248] with 32 bytes of data: Remember too, I can reach all these site if using Firefox but not IE. I will follow up next with the other info to your second request. Thanks. Tom "Les Connor [SBS MVP]" wrote: > Hi Tom, > > Earlier in the thread, you were asked for the result of ping > www.microsoft.com - that would be helpful. > > from the server, run these commands in a dos window, and post the output. > > ping microsoft.com > ping www.microsoft.com > ping support.microsoft.com > > the pings will time out, but we need to see if DNS resolution is working. > > -- > Les Connor [SBS MVP] > > > "Tom" <Tom(a)discussions.microsoft.com> wrote in message > news:00A5F5BF-8C37-48EE-A486-2EC4E2CBD091(a)microsoft.com... > > Any one have any other ideas here? > > > > "Tom" wrote: > > > >> Hello again: > >> > >> I have deleted all the temp files, but ran your command file anyhow, but > >> again to no avail. > >> > >> Other than the version of Symante A/V Corp edition that is on the server, > >> now else would I check for malware? > >> > >> Thanks again > >> > >> "Lanwench [MVP - Exchange]" wrote: > >> > >> > In news:A797AA86-C308-4008-AAAF-8A9A40C1E5D4(a)microsoft.com, > >> > Tom <Tom(a)discussions.microsoft.com> typed: > >> > > Oh...I know...and this has been done but to no avail. > >> > > >> > And you're positive you've reset all the defaults in the security > >> > zone/everwhere? Deleted all temporary internet items? > >> > > >> > Try running this in a command prompt (it's handy to have in a batch > >> > file)...mind line wrap! > >> > > >> > FOR /F %%A IN ('DIR/B "C:\Documents and Settings"') DO DEL/S/F/Q > >> > "C:\Documents and Settings\%%A\Local Settings\Temporary Internet > >> > Files\*.*" > >> > FOR /F %%A IN ('DIR/B "C:\Documents and Settings"') DO RD/S/Q > >> > "C:\Documents > >> > and Settings\%%A\Local Settings\Temporary Internet Files\" > >> > > >> > Are you sure there's no malware lurking on this server? Has anyone been > >> > treating it like a workstation? > >> > > >> > When you ping www.microsoft.com, what happens? > >> > > >> > > >> > > > >> > > "Lanwench [MVP - Exchange]" wrote: > >> > > > >> > >> In news:07BE828F-E765-44E7-BB13-C6E5BBBDCA54(a)microsoft.com, > >> > >> Tom <Tom(a)discussions.microsoft.com> typed: > >> > >>> Remember though the issue isn't just with the update sites, it's > >> > >>> with any microsoft domain site (i.e. - www.microsoft.com, > >> > >>> support.microsoft.com, etc.) > >> > >> > >> > >> Right, which is why I suggested using > >> > >> > >> > >> *.microsoft.com > >> > >> > >> > >> in the trusted sites. > >> > >> > >> > >>> Am I told this had been working as long > >> > >>> ago as three months. Odd thing is I can get to these via Firefox > >> > >>> (the other browser I mentioned). > >> > >>> > >> > >>> There is no error in the broswer though. It ends up with a blank > >> > >>> screen. The address bar does change to this though... > >> > >>> > >> > >>> http://sea.search.msn.com/dnserror.aspx?FORM=DNSAS&q=www.microsoft.com > >> > >>> > >> > >>> Seems like a DNS issue, but as noted earlier I doubt it as I can > >> > >>> get > >> > >>> there via Firefox. > >> > >> > >> > >> Did you try my suggestion? > >> > >> > >> > >> > >> > >>> > >> > >>> Tom > >> > >>> > >> > >>> "Lanwench [MVP - Exchange]" wrote: > >> > >>> > >> > >>>> In news:A89E88CC-A957-4BE4-93AB-A0FBE6E2A72E(a)microsoft.com, > >> > >>>> Tom <Tom(a)discussions.microsoft.com> typed: > >> > >>>>> Hello all: > >> > >>>>> > >> > >>>>> Picked up a new client running SBS2003 pre-sp1. The server > >> > >>>>> cannot > >> > >>>>> access the Microsoft Update site so I went in to check this out. > >> > >>>>> Seems that the server cannot access ANY Microsoft site. It's not > >> > >>>>> DNS because I installed a non-MS browser, and can get to MS sites > >> > >>>>> via this browser. IE6 can access all other non-MS sites though. > >> > >>>>> > >> > >>>>> Futher all the workstations can access the update site and all > >> > >>>>> other MS sites via their IE6 installation. > >> > >>>>> > >> > >>>>> Installing IE7 is not an answer since this server is pre-SP1, and > >> > >>>>> cannot be upgraded yet to SP1. > >> > >>>>> > >> > >>>>> Hope ya'll have some idea's as I am flumoxed on this one. > >> > >>>>> > >> > >>>>> Tom > >> > >>>> > >> > >>>> > >> > >>>> Add *.microsoft.com to the trusted sites, and set the security on > >> > >>>> that zone to "low". Try again. Report back with the specific > >> > >>>> errors > >> > >>>> you get, if any. > >> > >>>> > >> > >>>> I don't know that IE7 would help, and I'd never install it on my > >> > >>>> servers anyway (for as long as I can get away with that). I > >> > >>>> personally dislike it plenty on workstations, but it also causes > >> > >>>> issues on Exchange servers, and one shouldn't be surfing on a > >> > >>>> server anyway other than doing admin stuff. > >> > > >> > > >> > > >> > >
From: Les Connor [SBS MVP] on 27 Feb 2007 13:16 Looks like an IE issue then, as others have suggested. -- Les Connor [SBS MVP] "Tom" <Tom(a)discussions.microsoft.com> wrote in message news:B140B6F1-D1BE-4DA2-94AD-1EB137B8DD1C(a)microsoft.com... > sorry about that... > > Pinging microsoft.com [207.46.232.182] with 32 bytes of data: > Pinging lb1.www.ms.akadns.net [207.46.225.60] with 32 bytes of data: > Pinging support.microsoft.akadns.net [207.46.248.248] with 32 bytes of > data: > > Remember too, I can reach all these site if using Firefox but not IE. > > I will follow up next with the other info to your second request. > > Thanks. > > Tom > > "Les Connor [SBS MVP]" wrote: > >> Hi Tom, >> >> Earlier in the thread, you were asked for the result of ping >> www.microsoft.com - that would be helpful. >> >> from the server, run these commands in a dos window, and post the output. >> >> ping microsoft.com >> ping www.microsoft.com >> ping support.microsoft.com >> >> the pings will time out, but we need to see if DNS resolution is working. >> >> -- >> Les Connor [SBS MVP] >> >> >> "Tom" <Tom(a)discussions.microsoft.com> wrote in message >> news:00A5F5BF-8C37-48EE-A486-2EC4E2CBD091(a)microsoft.com... >> > Any one have any other ideas here? >> > >> > "Tom" wrote: >> > >> >> Hello again: >> >> >> >> I have deleted all the temp files, but ran your command file anyhow, >> >> but >> >> again to no avail. >> >> >> >> Other than the version of Symante A/V Corp edition that is on the >> >> server, >> >> now else would I check for malware? >> >> >> >> Thanks again >> >> >> >> "Lanwench [MVP - Exchange]" wrote: >> >> >> >> > In news:A797AA86-C308-4008-AAAF-8A9A40C1E5D4(a)microsoft.com, >> >> > Tom <Tom(a)discussions.microsoft.com> typed: >> >> > > Oh...I know...and this has been done but to no avail. >> >> > >> >> > And you're positive you've reset all the defaults in the security >> >> > zone/everwhere? Deleted all temporary internet items? >> >> > >> >> > Try running this in a command prompt (it's handy to have in a batch >> >> > file)...mind line wrap! >> >> > >> >> > FOR /F %%A IN ('DIR/B "C:\Documents and Settings"') DO DEL/S/F/Q >> >> > "C:\Documents and Settings\%%A\Local Settings\Temporary Internet >> >> > Files\*.*" >> >> > FOR /F %%A IN ('DIR/B "C:\Documents and Settings"') DO RD/S/Q >> >> > "C:\Documents >> >> > and Settings\%%A\Local Settings\Temporary Internet Files\" >> >> > >> >> > Are you sure there's no malware lurking on this server? Has anyone >> >> > been >> >> > treating it like a workstation? >> >> > >> >> > When you ping www.microsoft.com, what happens? >> >> > >> >> > >> >> > > >> >> > > "Lanwench [MVP - Exchange]" wrote: >> >> > > >> >> > >> In news:07BE828F-E765-44E7-BB13-C6E5BBBDCA54(a)microsoft.com, >> >> > >> Tom <Tom(a)discussions.microsoft.com> typed: >> >> > >>> Remember though the issue isn't just with the update sites, it's >> >> > >>> with any microsoft domain site (i.e. - www.microsoft.com, >> >> > >>> support.microsoft.com, etc.) >> >> > >> >> >> > >> Right, which is why I suggested using >> >> > >> >> >> > >> *.microsoft.com >> >> > >> >> >> > >> in the trusted sites. >> >> > >> >> >> > >>> Am I told this had been working as long >> >> > >>> ago as three months. Odd thing is I can get to these via >> >> > >>> Firefox >> >> > >>> (the other browser I mentioned). >> >> > >>> >> >> > >>> There is no error in the broswer though. It ends up with a >> >> > >>> blank >> >> > >>> screen. The address bar does change to this though... >> >> > >>> >> >> > >>> http://sea.search.msn.com/dnserror.aspx?FORM=DNSAS&q=www.microsoft.com >> >> > >>> >> >> > >>> Seems like a DNS issue, but as noted earlier I doubt it as I can >> >> > >>> get >> >> > >>> there via Firefox. >> >> > >> >> >> > >> Did you try my suggestion? >> >> > >> >> >> > >> >> >> > >>> >> >> > >>> Tom >> >> > >>> >> >> > >>> "Lanwench [MVP - Exchange]" wrote: >> >> > >>> >> >> > >>>> In news:A89E88CC-A957-4BE4-93AB-A0FBE6E2A72E(a)microsoft.com, >> >> > >>>> Tom <Tom(a)discussions.microsoft.com> typed: >> >> > >>>>> Hello all: >> >> > >>>>> >> >> > >>>>> Picked up a new client running SBS2003 pre-sp1. The server >> >> > >>>>> cannot >> >> > >>>>> access the Microsoft Update site so I went in to check this >> >> > >>>>> out. >> >> > >>>>> Seems that the server cannot access ANY Microsoft site. It's >> >> > >>>>> not >> >> > >>>>> DNS because I installed a non-MS browser, and can get to MS >> >> > >>>>> sites >> >> > >>>>> via this browser. IE6 can access all other non-MS sites >> >> > >>>>> though. >> >> > >>>>> >> >> > >>>>> Futher all the workstations can access the update site and all >> >> > >>>>> other MS sites via their IE6 installation. >> >> > >>>>> >> >> > >>>>> Installing IE7 is not an answer since this server is pre-SP1, >> >> > >>>>> and >> >> > >>>>> cannot be upgraded yet to SP1. >> >> > >>>>> >> >> > >>>>> Hope ya'll have some idea's as I am flumoxed on this one. >> >> > >>>>> >> >> > >>>>> Tom >> >> > >>>> >> >> > >>>> >> >> > >>>> Add *.microsoft.com to the trusted sites, and set the security >> >> > >>>> on >> >> > >>>> that zone to "low". Try again. Report back with the specific >> >> > >>>> errors >> >> > >>>> you get, if any. >> >> > >>>> >> >> > >>>> I don't know that IE7 would help, and I'd never install it on >> >> > >>>> my >> >> > >>>> servers anyway (for as long as I can get away with that). I >> >> > >>>> personally dislike it plenty on workstations, but it also >> >> > >>>> causes >> >> > >>>> issues on Exchange servers, and one shouldn't be surfing on a >> >> > >>>> server anyway other than doing admin stuff. >> >> > >> >> > >> >> > >> >> > >>
|
Pages: 1 Prev: Limit User Access within a time frame Next: IIS related services start hourly |