Re: Selling my soul to the devil is the next step...

On Thu, 17 Aug 2006 20:23:09 +0100, Dr Teeth <no.email.here.please@xxxxxxxxxx>
wrote:

I was just thinking how wonderful life was, when Chuck
<none@xxxxxxxxxxx> opened his gob and said:

But you could provide us CDiag log for Laptop, instead of for TARDIS_2 twice.

I wondered when I'd get caught out with that one! here's CDiag log for
Laptop:-

<SNIP>

Hope it helps.

Thanks.

That it does. The problem - and it's symmetrical - is between LAPTOP and
TARDIS_2. Neither can access the other, in any of 4 tests each. Look at CDiag
for LAPTOP, Target TARDIS_2. Look at CDiag for TARDIS_2, Target LAPTOP.
# Ping by name. Name resolution problem.
# Net View by name. No display (you'll probably see errors in the command
window).
# Ping by IP address. Request times out.
# Net View by IP address. No display (you'll probably see errors in the command
window).

With pings being blocked, both ways, this points to either a physical (cabling /
router) or logical (firewall) problem. Let's test logically, and do this very
methodically please. Read thru instructions first.
1) Swap router ports for 2 cables - say NUMBER_1 and LAPTOP. See if the problem
moves.
2) Swap router ports for NUMBER_1 and LAPTOP back, then swap NUMBER_1 and
TARDIS_2. See if the problem moves.
3) Swap router ports for NUMBER_1 and TARDIS_2 back, then swap Ethernet cables
between NUMBER_1 and LAPTOP. See if the problem moves.
4) Swap Ethernet cables for NUMBER_1 and LAPTOP back, then swap NUMBER_1 and
TARDIS_2. See if the problem moves.

Tests 1 - 4 will identify either a router port or Ethernet cable as the problem.
If no changes are observed from any of the 4 tests, then the problem will be a
firewall. Or possibly a LSP / Winsock problem, but with the symmetry, I don't
believe that.

If it's a firewall, we'll think of some more tests. Just do this very
deliberately.

And your testing, as you swap cables and / or router ports, can be very simple.
From Tardis_2, open one command window, and type "ping -t 192.168.1.3" (Ping
Laptop by IP address). Then open a second command window, and type "ping -t
192.168.1.4" (Ping Number_1 by IP address). Do the same for the other two
computers, but differing targets. The "ping -t" will ping continuously, and you
won't have to restart anything. See instantly when you make a change that makes
the problem move.

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
.

Relevant Pages

  • Re: Selling my soul to the devil is the next step...
    ... Look at CDiag ... for LAPTOP, Target TARDIS_2. ... Swap router ports for NUMBER_1 and LAPTOP back, ... Swap router ports for NUMBER_1 and TARDIS_2 back, ...
    (microsoft.public.windowsxp.network_web)
  • Re: mlock(1)
    ... willing to assume only dumb criminals steal their laptop. ... boot and on restore, most folks are happy to type their password in to ... > be stolen and compromised at this level, you presumably have set your bios passwords ... > power switch because they couldn't trigger the suspend, the swap image is scrambled. ...
    (Linux-Kernel)
  • Re: encrypted swap question
    ... Indeed this is a laptop - I guess I can re-run mkinitrd manually and maybe this will work ahead of waiting for another kernel. ... I think either case gets you out of typing a 2nd LIKS password. ... Using /dev/urandom seems to avoid having a password where anyone could ever recover it, and I think using LUKS on swap will kill suspend in either case. ...
    (Fedora)
  • Re: Memory usage (avoid swapping, top accuracy...)
    ... precisely because this is a laptop. ... Disabling spamd probably helped (and the reboot too). ... Don't pay attention to how much swap is used. ... a large amount of active swapping is a *good* thing and you're fretting over ...
    (Debian-User)
  • Re: Limited Network
    ... however I have also tried just a normal hub with the ... > with lock up happening after about 20-30 seconds either way. ... Swap out the nic on the older machine for a new, ... Change the router ports. ...
    (microsoft.public.windowsxp.network_web)