A1200 to WinXP PC Networking

[KennyR]

(Posted for a friend).

Could someone please end my amiga -> winxp network nightmare. I`v set it all up but I cant get either machine to talk to each other. Im using winxp (sp1) with 2 belkin ethernet pci cards, one connected to ntl cable via an ntl set top box, the other connected by a crossover cat5 ethernet cable to a netgear FA 410tx pcmcia card on the A1200 using cnet device. (note. a router isnt an option)

my Miami setup (3.2b): Interfaces > Sana 2 ethernet, driver=cnetdevice unit=0
                                    IP type=static      IP=192.168.1.2
                                    Network type=static netmask=255.255.255.0
                                    Gateway=static      IP=192.168.1.1
                                    multicasts=send as multicasts
I can query the pcmcia card for sana2 parameters and i have the two lan ips in the hosts database. The link light at both ends is in the connected state and miami goes "online".

windows setup: link speed 10mbps full mode (doesnt even enable the connection on anything else)authentication off. client for m$ networks ticked, file and printer sharing ticked, tcp/ip ticked. tcp/ip properties > IP address=192.168.1.1 netmask 255.255.255.0 default gateway blank (also tried with both lan ips no luck) DNS servers blank and in advanced settings enable netBIOS over tcp/ip ticked. I`v also tried wingate, proxy+ and winroute with no success. Any help greatly apreciated.

[KennyR]

Well, first things first. Can each machine ?ping? the other?

No, they can't even do that. That's the whole problem.

Next thought, netBIOS is set to OFF on my PC, as Samba runs just fine without it. Which software are you trying to run over your TCP/IP stack?

None, yet. Until the machines can be made to simply ping each other, there's no going forward at all.

[KennyR]

Are you sure that your PCMCIA card is supported by cnet.device

Absolutely sure. I know several people who use exactly the same card without problems. And if cnet didn't support the card, it would not go online at all.

You've got Samba working on your Amiga talking to Win-DOHS XP??

So have I (but not my friend, who has the problems). It's no different that doing it on Windows98. Just make sure WinXP isn't firewalling the connection.

[KennyR]

et the gateway to 192.168.1.2 (the IP address of the A1200) for the NIC that is connected to the Amiga. You can't leave it blank, because it won't know where to send any packets. You will also probably want to set it for half duplex mode.

Both done, thanks. But still nothing.

[KennyR]

Try connecting the Amiga to the cable modem (with a standard Ethernet cable) and see if it can talk to that.

I'm not sure that's possible. It's a DSL modem, not cable, and has been set up to use the PC's MAC address, and I think it uses PPPoA, which the Amiga doesn't support in any form.

Or try connecting it to your PC with two standard Ethernet cables and a hub in between.

Buying any extra hardware such as routers and hubs is not a possibility, unfortunately.

[KennyR]

I don't understand why a router wouldn't be an option.

Too expensive. My friend has no more money left to buy any routers or hubs for the moment.

Thanks for your other info, but it's pretty much the same advice that I gave him, and he's tried lots of configurations. But no luck. I was hoping it was a WinXP configuration problem with having two network cards and that someone knew a fix.

[KennyR]

Wait a minute, wouldn't the PC require a separate IP address for each of its network cards?

Yes, and it has them. The PC->Amiga network card is set at 192.168.2.1 and the PC->modem network card's IP address is dynamically allocated by the ISP.

Also, it occurs to me that unless the computers are connected directly to one another, you should use one-to-one cables instead of crossover cables.

They are directly connected. ;-)

If you cannot ping under those circumstances, then it’s a hardware fault with either one of the cards, or the cable. Check each of these with known good equipment, if possible, to determine which is at fault. If you can ping while connected that way, try adding other bits one at a time, testing after each addition.

Easier said than done. I'm beginning to suspect a bad card or crossover too, but there's no easy way to test either. I'll see what kind of resources my friend has. He'll be greatful of your help, thx.

[KennyR]

Thx Lemming. This is more or less exactly the setup I told my friend to use from memory, but he can't get any ping across at all. It's beginning to look very much like a hardware issue...

[KennyR]

I also have to mention that the crossover cable came with a network kit, and when plugged in the network card link lights go on as expected. Also the Amiga can ping the PCMCIA card and CardPrep reports correct data from the card (when not in use, of course).

So either something in hardware is very subtly broken, or something in WinXP is breaking everything.

Is there no-one out there who's had this problem with XP and found a solution?

[KennyR]

Still no luck guys. I've been asked to post this:

Thanks for your well researched and in-depth answer. although some of these settings dont appear in winXP. for example i dont have the option of disabling WINS resolution, and i have nowere to enter both local ip addresses, i also cant disable DNS. I cant find the "Set this protocol to be the default protocol" option or the Primary Network Logon section or the access control

>10) Now click the tab at the top of the window labelled 'Identification'. In the computer
>name box, delete any existing text, and type the 'hostname' you made up earlier.

Would this be an IP address or other name and would i have to add it to miami. would i need to add the workgroup name to miami also.

I seemed to have turned off the network neighbourhood icon or it may just be Networks in XP any idea how i would bring it back? Would i have to add a workgroup name somewere in miami?
If i can ping both machines local IP whilst on either computer but not the remote one what other things can i check, what about cable length or a tightly wrapped (ball of wool style) cable

in another post about win2k they just enabled ICS and ran miami init, when iv tried this miami cant find any IP addresses.