For now, just a guess, based on your saying --
I only changed from "obtain IP address automatically" to the fixed 192.168.0.2 and .3 addresses in an attempt to debug this problem.
While you added the IP address 192.168.0.2 (and .3), did you specify a subnet mask of /24 (or 255.255.255.0 in the Windows setup box)?
Did you also try to run Kaboodle while leaving the NICs at "obtain IP address automatically"? If so, then your problem with *that* setup is that in the absence of a DHCP lease, the hosts will default to assigning themselves random 169.254.c.d IP addresses, but on a /16 network, not a /24 network ... hence, Kaboodle will very probably not find the other end of a crossover pair set up using these defaults, since there is only about 0.4% chance that the two random addresses will be on the same /24 network (thoughin this instance they should ping each other, since their routing tables know they are on a /16 network).
At 11:20 PM 1/12/2004 -0800, Peter Judd wrote:
Ray Olszewski et al,[old stuff deleted]
Yes it's a working crossover cable and the NICs work - I've been getting 100mbit throughput with it for two years between a desktop & laptop.
Here are the results of your proposed tests:
--------------------------------------------- IPCONFIG: Ethernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected PPP adapter Pender 5590:
Connection-specific DNS Suffix . : IP Address. . . . . . . . . . . . : 204.244.17.90 Subnet Mask . . . . . . . . . . . : 255.255.255.255 Default Gateway . . . . . . . . . : 0.0.0.0
----------------------------------------------
ROUTE PRINT
0x1 ........................... MS TCP Loopback interface
0x2 ...00 c0 a8 8c 7d 01 ...... GVC-REALTEK Ethernet 10/100 PCI Adapter - Packet Scheduler Miniport
0x20004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 204.244.17.90 204.244.17.90 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
204.244.17.5 255.255.255.255 204.244.17.90 204.244.17.90 1
204.244.17.90 255.255.255.255 127.0.0.1 127.0.0.1 50
204.244.17.255 255.255.255.255 204.244.17.90 204.244.17.90 50
224.0.0.0 240.0.0.0 204.244.17.90 204.244.17.90 1
255.255.255.255 255.255.255.255 204.244.17.90 2 1
Default Gateway: 204.244.17.90
===========================================================================
Persistent Routes:
None
I only changed from "obtain IP address automatically" to the fixed 192.168.0.2 and .3 addresses in an attempt to debug this problem.
Don't understand about Gateway yet - I assumed it has to do with a router function but the above 'Default Gateway: 204.244.17.90'
reported is my dial up IP address.
------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Kaboodle-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kaboodle-user To UNSUBSCRIBE, click on the above link.
