Re: BBC programme re: re-cyclling computers

"Rabbit" <Rabbit_is@xxxxxxxxxxx> wrote in message
news:4klrc4Fcoj76U1@xxxxxxxxxxxxxxxxx
"pmj" <post@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:dysEg.4074$r61.1517@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
"Rabbit" <Rabbit_is@xxxxxxxxxxx> wrote in message
news:4kebvuFbmkbaU1@xxxxxxxxxxxxxxxxx
"pmj" <post@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:fX9Eg.3658$r61.2751@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Rabbit Posted...
<snip>
... but something stuck in my mind about the only completely
safe way to wipe a hard drive costs big bucks.

Have a look at...
http://heidi.ie/eraser/features.php
http://heidi.ie/eraser/faq.php#erase%20hd

That one is the most popular of the readily available ones.
But there are others.

You've brokted them :-) They both time out here :-(

Both those Pages (which are on the same Site) work OK here.
Try them again?

I have done,several times,over several days now, with and
without Proxomitron, but for thee of little faith

It's not a question of anybody being "of little faith"!
:-)

But we (you) need to see what's actually happening, so as to be
able to suss out what's what, where the prob actually is & thus make
it Fixted...

... the Proxomitron log says.........

New Message Log Window....

+++GET 167+++
GET /eraser/features.php HTTP/1.0
Accept: */*
Accept-Language: en-gb
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1;
SV1; .NET CLR 1.1.4322)
Host: heidi.ie
Connection: keep-alive
Retry 167...
Retry 167...
<snip Retries>
Retry 167...
Retry 167...
** 167 Socket Error 10061 for connect() **
+++CLOSE 167+++

New Message Log Window....

+++GET 174+++
GET /eraser/faq.php HTTP/1.0
<snip>
** 174 Socket Error 10061 for connect() **
+++CLOSE 174+++
<snip>
See above, got the list page but still can't get heidi and I've
got the proof in black and white :-

OK...

That means you're getting a "Connection Refused" TCP Socket Error
(that's what "Socket Error 10061" is)...

You can find out what all the various Socket Errors mean from
the Sockets.com WebSite...

http://sockets.com/err_lst1.htm

<quote>
WSAECONNREFUSED (10061) Connection refused.

Berkeley description: No connection could be made because the
target machine actively refused it. This usually results from
trying to connect to a service that is inactive on the foreign host.

TCP/IP scenario: In TCP terms (datastream sockets), it means
an attempt to connect (by sending a TCP SYN packet) caused the
destination host to respond to the host by returning a reset
(a TCP RST packet). If an application sends a UDP packet to
a host/port that does not have a datagram socket "listening,"
the network system may respond by sending back an ICMP Port
Unreachable packet

User suggestions: Either you went to the wrong host, or the
server application you're trying to contact isn't executing.
Check the destination address you are using. If you used a
hostname, did it resolve to the correct address? If the hostname
resolution uses a local hosttable, it's possible you resolved to
an old obsolete address. It's also possible that the local services
file has an incorrect port number (although it's unlikely).
</quote>

Try these things, so as to enable us to start sussing out what's what...

Open up a Command Prompt Window & do a Ping of the Host heidi.ie

ping heidi.ie [Enter]

& Post back with what you get (that will tell us if your PC is
Resolving the HostName OK & what IP Address it's Resolving it to
& will also tell us if the Host that it's Pinging is Responding
to ICMP (Ping) Packets.

Then, depending on what you get from doing a Ping, we can then try
other things.

Since it *is* obviously Resolving to an IP Address of some kind -
cos it's *trying* to Connect - otherwise you would have got a
"Host Not Found" type DNS Error), you need to check/Verify that
the IP Address that it's trying to Connect to is actually the
*Correct* IP Address...

So - Also, do an NSLookup of that HostName (at a Command Prompt,
Enter this Command)...

nslookup heidi.ie [Enter]

(or just Open up NSLookup, (from the Command Prompt) by Entering...

nslookup [Enter]

& then (at the NSLookup Prompt) Entering the HostName...

heidi.ie [Enter]

What IP Address does *that* show?
& is it the same as the IP Address that the Ping Command showed?

I suspect (but when you Post back with the Results, that will
Confirm/Deny what I'm suspecting) that you will prolly find that the
Ping Command is Resolving the HostName (by using the HOSTS File) to:
127.0.0.1 (which is your own Machine, which is why it's Rejecting
the Connection Attempt, but when you do an NSLookup for the HostName,
(which uses your Router & the ISP's DNS Servers for the DNS Lookup,
rather than the HOSTS File), it will give the IP Address as:
69.93.191.45 [2d.bf.5d45.static.theplanet.com]

So, try these URLs (which use the IP Address, rather than a HostName)...

http://69.93.191.45/eraser/features.php
&
http://69.93.191.45/eraser/faq.php#erase%20hd

If they work OK, then the prob was/is something on your Machine
that is making the HostName Resolve to the wrong IP Address (prolly
you have an Entry in the HOSTS File for that particular HOST Name -
just Comment the Line out, (with a "Hash" Symbol - "#" at the
beginning of the Line) & see if the original URLs (with the Host
Name, rather than the IP Address) then work OK.

HTH

--
pmj


.

Relevant Pages

  • Re: What is the difference between "No address associated with name" and "Unknown host"
    ... ping: cannot resolve accounts.eirtrade.ie: No address associated with name ... ping: cannot resolve accounts.eirtrade.i: Unknown host ... Because the domain name server cannot be found, it is not possible to tell the IP address of the given hostname. ...
    (freebsd-questions)
  • Ping IPv6 host by hostname
    ... In the host table of the Solaris system I have placed ... I can ping the Windows system by IP address ... but I can't ping it by hostname. ...
    (SunManagers)
  • SUMMARY: Cannot ping or telnet by hostname
    ... Subject: UPDATE: Cannot ping or telnet by hostname ... 755 permissions on /etc/hosts ... The specific hosts we are trying to ping are not defined in our DNS but ARE ... hostname and we get the following error ping: ...
    (Tru64-UNIX-Managers)
  • Re: CDE/Network problem
    ... Probably a name resolving issue. ... Make sure both IP address and hostname resolve correctly ("host ... setup details. ...
    (comp.unix.aix)
  • UPDATE: Cannot ping or telnet by hostname
    ... 755 permissions on /etc/hosts ... The specific hosts we are trying to ping are not defined in our DNS but ARE ... hostname and we get the following error ping: ...
    (Tru64-UNIX-Managers)