I've had a "code 65" error many times before; So far it's
always been due to my firewall blocking incoming &/or
outgoing ICMP Ping &/or Echo requests.
You'll most likely find the problem is related to the
actions of a firewall (OR possibly proxy server as well,
but that's a pure guess as I've no hand's on experience.
Perhaps someone else could comment further on that point?
The logic being that I think the code relates to packet
interception/blocking on an otherwise healthy network
connection, which we can assume is true if the drivers and
hardware have be replaced!
[... but you never know with all the sloppy development
we've learnt to expect as "normal", it might be one of
those "catch all error codes" which is given for hundreds
of different causes. Thus it would translate to the
equivalent of "THERE'S BEEN AN ERROR SOMEWHERE, I THINK,
BUT NOT ENTIRELY SURE WHERE OR WHY AND CAN'T BE BOTHERED
TO EVEN TRY AND HELP YOU OUT, 'CAUSE I'VE GOT DEADLINES TO
MEET! (ALSO I MIGHT FIND SOME GAPING BUG IN MY CODE WHICH
I'D RATHER NOT BE MADE AWARE OF FOR THE SAME REASONING.
MAYBE I'LL JOT DOWN A NOTE TO REMEMBER TO DO BETTER IN THE
NEXT VERSION?", but that lame old excuse is wearing a
little thin these days...] ;-/ LOL
(in case the sarcasm wasn't 100% obvious to you, I
quote: "The truest words are often said in jest"!)
Happy hunting! Hopefully that'll get you going again.
E ;-)
