Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Forum Jump  
[SOLVED] VEPro 5 - connection problem
Last post Wed, Apr 18 2018 by jussi.lampela, 7 replies.
Options
Go to last post
Posted on Tue, Apr 17 2018 12:18
by jussi.lampela
Joined on Tue, Oct 12 2004, Posts 17

Hi folks,

 

Need help urgently: VEPro  is not connecting my two OS X computers anymore. It used to do this fine a couple of weeks back, now when coming back to work it does not.

I have two computers, a mac mini and a macbook pro, both running High Sierra and VEP5 (the latest update of 5). I'm primarily using VEPro with Sibelius (Ultimate). The two computers are connected with an ethernet cable, without a router.

I'm attaching a picture of my network settings from both computers (the other machine OS has the Finnish language, but the idea should be clear...). I tried having both fixed and dynamic IP addresses, no luck. Left it right now at fixed.

Anyone? Will mail support of course if no answer here.

 

best,

 

Jussi L.

File Attachment(s):
Sibelius-VEPro.png (411kb) downloaded 1 time(s).
jussi.lampela attached the following image(s):
Master.png (72kb) downloaded 0 time(s).
Slave.png (92kb) downloaded 0 time(s).

You cannot view/download attachments. Try to login or register.
Posted on Tue, Apr 17 2018 12:57
by marnix
Joined on Tue, Mar 16 2004, Vienna, Posts 975

Hi Jussi,

Please set the Subnet Masks to 255.255.255.0 (instead of 255.255.255.255) on both machines.

Best, Marnix

Posted on Tue, Apr 17 2018 13:28
by jussi.lampela
Joined on Tue, Oct 12 2004, Posts 17

SOLVED:

The subnet was the answer! Although I get along with computers somhow decently, any network related things drive me more or less crazy, and this is the first time I've had to touch the subnet settings. What does it do anyway, why is the automatic setting not good?

 

best,

 

 

JL

Posted on Tue, Apr 17 2018 14:41
by snakem
Joined on Mon, Mar 19 2018, Posts 6
In short the subnet mask defines which IP-Adresses are directly and physically reachable from the given local IP-Adresses interface. Those are the IP-Adresse that are „on the same wire“ as the local interface.

A netmask of 255.255.255.0 in the given case means the all packets to IP. adresses 192.168.1.xxx (with xxx being 0 to 255) can be sent out directly over the interface to reach their destination.

For all masked parts (with 255.255.255.0 the first three bytes = the first three dot separated parts of the IP address) the packets will be sent to the default gateway configured on the interface (typically set via DHCP), that then knowns to whom to route those packets in order to reach the destination IP.

So, a 255.255.255.255 means that no other IP can be reached via the interface (not even the gateway). Can not work this way ;-)
Posted on Wed, Apr 18 2018 06:40
by jussi.lampela
Joined on Tue, Oct 12 2004, Posts 17

ok, thanks! Got it somehow....

But actually, the problem persists:

Didn't have time to check last evening if it indeed was working. The dialog in Sibelius reported different static IPs than I had specified in the network configuration-dialog (ending in .142 and .194 for my two computers). Also, the local machine (Mac Mini) now showed an IP address 192.168.1.194 in the VEPro connect-dialog, that has previously been listed only as "localhost etc..."

Also, the sound from the slave was severely distorted and with a big latency, and turning of Wifi confirmed my suspicion that it was trying to connect via Wifi (or so it seems).

So the manually set IP-addresses still don't show up (Master: 192.168.1.7, host: 192.168.1.8, subnet mask255.255.255.0)

Sent to Marnix by email as well

File Attachment(s):
Master-strangeU0020IPs.png (465kb) downloaded 0 time(s).

You cannot view/download attachments. Try to login or register.
Posted on Wed, Apr 18 2018 08:42
by snakem
Joined on Mon, Mar 19 2018, Posts 6
You may try to enter the respective IP adress directly. “localhost” is the default name for IP adress 127.0.0.1 that is internal (or virtual, you have that even if your computer does not have any physical network card at all). This IP simple means “this computer itself”.

So, after configuring your network card (NIC) your master computer has indeed two IP adresses: the 192.168.1.194 on the NIC and 127.0.0.1 (localhost) internally. For the software running locally it should not really matter which one to use.

To see wether it works on the lowest level you can open a terminal window on the MacMini (simply use spotlight to search for “terminal”) and enter e.g. “ping 192.168.1.8”. That sends special “test” packets to the given IP and sees wether it responds.

Simly understand that an IP adress is “per interface”, not “per computer”. In your case that may be e.g. 127.0.0.1 (internal), 192.168.1.194 (dynaminally set on the WiFi card via DHCP), and 192.168.1.7 (manually set on the LAN NIC) all at the same time. If an other computer connects to you via 192.168.1.194 then the connection will be via WiFi, if it connects via 192.168.1.7 it goes via LAN in this example. The same target computer, just an other adress (and route).
Posted on Wed, Apr 18 2018 10:05
by jussi.lampela
Joined on Tue, Oct 12 2004, Posts 17

yes, thanks all for the help.

Case is now closed, the subnet mask was at first the critical thing, that had to be manually corrected to 255.255.255.0.

After that it still tried to connect via wifi (saw only 192.168.1.194 and 192.168.1.142, the wifi ports presumably).

After that, disabling wifi on the slave forced the manually set IPs to come alive, and now it seems to work again.

Just have to remember to not use wifi on the slave....

 

best,

 

 

JL

You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.