![]() ![]() Moving windows around like crazy otherwise not a problem, responsiveness perfect. it seems that the clock running on the tiger computer was causing lion to refresh that entire desktop, and then pump out that image over vnc constantly.īy turning off anything at all updating on the lion system (seconds on the time, istat menus refreshing) data has now trailed off to zero whilst resting. Ok, a bit more testing, and it seems that on closing the tiger vnc connection, the data output from the lion box dropped to 10k/sec. Whilst Im able to access a lion machine from my SL laptop, and from that Lion machine, Im able to access a tiger system, for some reason, in their restful state the tiger machine is sending zero data, but the lion machine is pumping it out at a meg a second. Also, we're using the built-in VPN connection with the Cisco settings, not the Cisco thick client nor the An圜onnect client. perhaps the virtual interface of the VPN or the statefulness of the VPN connection are factors. We're using Wireshark and Cisco NAM to try and isolate things further. The VPN solution is the only thing that's worked on our local campus and we just stumbled upon it. Ironically, my 10.7.2 Mac has piss poor performance trying to VNC to this Linux system, but I can VNC from my Mac to my Mac Mini at home on my home network w/o issue. The problem is specifically with Lion systems trying to VNC to a remote system. Built another Linux system for testing and had the same results. A Windows PC with TightVNC or RealVNC can hit the Linux PC w/o issue. Leopard and Snow Leopard can connect to the Linux host just fine. We're using the built-in Screen Sharing app (Finder, Apple + K, vnc://hostname). The remote Linux system (CentOS)has only one monitor. Our scenario is any Mac trying to VNC to a Linux system here on campus. In any case, if you're having performance problems using VNC to access another system (Mac, PC, or Linux) from a system running 10.7 and you have a VPN, try connecting to it and see if it resolves your issues. We haven't deduced the actual problem just yet, but we think we're onto something related to either the virtual interface and/or the statefulness of the VPN connection. There appears to be something about the virtual interface that's created that works whereas using the default en0 (wired) or en1 (wireless) interfaces are problematic. That caused us to try having the system connect to our VPN while on the local campus and sure enough it worked as well. The same laptop on the local network would get absolutely unworkable performance on the local wired or wireless network, but would work just fine over our Cisco VPN (but using the builtin VPN options for the Mac, not the Cisco VPN client) from outside our campus. In testing to make sure our network wasn't part of the problem, we tried to VNC to a system over our VPN from outside our office. These same issues do not exist with Leopard or Snow Leopard. ![]() See, for example, this Apple Discussion thread. Here's a workaround for some VNC issues that may appear with Lion.Ī quick search will show a growing list of users having issues with VNC in Lion. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |