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.
Thanks for your input Peter
At 08:03 PM 12-01-2004, you wrote:
Message: 4 Date: Mon, 12 Jan 2004 11:54:58 -0800 To: [EMAIL PROTECTED] From: Ray Olszewski <[EMAIL PROTECTED]> Subject: Re: [Kaboodle-user] Re: Doesn't find PCs on 2 PC network
At 06:36 PM 1/12/2004 +0000, Scott C. Best wrote: >Peter: > > Yes, it looks like your Ethernet network isn't working as >well as it could be. I'd suggest removing the crossover cable, and >connect the PC's thru a low-end router like the LinkSys BEFSR41. >You can find one of those on EBay for less than $25. With one >of those "in between" your PC's, you don't even have to specify >an IP address. Just choose "Get IP Address Automatically" in the >TCP/IP setup. That should work much more reliably.
Alternatively, you could examine and fix the problem with the crossover setup. Possible problems are:
1. The cable either is not a crossover cable or it is bad. Try a different one.
2. How are you assigning IP addresses? Are you providing the rest of the needed information -- netmask, gateway, and so forth -- correctly? From a DOS box, do these commands --
ipconfig route show
report reasonable values for the various network settings? (These are the Win2K commands; I assume WinXP uses the same ones.)
3. I'm assuming that the NICs themselves are OK. For example, they work properly when the machines are connected to a real LAN. If you don't know this, you need to consider it as part of your troubleshooting procedure.
In any case, your problem is with basic connectivity, not with Kaboodle as such.
--
Checked by AVG Anti-Virus (http://www.grisoft.com). Version: 7.0.209 / Virus Database: 261.6.1 - Release Date: 08-01-2004
------------------------------------------------------- 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.
