J
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?
When I attempt a live update - it says I am not connected
to the internet?
James Keddington said: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?
-----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
---
.
James Keddington said: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
---
.
in front of the lines you wish to eliminate.
H Leboeuf said: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
===
James Keddington said: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
---
.
enter ....
Sorry - I am operating in XP
James Keddington said: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
---
.