Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: mikey2001 on January 08, 2004, 05:18:23 PM
-
Hello people, I am currently having a few problems with my network setup.
I have a XP Pro PC connected to a 4 port Ethernet hub which in turn is connected to an ADSL router. There is also a Win 98 machine connected to the hub. I also have an A3000 with an Ariadne network card and AmiTCP installed. I thought it would be a good idea to network the three machines together but I am having no joy.
I have 'pinged' the A3000 in the shell and the Ariadne is definately working, as are the PC network cards, as the PCs can see each other but not the Amiga.
Please be gentle, I have been away from the scene since 1999 and only recently started getting back into Amigas again. :-)
-
Ok I try to help you :-)
But we need some more details
Are you using fixed IP's or has the router DHCP ?
If you wanna share drives then you need SAMBA.
(It's a bit hard to install)
And you have to remove the encrypted password setting in the registry. (Win2k+XP)
I suggest you to try to connect to the W98-Box first..
-
AFAIK the router uses DHCP and the IP address is not fixed on the PC side. SAMBA is configured as well AFAIK. :-)
-
My samba setup works !
But I use fixed IP's (also the PC's)
I tried with DHCP but since Genesis doesn't support it..
-
I do know the IP addresses of the network:
Router: 192.168.0.1
XP PC: 192.168.0.3
A3000: 192.168.0.30
(Not too bothered about the other PC at this moment in time)
Mike
-
Things to keep in mind:
In MiamiDX (don't know if this applies to AmiTCP), hostnames need to be manually matched up to IP addresses. If the addresses change (DHCP), the settings must be adjusted.
Samba needs the nmbd and smbd daemons running to work properly (smbd isn't really mentioned in the AmigaSamba config guide). The nmbd allows the PC to actually access the Amiga, smbd will bring the Amiga up in the Network Neighborhood listing. I'm sure they do other things, too, but I don't know what.
For some reason, the nmbd no longer works on my home network (though it did work at college - probably a PC problem). The nmbd is failing to resolve something, and not starting. The samba logs can help here. The Amiga can read the PC, but not vice versa.
It sounds like we might have the same problem. Check your nmbd logs to see what they say.
-
NMBD? SMBD? Im sorry, im not really a networking person, i dont have much experience networking any computers let alone Amigas lol!
I think using fixed IP addresses on both sides maybe the way to go though... :-)
-
mikey2001 wrote:
NMBD? SMBD? Im sorry, im not really a networking person, i dont have much experience networking any computers let alone Amigas lol!
I think using fixed IP addresses on both sides maybe the way to go though... :-)
SMBD and NMBD are two programs in the Samba package. The easiest way to use them is to execute a script upon going online:
Run >NIL: Samba:bin/nmbd -D
Run >NIL: Samba:bin/smbd -D
My script also has some MiamiSysCtl InetD stuff in it, too but I'm not at my Amiga right now so I can't check the exact setup.
This used to work perfectly... Maybe you'll have better luck.
-
mikey2001 wrote:
NMBD? SMBD? Im sorry, im not really a networking person, i dont have much experience networking any computers let alone Amigas lol!
I think using fixed IP addresses on both sides maybe the way to go though... :-)
I had no end of problem with DHCP... but I only have 5 machines, so I just set them all up wirth static adress everything worked fine after that.
-
Erm...... I don't know what to say really. As I have said before I am not a networkin person, but when noticed that the piece of Cat 5 cable had a 'cross-wired cable' label on one end I thought "what would happen if I changed the cable?"
Yes exactly, everything worked first time and I can now communicate between the two machines. Definately a case of you learn by your own mistakes.... :roll: :oops: :oops: :oops:
Many thanks to all those who offered their advice and expertise though. :-)
Mike