Ping, Amiga<>PC LAN, dual Ethernet cards, filesharing probs & fixes

[Zac67]

What's the setup, really? You say, you pinged your modem - a DSL modem usually has no IP; sounds more like a router.
Does the modem/router have only one LAN port or more than one? How do you connect Amy, PC and 'Modem'? Is there some Hub/Switch in between?

A crossover cable is only good for connecting exactly two NICs, if you've got more devices you need a hub/switch. The port LEDs must light up when something's hooked up.

Forget about routing for a minute, if the hosts can't ping each other everything else is in vain.

Something like:
Router: 192.168.0.1, mask 255.255.255.0
Amy: 192.168.0.2, mask 255.255.255.0
PC: 192.168.0.3, mask 255.255.255.0
should work.

If you can't ping the PC, ping Amy from Windoze. Look at the ARP table to see if the IP could be resolved to the physical MAC address ('arp -c').

PS: sorry, read your description more carefully now: you're trying to share the Internet connection from the one NIC connected to DSL through the second NIC of your PC?
You'd need to activate ICS then, but it's not very good (=reliable) - get a simple DSL router (~$30). Or get some decent NAT routing software for Windows, I've used Sygate a couple of years ago. There's no way to do what you want without NAT, since you've only got one public IP.

[Zac67]

Hmm,

could be a problem in the NWAY negotiation - manually configuring both sides to exactly the same parameters (e.g. 10 Mbps full duplex) should take care of that. Have you swapped the cable? Little chance, but they do break at times.

Are the connect LEDs lit on both sides? Is there any activity on the opposite side when you try to ping?

[Zac67]

ChaosLord wrote:
Amiga - 192.168.1.101
PC =    192.168.1.102

Those numbers have worked since around 2000

Yes, and that's probably why it does not work now. I assume you're using a mask of 255.255.255.0, and all IPs are in the same segment 192.168.1.x, so there's no way for the PC to know which NIC to use, routing wise.
Two NICs in the PC mean two segments which must be differentiated by their network address. Use
192.168.1.101 Amiga
192.168.1.102 PC (Amiga connection)
192.168.2.102 PC (DSL side)
with a mask of 255.255.255.0 (/24) or don't bind an IP to the DSL NIC at all.
Or enlarge the network mask to 255.255.255.240 and use
192.168.1.17 / 192.168.1.18 Amiga - PC
192.168.1.1 / 192.168.1.2 DSL - PC
Binary ANDing the host IPs with the network mask gives you the network address and these MUST be different for the two networks your running, otherwise your routing will be screwed up. Be aware that the host part of the IP (the rest) must not be all 0s or all 1s. Eg. a host IP of 192.168.1.16 with a 255.255.255.240 mask (/28) is not valid since 16 and 240 equals 16 and the rest is 0.

PS: Noone forces you to be a Verizon customer...  ;-)

[Zac67]

Nice to hear that it's working again. :-)

I usually ignore the crapy workgroup stuff and just UNC access the machine \\computer\share and that's it. Even with two domain controllers, network neighborhood is not working 100% reliably - windows networking sucks!  :lol:

Actually you don't need much of a firewall on the Amiga side, since there's little probability that Amy attacks your XP box. :-P Just watch out for the DSL side; connecting 2k/XP w/o firewall is right next to suicide...