Hyperion Entertainment Message Boards

Posted: **Thu Oct 31, 2013 10:47 pm**

Oui, comme davebraco a ecrit

Except that I chose to create a new directory inside Devs called Servers and copy the server there - I somehow don't feel it belongs in C. But as long as you set up your Servers page/file to point to it, it doesn't matter where you put it.

Also, I have chosen to follow the advice in the docs and select a different port number than 2500 for obscurity; this has consequently been changed in my Services config as well.

And yes, it works just fine with RoadShow.

BTW, someone told me some time ago that it isn't necessary to add the colons after the device names in the NetMount command, so I have gotten into the habit of omitting them. And I have never had to explicitly add the handler specification to the command. E.g. "Netmount mysam sys rh1" would work for me (if I had a host called mysam).

Best regards,

Niels

Posted: **Fri Nov 01, 2013 5:21 pm**

@davebraco
merci beaucoup.
@nbache thanks for more info

That was very clear. however i don' t get connected ( i tested in both directions)

In the shell i get a message "unrecognised error" and this is the Snoopy trace

Hidden Text - Click to Show :

Posted: **Fri Nov 01, 2013 8:03 pm**

Code: Select all

c:netmount 460 Sys: rh1: handler=l:netfs-handler

It seems correct.

Could your post your hosts config of both sam please?

Posted: **Sat Nov 02, 2013 10:46 am**

Here are my settings, i only copied those that were changed
Doing this i remartked a difference in the 440 & 460 settings i changed
nameserver=192.168.1.1 // was 8.8.8.8 and did not work either.

I just realised i did not reboot though. I'll try that now

Hidden Text - Click to Show :

Posted: **Sat Nov 02, 2013 12:17 pm**

It is emerging that one of his machines is a Sam460ex.

nbache wrote:
Spectre660 wrote:So the issue linked to below is working for you now ?

http://213.133.108.237/viewtopic.php?f= ... 504#p15876
No, it's still the same. But it doesn't bother me much, as I can still mount the 460's drives from another machine and transfer in both directions through that.

And anyway, the OP mentioned using a 440 (flex), and I don't have any problems on my 440ep, so I decided it was not worth mentioning here.

Best regards,

Niels

Posted: **Sat Nov 02, 2013 8:54 pm**

So here is the IP important parts :

Sam440
192.168.1.3 localhost localhost.my.domain
192.168.1.6 460

Sam460
127.1 localhost localhost.my.domain
192.168.1.5 440

I'm not a specialist but it seems that your Sam440 has the IP 192.168.1.3 but the Sam460 try to access the Sam440 via the IP 192.168.1.5.
If you are using DHCP, you can know your address by entering : c:shownetstatus in a shell.

It's better to use a fixed address instead of DHCP (or maybe you could reserve the IP address in your router)

Posted: **Sat Nov 02, 2013 9:43 pm**

@davebraco
Thaks

I corrected to the values given bu shownetstatue., but still no connection. Snoopy is not informative, only thing i se : not calling netfs-handler, but netfs-handle (though my command line is OK.

Is there any way to follow what is going on other than snoopy?

Posted: **Sat Nov 02, 2013 10:52 pm**

Guys. For the Second time.
Sam440ep to Sam460ex AmigaNetFS and Samba does not work.

Posted: **Sun Nov 03, 2013 1:03 am**

Spectre660 wrote:It is emerging that one of his machines is a Sam460ex.

Yes. In that case, it won't work to netmount a 440 drive on the 460, but only the other way.

Best regards,

Niels

Posted: **Sun Nov 03, 2013 1:05 am**

Spectre660 wrote:Guys. For the Second time.
Sam440ep to Sam460ex AmigaNetFS and Samba does not work.

I'm pretty sure it does work (at least did here the last time I tried) from 440 to 460, just not from 460 to 440.

I can't check right now, though, as my 460 is not connected.

Best regards,

Niels

Hyperion Entertainment Message Boards

Ethernet communication between 2 SAM's

Re: Ethernet communication between 2 SAM's

Re: Ethernet communication between 2 SAM's

Re: Ethernet communication between 2 SAM's

Re: Ethernet communication between 2 SAM's

Re: Ethernet communication between 2 SAM's

Re: Ethernet communication between 2 SAM's

Re: Ethernet communication between 2 SAM's

Re: Ethernet communication between 2 SAM's

Re: Ethernet communication between 2 SAM's

Re: Ethernet communication between 2 SAM's