Amiga.org
The "Not Quite Amiga but still computer related category" => Alternative Operating Systems => Topic started by: orange on November 11, 2004, 04:53:25 PM
-
I would like to connect Amiga to a PC using nullmodem cable and MiamiDX. (did this with 2 Amigas and got a bit greedy now :-D ) The problem is that MiamiDX.guide explains only connecting to win95/98. The PC should be router. It seems that MiamiDX help tells that BOTH computers should dial each other :-?
How do I configure winXP(Home)?
-
Hum,
i imagine that they are basically the same...
But first, if you have Norton firewall or another firewall, check that it does not block the accesses of the network...
And use cross cables etc....
check out this site for better info (http://www.skratchy.demon.co.uk/cnet_main.html)
-
Assuming you don't have network cards for both computers .
(been a long time since I've done SLIP & PPP over serial cables )..
-
Hum,
best to download a guide from aminet....
Run MiamiInit. Select a "nullmodem" connection, and turn off the
"Internet" and "DNS" options.
then look at this (http://www.ncf.carleton.ca/freenet/rootdir/menus/sigs/computer/amiga/res/other/Amiga_PC)...
or
amiga universitys guides... (http://www.amigau.com/c-networking/cnhome.html)
-
Hmmm, I probably need one of them to be set as dial-out, not dial-in.
When I go online on Amiga side, I can see PC dialing a number.
But, after clicking "send Break" nothing happens. PC constantly just displays "dialing number".
How should it be set up? :-? :-?
-
I've done this with Win2k, so it's probably very similar with XP (but Home might be a little different).
What I had to do was make a new network connection.
The first question the wizard asks is the type of connection you want. You have to pick "Accept Incoming Connections".
Then pick the port that you are connecting your Amiga to.
Next I answer "no" to the VPN tunneling question.
Then you have to choose or add a user that will be allowed
to connect.. this is the user and password you use for
Miami.
The rest is pretty straight forward, except for one part which I don't remember the details of any more.. :-(
What I do remember is I had to edit a *.mdm file in Windows somewhere, and change an init string. Something about the way Windows PPP works that doesn't work with Miami out of the box. I found the info on Google at the time.
Once that's done, IIRC I just had to set up Miami for a PPP Connection using MS-Chap for authentication, put in the user name and password from the PC, set it to do a direct connection so it doesn't try to talk to the modem, and that was it.
Clear as mud? :-)
Hope that helps a little, at least!
If you get stuck, let me know and I'll check on the A3000 and see if it's still got that config set up in Miami.
-
I hadn't tried what you said, still
I made some progress (finally).
Amiga can ping PC :banana:
It seems that mdmcisco.inf asks this as reply:
CLIENTSERVER
when PC dials Amiga. So I put that as login name, pressed "send loginid" on Amiga and voila, it worked.
Now all I need is to somehow connect SLIP and Ethernet on PC side ("bridge" is the word, I think) Can that be done in XP home or some external program like Wingate is necessary?
BTW, some help can be found here, too (in case someone needs it):
http://web.archive.org/web/19991009113538/home.intekom.com/jacog/howtonet/configamiga.html
-
Glad you hear you got it connecting! :) Have you tried entering the IP address of your XP machine as the gateway in Miami? That should allow you to access the rest of your LAN and the internet.
-
Yes, I did enter it as gateway. Unfortunately it still doesn't work. I've installed WinGate on XP, but it didn't change anything. This is my setup:
2 PCs +1 cable modem all connected to switch
1 Amiga connected with serial to one of those PC.
Whatever I do, Amiga can't ping the "remote" PC (non serial one). It does try, however, as the network monitor in Wingate shows activity every time I try ping.
I have shut down ALL firewalls, what is there left to try? :-? :-? :-? :-x
-
Is your Amiga able to resolve names? If you try to ping
www.amiga.org does it resolve that to an IP address?
Or, can you ping an IP address from your Amiga like
64.233.167.99?
As for why you can't ping the remote PC on your LAN.. not sure about that. Are you letting Miami obtain all of its settings with DHCP? Maybe the subnet mask needs to be set a particular way.
-
If you correctly set up the SLIP link you shouldn't have needed to install Wingate. Windows 98SE onwards includes "Internet Connection Sharing" which will happily forward packets from your internet connection to the SLIP line.
Caveats; it refuses to work on any other configuration than plonking itself at 192.168.0.1.
Without knowing what your current network is beyond connecting an Amiga to a PC, it's a little hard to say if that would be adequate? I assume though since you're going so far as using a serial line, that your "network" is entirely absent :)
-
I tried setting SLIP to 192.168.0.1 (PC) and 192.168.0.2 (Amiga), but that didn't change anything.
PC is DIRECTLY (ETHERNET LAN) connected to cable modem and it has Internet connection. The problem is that Windows XP Home doesn't have an option for ICS on LAN adapter, only on dialups. And if I try to set ICS on SLIP (which is probably silly, but hey what the heck..) it warns me that LAN adapter would be set to 192.168.0.1 which probably means byebye Internet.. :-?
pinging anything but 192.168.1.1 or 192.168.1.2 from Amiga doesn't work. Here is "route print" from PCrouter:
http://qrange.150m.com/nrt.txt
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...08 00 46 57 43 a9 ...... Intel(R) PRO/100 VE Network Connection - Packet Scheduler Miniport
0x120004 ...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 10.1.0.2 10.1.92.196 20
10.1.0.0 255.255.0.0 10.1.92.196 10.1.92.196 20
10.1.92.196 255.255.255.255 127.0.0.1 127.0.0.1 20
10.255.255.255 255.255.255.255 10.1.92.196 10.1.92.196 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.1 192.168.1.1 1
192.168.1.0 255.255.255.0 192.168.1.1 192.168.1.1 50
192.168.1.1 255.255.255.255 127.0.0.1 127.0.0.1 50
192.168.1.2 255.255.255.255 192.168.1.1 192.168.1.1 1
192.168.1.255 255.255.255.255 192.168.1.1 192.168.1.1 50
224.0.0.0 240.0.0.0 10.1.92.196 10.1.92.196 20
224.0.0.0 240.0.0.0 192.168.1.1 192.168.1.1 50
255.255.255.255 255.255.255.255 10.1.92.196 10.1.92.196 1
Default Gateway: 10.1.0.2
===========================================================================
Persistent Routes:
None