Ping Probleme

[AEN007]

29Nov2009

Hallo.
Ich könnte auf Deutsch schreiben, aber
das wäre zu langsam ...

I have three XP laptops & lots of "little problems."

1) The laptops cannot ping one another.
That means I cannot use intranet time sync utilities.

2) The Netlogon service will not start.
I tried the Winsock reset procedures -
at first on the 2 XP-Pro laptops (T & I).
Immediately afterwards I had partial ping success
but Netlogon would still not start.

3) I have not yet been able to ping my usb netzkabel
IP addresses. I network these 3 laptops various ways
depending on what internet access connections I have.
I always use 1 usb netzkabel between laptops I & G.
G has XP-Home. I always use static IP addresses
whether I am using usbnetz, ethernet patchkabel
or Ad Hoc wlan. Laptop T is 11 years old and the most
difficult to network. I now use a pcmcia-wlan card
to connect T with I & G. Because I also use a usbnetz
kabel between I & G (the two more modern XP laptops),
I have a redundant LAN connection between I & G.

4) Is there any way to connect T with I & G via wlan
but not also connect I & G via the ad hoc connections?
I recently discovered how to set the ad hoc wlan
connections @ 54Mbps instead of 11Mbps.
The usbnetz kabel connect (now) at a stated 480Mbps.
I recently upgraded the usbnetz drivers. Prolific in Taiwan
seems to be the only supplier of usbnetz cables.
The usbnetz connection previously was a stated 12Mbps.
Regardless of the stated speed, the usbnetz connection
copies files at about 4Mbps, whereas ethernet at a stated
speed of 100Mbps copies at about 1.5Mbps or less.
The 54Mbps wlan copy at about 1Mbps or less.
The usbnetz kabel at 12Mbps was always about 3 or 4
times faster than the ethernet at a stated 100Mbps. Why?

5) The partial ping success lasted about 30 minutes.
After the XPP winsock resets, I could ping all the wlan
connections but still not the usbnetz connections.
I had to make some nic re-adjustments which maybe killed
the partial ping success. I don't now why the reset on the
2 XPP laptops (I & T) allowed pinging the untouched
XPH laptop (G). It might be that installing the usbnetz
connections somehow impedes the pinging. If so, I don't
know why. The "networking" works fine. Each connection
reads & writes both directions without problems.
The XP "Search for Computers" finds all computers, but
I still cannot ping any connections.

6) Activating a parallel port direct cable connection
between I & T for some unknown reason enables pinging
between I & T - all connections (usbnetz, wlan, DCC ...)
I have no idea why that happens.

7) For some unknown reason these ping problems do not
exist when I use an ethernet crossover cable - at least
that was always the case. I would have to test again.

8) The ping problems exist whether I have ZoneAlarmFree
firewall turned on or off on laptops G & I.

9) I cannot reinstall IPv6 on laptop G.

Any helpful replies/insights appreciated.
Danke.
Grüße,
AEN
Æ

[BuckFix]

I could write in English, but that would also be too slow.

Poste die Ausgabe von "ipconfig /all" aller beteiligten Rechner.
Poste die Angabe aus der Ereignisanzeige, die sich auf den fehlgeschlagenen Start des Netlogon-Service bezieht.

Deinstalliere ZoneAlarm, bevor du weitere Probleme im Netzwerk lösen willst.

[AEN007]

30Nov2009
Hallo.
Danke für eine Antwort.

1) The netlogon service issue is no longer an issue;
however, I now have (noticed) a more serious
"service won't start" problem. I use the NirSoft
services manager (or command line) instead of
the XP services manager. I realized/discovered
after your posting that neither the NSSM
nor the CL give the error messages that the XPSM does.
Reading the error message allowed me to solve
the netlogon "won't start" problem.

2) I cannot start remoteaccess on I; however,
I can start remoteaccess on T. G does not list
remoteaccess as a service option. I & T have
parallel & serial ports. G does not.

At a minimum I would like to "ping" between I & T.
T is usually never connected to the internet,
so I would like to use intranet time sync utilities
between I & T.

Enabling the direct cable / parallel port connection
between I & T (I as guest & T as host) allows
pinging between the I & T DCPPC IP addresses
(but not the wLAN IP addresses ...).
Most of my LAN traffic goes from I to G & I to T,
so I set up the DCPPC with T as host.
Previously I could not set up a guest DCPPC on T
but could start remoteaccess on I. Now I cannot
start remoteaccess on I but yesterday was able
to setup a guest DCPPC on T. I could use intranet
time sync between I & T when a DCPPC would be active.
I cannot, however, have the DCPPC where T is host
because all traffic from I would go over not only
the wLAN connection but also the DCPPC,
which causes T CPU usage to go to 100%.
If I could (once again) start remoteaccess on I,
then I could activate T as a guest. Then there would be
an active DCPPC but traffic from I to T would only go
over the wLAN connection. I found/tried 2 proposed
solutions to the remoteaccess "won't start" problem,
but neither worked for me.

3) I'm not ready (yet) to uninstall ZoneAlarm.
I could ping previously between G & T and also I & T
when ZoneAlarm was active on G & T.
Even if I shut down ZA
these current ping problems persist.

4) I have attached 6 txt files with ping, IPconfig &
remoteaccess results for I & T. There are ping results
with & without the DCPPC enabled. XP assigns
the DCPPCs a subnet mask of 255.255.255.255,
which I thought was "illegal" ... When I ping G,
the G internet IP address answers but not the
wLAN or usb netzkabel connections.

5) The usbnetz stats I gave are for when the usb
netzkabel is in "Network" mode - which I use
(99% of the time) because it is way more convenient
than the "Bridge" mode - which is, however,
about twice as fast as the "Network" mode -
which is 3 or 4 times faster than the ethernet crossover.

6) I would really like to solve these issues.
It's just one problem to solve after another
with XP networking ...

Any helpful replies/insights appreciated.
Danke.
Grüße,
AEN
Æ

[BuckFix]

Also mal davon abgesehen, dass es eine völlig chaotische Netzwerkkonstruktion ist, musst du die verschiedenen Netzwerke schon untereinander routen, damit sie miteinander kommunizieren können.
Und wenn du ZoneAlarm nicht deinstallieren willst, bin ich auch nicht bereit hier weitere Unterstützung zu geben.

[AEN007]

5December2009

Greetings.
I am VERY HAPPY & RELIEVED to say that
I have finally actualy hacked my way through
this Network/Ping labyrinth and now seem to have
a fully functioning PINGABLE XP Ad Hoc LAN.

ZoneAlarm had nothing to do with the problem or solution.

Regards,
AEN
Æ

[leader]

And what type of problem was it?

The next user would be happy about a solution.

[AEN007]

Ich bin auch nicht bereit hier
weitere Unterstützung zu geben...

[BuckFix]

Gut zu wissen!

[leader]

Ach schau...wenn wir beleidigt sind können wir auch in deutsch schreiben.
Na dann tschüss

Man sollte sich auch mal die Mühe geben auf die Tipps und Hinweise einzugehen und nicht als Hilfesuchender immer direkt alles besser zu wissen.
Auch wenn ZoneAlarm hier mal nicht der Übeltäter gewesen zu sein scheint...hätte man das durch den Tipp von BuckFix schließlich auch festgestellt und danach nach anderen Lösungen gesucht.