Symantec Website Unaccessible

[James Keddington]

I cannot open up wwww.symantec.com or do a live update?
When I attempt a live update - it says I am not connected
to the internet?

 

[kim]

I repaired a computer with this issue, it was Sasser that
gave the site na invalid page name something like
wwww.@%symantec.com.

Try going to the iternet through IE and see if you can
get to symantec that way, if you can not then I suggest
you scan for sasser.

Kim

 

[jameskeddington]

Thanks Kim- I still cannot access symatec via IE, I
scanned for Sasser with two methods - still didnt work?

any other ideas??

 

[Robert Aldwinckle]

I cannot open up wwww.symantec.com or do a live update?
When I attempt a live update - it says I am not connected
to the internet?

James,

Nobody can give you useful suggestions if you do not disclose your OS.

In case you are running NTx open a command window and enter
these commands:

nslookup

Verify that that shows it can see your DNS server.
The command leaves you in nslookup's interactive mode.
Enter your problem site name:

wwww.symantec.com

Really? or should it be:

www.symantec.com

Do both so you can see the difference.

Now exit nslookup. Enter:

exit

Now use telnet to check that that there is a port open at that address.

telnet www.symantec.com 80

If the screen clears it means that there is a port open at that address.
If you like you can also try typing:

GET /

(That's GET <space><slash><Enter>.)

Eventually the connection will be dropped
otherwise press Ctrl-[ and type c and then q to close the connection
and quit the telnet application.

If the screen doesn't clear that means that there is no port open
at that address but it might also mean that the address being chosen
for the telnet connection isn't the right one. So redo the command
using an IP address that the nslookup command gave you instead
of the symbolic name. If that works you would know that your DNS
is working fine, since you were successful using the address that
nslookup returned. So then suspicion would be transferred to either
your HOSTS file or your OS dnscache.

You can test the address being saved by either mechanism by using ping:

ping -n 1 www.symantec.com

Is the address being used one of the ones that nslookup returned?
If not that would explain your problem. Then you should either fix HOSTS
or delete it and then flush the dnscache.

ipconfig /flushdns

Now try the telnet test again.


Good luck

Robert Aldwinckle
---

 

[Kim]

Try scannaing for ad/spyware use ad-aware 6 it is a free
download at http://www.lavasoft.de/

be careful when deleting things it finds as it can delete
important files that use IE to open and run, what happens
is that ad/spyware will overwrite valid files with ad
ware, then when the program finds it and you delete it -
it can damage IE.

I suggest that you quarentine the files so you can
replace them if this hapens. Good luck,

Kim

 

[James Keddington]

Sorry - I am operating in XP

-----Original Message-----

I cannot open up wwww.symantec.com or do a live update?
When I attempt a live update - it says I am not connected
to the internet?

James,

Nobody can give you useful suggestions if you do not disclose your OS.

In case you are running NTx open a command window and enter
these commands:

nslookup

Verify that that shows it can see your DNS server.
The command leaves you in nslookup's interactive mode.
Enter your problem site name:

wwww.symantec.com

Really? or should it be:

www.symantec.com

Do both so you can see the difference.

Now exit nslookup. Enter:

exit

Now use telnet to check that that there is a port open at that address.

telnet www.symantec.com 80

If the screen clears it means that there is a port open at that address.
If you like you can also try typing:

GET /

(That's GET <space><slash><Enter>.)

Eventually the connection will be dropped
otherwise press Ctrl-[ and type c and then q to close the connection
and quit the telnet application.

If the screen doesn't clear that means that there is no port open
at that address but it might also mean that the address being chosen
for the telnet connection isn't the right one. So redo the command
using an IP address that the nslookup command gave you instead
of the symbolic name. If that works you would know that your DNS
is working fine, since you were successful using the address that
nslookup returned. So then suspicion would be transferred to either
your HOSTS file or your OS dnscache.

You can test the address being saved by either mechanism by using ping:

ping -n 1 www.symantec.com

Is the address being used one of the ones that nslookup returned?
If not that would explain your problem. Then you should either fix HOSTS
or delete it and then flush the dnscache.

ipconfig /flushdns

Now try the telnet test again.


Good luck

Robert Aldwinckle
---



.

 

[H Leboeuf]

It may be a HOSTS file problem.
Look for a file named HOSTS (no extension, could be hidden) rename it
OLDHOSTS.

Or, you can open the file with Notepad

Unless you have install or created this file, there should be only one
uncommented line in it and that is
"127.0.0.1 localhost" (no quotes)

If there's anything else, either delete it or put a semi-colon ( ; ) in
front of the lines you wish to eliminate.
There are viruses, spyware and Web accelerator programs that will alter your
HOSTS file to prevent you from accessing certain sites.

You can use a simple batch file to rename the HOSTS file "on-the-fly".
Download: RenHosts.bat [right-click and select: Save Target As]
http://www.mvps.org/winhelp2002/hosts.htm

Tool to manage the HOSTS file.
Available at http://mvps.org/PracticallyNerded/Software.htm

--

Henri Leboeuf
Web page: http://www.colba.net/~hlebo49/index.htm
===

Sorry - I am operating in XP

-----Original Message-----

I cannot open up wwww.symantec.com or do a live update?
When I attempt a live update - it says I am not connected
to the internet?

James,

Nobody can give you useful suggestions if you do not disclose your OS.

In case you are running NTx open a command window and enter
these commands:

nslookup

Verify that that shows it can see your DNS server.
The command leaves you in nslookup's interactive mode.
Enter your problem site name:

wwww.symantec.com

Really? or should it be:

www.symantec.com

Do both so you can see the difference.

Now exit nslookup. Enter:

exit

Now use telnet to check that that there is a port open at that address.

telnet www.symantec.com 80

If the screen clears it means that there is a port open at that address.
If you like you can also try typing:

GET /

(That's GET <space><slash><Enter>.)

Eventually the connection will be dropped
otherwise press Ctrl-[ and type c and then q to close the connection
and quit the telnet application.

If the screen doesn't clear that means that there is no port open
at that address but it might also mean that the address being chosen
for the telnet connection isn't the right one. So redo the command
using an IP address that the nslookup command gave you instead
of the symbolic name. If that works you would know that your DNS
is working fine, since you were successful using the address that
nslookup returned. So then suspicion would be transferred to either
your HOSTS file or your OS dnscache.

You can test the address being saved by either mechanism by using ping:

ping -n 1 www.symantec.com

Is the address being used one of the ones that nslookup returned?
If not that would explain your problem. Then you should either fix HOSTS
or delete it and then flush the dnscache.

ipconfig /flushdns

Now try the telnet test again.


Good luck

Robert Aldwinckle
---



.

 

[Robert Aldwinckle]

If there's anything else, either delete it or put a

#

in front of the lines you wish to eliminate.

Henri,

Unless there is something very different about your OS
you should fix this information you copy from.

HOSTS.SAM should explain how to do comments.




Robert
---

It may be a HOSTS file problem.
Look for a file named HOSTS (no extension, could be hidden) rename it
OLDHOSTS.

Or, you can open the file with Notepad

Unless you have install or created this file, there should be only one
uncommented line in it and that is
"127.0.0.1 localhost" (no quotes)

If there's anything else, either delete it or put a semi-colon ( ; ) in
front of the lines you wish to eliminate.
There are viruses, spyware and Web accelerator programs that will alter your
HOSTS file to prevent you from accessing certain sites.

You can use a simple batch file to rename the HOSTS file "on-the-fly".
Download: RenHosts.bat [right-click and select: Save Target As]
http://www.mvps.org/winhelp2002/hosts.htm

Tool to manage the HOSTS file.
Available at http://mvps.org/PracticallyNerded/Software.htm

--

Henri Leboeuf
Web page: http://www.colba.net/~hlebo49/index.htm
===

Sorry - I am operating in XP

-----Original Message-----
I cannot open up wwww.symantec.com or do a live update?
When I attempt a live update - it says I am not connected
to the internet?

James,

Nobody can give you useful suggestions if you do not disclose your OS.

In case you are running NTx open a command window and enter
these commands:

nslookup

Verify that that shows it can see your DNS server.
The command leaves you in nslookup's interactive mode.
Enter your problem site name:

wwww.symantec.com

Really? or should it be:

www.symantec.com

Do both so you can see the difference.

Now exit nslookup. Enter:

exit

Now use telnet to check that that there is a port open at that address.

telnet www.symantec.com 80

If the screen clears it means that there is a port open at that address.
If you like you can also try typing:

GET /

(That's GET <space><slash><Enter>.)

Eventually the connection will be dropped
otherwise press Ctrl-[ and type c and then q to close the connection
and quit the telnet application.

If the screen doesn't clear that means that there is no port open
at that address but it might also mean that the address being chosen
for the telnet connection isn't the right one. So redo the command
using an IP address that the nslookup command gave you instead
of the symbolic name. If that works you would know that your DNS
is working fine, since you were successful using the address that
nslookup returned. So then suspicion would be transferred to either
your HOSTS file or your OS dnscache.

You can test the address being saved by either mechanism by using ping:

ping -n 1 www.symantec.com

Is the address being used one of the ones that nslookup returned?
If not that would explain your problem. Then you should either fix HOSTS
or delete it and then flush the dnscache.

ipconfig /flushdns

Now try the telnet test again.


Good luck

Robert Aldwinckle
---



.

 

[Robert Aldwinckle]

In case you are running NTx open a command window and

enter ....

Sorry - I am operating in XP

XP == NT5

Did you try any of those diagnostics?


---

Sorry - I am operating in XP

-----Original Message-----

I cannot open up wwww.symantec.com or do a live update?
When I attempt a live update - it says I am not connected
to the internet?

James,

Nobody can give you useful suggestions if you do not disclose your OS.

In case you are running NTx open a command window and enter
these commands:

nslookup

Verify that that shows it can see your DNS server.
The command leaves you in nslookup's interactive mode.
Enter your problem site name:

wwww.symantec.com

Really? or should it be:

www.symantec.com

Do both so you can see the difference.

Now exit nslookup. Enter:

exit

Now use telnet to check that that there is a port open at that address.

telnet www.symantec.com 80

If the screen clears it means that there is a port open at that address.
If you like you can also try typing:

GET /

(That's GET <space><slash><Enter>.)

Eventually the connection will be dropped
otherwise press Ctrl-[ and type c and then q to close the connection
and quit the telnet application.

If the screen doesn't clear that means that there is no port open
at that address but it might also mean that the address being chosen
for the telnet connection isn't the right one. So redo the command
using an IP address that the nslookup command gave you instead
of the symbolic name. If that works you would know that your DNS
is working fine, since you were successful using the address that
nslookup returned. So then suspicion would be transferred to either
your HOSTS file or your OS dnscache.

You can test the address being saved by either mechanism by using ping:

ping -n 1 www.symantec.com

Is the address being used one of the ones that nslookup returned?
If not that would explain your problem. Then you should either fix HOSTS
or delete it and then flush the dnscache.

ipconfig /flushdns

Now try the telnet test again.


Good luck

Robert Aldwinckle
---



.