196,679 users have contributed to 43,023 threads and 258,420 posts.
In the past 24 hours, we have 2 new thread(s), 4 new post(s) and 91 new user(s).
You can try this :
Didable WIFI on all the MAC
Connect everyting using DHCP
Check if it is working
Note down every parameter
Set your Mac with FIX IP with the parameter you have note down
Tell me if it s working
I reconnected everything using DHCP and still nothing. The strange part is these were my default settings before I started messing with the static IP haha. Any suggestions why that's happening now?
Thank you for your help!
Hello
If it does not work with DHCP it is very bad.
Phone to Apple support they will help you on line to remove the files so you start from scratch (they are very helpfull and it is free)
Good luck
Hi, would really appreciate some insight here - I'm planning to connect a mac mini late 2012 as the master and a mac pro late 2009 as the slave.
1.
For connecting: Do I need a
Gigabit Switch? If so, which one??? Type gigabit switch into amazon....
Gigabit Router? See above....
Or simply, a Cat6 "Gigabit" cable? Are all cat6 cables "Gigabit", and does "crossover" matter?
2.
Can I still use wifi on the master and slave for basic web browsing?
3.
Is there a video walkthrough of someone setting up the static IP addresses? In system preferences, I configured the ethernet hardware to manual, speed to 1000baseT, but am unsure of the optimal settings for the Duplex/MTU/ABV/EAV Mode settings.
Is there anyone who does private consults on these setups? I'd be happy to pay someone for a brief phone consult. Thanks so much!
Hi there,
I don't know if you actually need a gigabit switch or not but in my experience it works better with a switch than direct ethernet cable connection. Plus you only need a small one and they are very affordable these days.
Definitely get a few Cat 6 if not Cat 7 ethenet cables. - I experienced a NOTICEABLE difference from CAT 5.
You should not need a gigabit router or a any router really. If you follow the instructions in the first thread you should be all set. Hang in there and be very thorough - It's about getting all those settings correct and restarting a lot and it will work...eventually!
Yes, you can use wifi on the master setup. You simply add an ethernet connection in system prefs and set service order.
If you really can't get it set up, I can help. felixbird.at.gmail.com
Felix
Hi, would really appreciate some insight here - I'm planning to connect a mac mini late 2012 as the master and a mac pro late 2009 as the slave.
1.
For connecting: Do I need a
Gigabit Switch? If so, which one??? Type gigabit switch into amazon....
Gigabit Router? See above....
Or simply, a Cat6 "Gigabit" cable? Are all cat6 cables "Gigabit", and does "crossover" matter?
2.
Can I still use wifi on the master and slave for basic web browsing?
3.
Is there a video walkthrough of someone setting up the static IP addresses? In system preferences, I configured the ethernet hardware to manual, speed to 1000baseT, but am unsure of the optimal settings for the Duplex/MTU/ABV/EAV Mode settings.
Is there anyone who does private consults on these setups? I'd be happy to pay someone for a brief phone consult. Thanks so much!
I on Window 10. I've setup the adaptor priorty on both systems. The VEP netowrk doesn't even show up in VEP.
The systems are connected with a stright ethernet cable; perhaps I need to try a crossover cable, though I can ping the other system.
I on Window 10. I've setup the adaptor priorty on both systems. The VEP netowrk doesn't even show up in VEP. The systems are connected with a stright ethernet cable; perhaps I need to try a crossover cable, though I can ping the other system.Have you tried turning off the Wi-Fi and getting it working? Then once you’ve got it working properly, turn the WiFi back on. Is there a difference in performance?
Both are desktop systems, so no WiFi. Each has 2 Ethernet ports, one for general use and internet (DHCP) and one for VEP (192,168.20.x) and set to first priority.
In the server connection window, the local host shows up with a strange ip, 127.0.0.1; don't remember if that was the case before. With the private network connected, the server on the slave system doesn't show up. If I unplug that cable, the slave server shows up with the with the general ip. I have a crossover cable coming tomorrow, so we'll see it that makes a difference.
I find it strange that there's so little information about working with a separate VEP network. I haven't seen anything here from VSL.
