Does anyone else have this same problem after having updated the latest Snow Leopard update 10.6.2: I turn off my Mac Pro for the night, open in the morning, open the project I was working on (in DP 7.01), and the connections from VE Pro plugins (4657) to PC slaves' VE Pro:s are lost. In the server interface I see the slave computers listed, but not the preserved instances that are open. I can fix this by turning the "internet sharing" on my Mac off and then on again. It seems to refresh the connections. And then connect the plugins all one by one.
-
New Snow Leopard update - server problem
-
The plugins try to find each slave instance (I have 7) for like 1 minute so it takes time for the projects to load. After it is loaded with all plugins showing "not connected", I have to connect them to their instances. For some reason all the instances can be found manually. It would be good if the plugins don't find the instances, it wouldn't try to find them for as long as they do now.
-
I emailed VSL about this problem last week and got this fantastically prompt response (the VSL support really is top notch by the way):
-----
Do you use DHCP for your slave computers? When the DHCP lease times
out, and you turn on your slaves the next day - they get their IP
addresses changed and VE Pro cannot recognize them anymore.-----
As I'm not much of an expert on networks I don't know how to change this. There are a variety of other configuring options available - Using DHCP with manual response, Using BootP, Manually, Off, Create PPPoe service - but I'm afraid that being the ignoramus I am, I'll completely screw up my system if I start fiddling!
-
@Nick Harvey said:
I emailed VSL about this problem last week and got this fantastically prompt response (the VSL support really is top notch by the way):
-----
Do you use DHCP for your slave computers? When the DHCP lease times
out, and you turn on your slaves the next day - they get their IP
addresses changed and VE Pro cannot recognize them anymore.-----
As I'm not much of an expert on networks I don't know how to change this. There are a variety of other configuring options available - Using DHCP with manual response, Using BootP, Manually, Off, Create PPPoe service - but I'm afraid that being the ignoramus I am, I'll completely screw up my system if I start fiddling!
Use the manual configuration. Set one computer's IP address to 192.168.0.x where x is an number between 0 and 255 unused by other devices on your local network. Set the Subnet mask to 255.255.255.0. Repeat on the other computer but use a different number for x (on my system I use 125 for one and 175 for the other). Your IPs are now fixed! I don't use a switch between my 2 machines but if you do then you may well have to reboot it.
Hope this helps.
Martin
-
Thanks for that Martin.
Unfortunately, after following your advice I wasn't able to get internet access (either airport or ethernet - my ADSL router is attached to the network switch which must have something to do with it). Obviously I've had to revert back to the original settings - life without internet? Has there ever been such a thing? - but before I did so, all computers were showing up on the network and there was indeed a connection on first launch of the project. :)
It's a shame that my ADSL router doesn't seem to like the manual settings. Any other ideas?
Hope you're well.
Nick
-