Samba Networking

[Skippy]

Alright,

Got an a1200 networked to WinXP using Miami 3.2b and Samba via ethernet using a hub.

Amiga side everything is fine. Mounted the DOSDriver to pcc: Workbench browsing so forth ok, ping xp all works ok.

But Xp aint having none of it. In the hosts file both machines ips are binded to host names. PING Amiga or its IP fine that works ok.

But it just will not Map the drive or appear in the network group for browsing. I've verified all the protocals are installed, checked the samba scripts, miami details etc.

But Xp says the Amiga doesn't exist. I've removed firewalls, antivirus software still no luck.

I've also notice, again I don't know why, Amiga Forever's Amiga Explorer won't  connect to the a1200 reporting that it can't access the Amiga's resources. Miami and AExplorer are running. It used to work ok then stopped.

Finally when I mount my Win98 box to the a1200 on pcc2: it keeps asking me for a password, but Win98 sharing polices don't require any passwords! Neither is does Samba or Miami.

WinXP and Win98 communicate fine with each other but they don't seem to like my Amiga.

Is Xp and 98 bullying this poor little bugger and not allowing him to play in their workgroup because he's old and useless? Is it a case of "yeah we hear you knocking on the network door mate but you aint coming in. Go play with your C64 chums."

Any thoughts on this.

Skippy.

[Thomas]

Stop smbd and nmbd (open a shell window, enter status to see which processes they run on then enter break for each), then go to Samba:log and delete all files (keep the locks directory). Then try to access the Amiga again and look into Samba:log for log files with error messages.

To access the Amiga, open Windows Explorer and enter \\amiga into the address line (amiga being the host name of your Amiga). It might not appear in Network Neighbourhood until access is working.

Bye,
Thomas

[Thomas]

Forgot one thing: you should use Samba V2.0.7 from www.amigasamba.org. Later versions don't work.

Bye,
Thomas

[Jettah]

@Thomas

Forgot one thing: you should use Samba V2.0.7 from www.amigasamba.org. Later versions don't work.

I have installed yesterday V2.2.5. Works very fine on my A1200. Mounts the various shares on the XP-box without any problem! And rather fast that is.

Have not yet tried it on my A1 yet, but I'm shure it'll work simmilarly.

Regards,

Jettah

P.s. I've got other worries with my A1200 currently. H/W worries. Jakkes!

[Skippy]

Regarding the version number, I'm actually using version
1.9.16p9

Which if what you're saying is true means I'm bashing my head against the wall in confusion when I've not done anything wrong and that the software is to blame..

I will however try your suggestions.

Skippy

[KennyR]

Do you have a LMHOSTS file set up on the Amiga Samba?

[Elwood]

Here, my Win2K needs to be set up with "people need to enter a login + password to use this computer" in order to access my Samba-ed A1.

bye

[Thomas]

I have installed yesterday V2.2.5. Works very fine on my A1200. Mounts the various shares on the XP-box without any problem! And rather fast that is.

Yes, I didn't consider the new port of V2.2.5. The ixemul-based port available on amigasamba.org doesn't work. The new port available at amigaos.dk is quite fine.

Here, my Win2K needs to be set up with "people need to enter a login + password to use this computer" in order to access my Samba-ed A1.

Well, I am not so firm with all the security settings. However, on my home network I can access any share on any computer, no matter if I supply a password or not. Even those drives which were set up with a password can be mounted without. I'm using WinXP Home, though.

So my suggestion for every Samba beginner is to hide his network from the internet by a NAT router in all cases. (I for one will never again connect a Windows computer to the internet without an external router/firewall. Last time I did it lasted about one minute until the PC was shut down by one of those Blaster viruses or whatever they are called).

Bye,
Thomas

[KennyR]

Uhm, I think the 2.2.5 port is not fine after all. It seems name resolution doesn't work. Although you can use the samba network, the machine/share names don't appear in Windows. This is your original problem, Skippy, and I think it's the 2.2.5 port's fault. The same happens if you don't use nmbd at all, so it looks like nmbd is faulty.

I've gone back to 2.0.7 and I got things working again immediately. If nmbd works in 2.2.5, I don't know how to set it up.

(Swat doesn't seem to work either. :-()

[MiAmigo]

I had the same prob with Samba, but, unfortunately, I was rather easily distracted by 'something else' (who knows what) and never quite resolved it. When last I worked on it, I had everything fully enabled, with my Amiga able to see all the shares across my network, but with none of my PCs, or Linux machines were able to see it (the Amiga). And I'm pretty sure I did everything right. I'll be watching this thread, to see if any solutions comes up.

[Fats]

You can try to find out if it is a problem with the name or the whole sambe configuration on the amiga. With windows explorer try to access \\amiga-ip.address directly without a name and see if that works.

Staf.

[MiAmigo]

Fats wrote:
You can try to find out if it is a problem with the name or the whole sambe configuration on the amiga. With windows explorer try to access \\amiga-ip.address directly without a name and see if that works.
Staf.

That'll probably work. I was able to ping the Amiga by IP address from my PCs. So, that may indicate a DNS problem. I'll try it out.