Lee's answer made me wonder if someone would have the answer to this. For 8 hrs the guys worked on setting up 4 servers. First we had a problem getting them to set up remotely, and we had another problem using ethernet to boot one in target mode (we were following the steps one at a time from the Apple manual) but these two things would not work, this morning I am convinced that it is because we were going through the Cisco switches instead of connecting an ethernet cable from one computer to another direct, like you do with the firewire cables using Target mode, which is what we eventually had to do in order to reset the password on one of the Mini Servers. This place looked like NASA, there were 5 computers going on my desk at one time, plus an iPad. The one man that knows the hardware had one of his servers in Cincinnati go down so he was working on that at the same time he was working on all this mess. We had ethernet cables all over this house. I was getting a headache just trying to figure out what they were doing.
Anyway all four were done and the software was loaded and here is where we ran into our hurdle that we could not figure a solution. Called Apple Server support and the only thing they could suggest was to upgrade the Pro to ver. 10.6.6. For some reason all three of the Mini's had 10.6.6 but the Pro had 10.4.0. We knew that would not work but we did it anyway. Our database looks for the socket to connect the database to SQL in a certain location, which is where it has always been. We have been running this on three different computers for months, my laptop pro, a mini here at home and then a mini in Cincinnati. However on the true SERVER models this particular .lib (I have no idea if I am saying this correct) file is in a different location so our database will not connect with Apple's Server SQL. We would move the location and on restart it would go right back to it's original location. To solve this they tried several methods, nothing worked. So, if they can find a solution as to how the SQL that is Apple's that runs the database can talk to the SQL that is Apple's server we have a problem. Apple did say that they would give support to individual software problem at the rate of $600+ per issue, or something over a thousand a year. UGH, those guys come expensive. So, if any of you have worked with Apple's Snow Leopard server and have the foggiest idea of what I am ignorantly trying to say any help would be appreciated. As far as the 50 meg download, boy was it helpful yesterday when all these machines were hitting the switches and Insight's 50 meg, the guys were amazed at how fast we could accomplish all we were doing. John On Jan 16, 2011, at 10:04 AM, John Robinson wrote: > Lee, as always many thanks. Just Friday I had two men here trying to set up > the three server's, one thing they downloaded was a program called dyndns, I > believe. I am going to talk to them about what you have just sent, I am sure > this will help. > > John > > > On Jan 16, 2011, at 9:27 AM, Lee Larson wrote: > >> On Jan 15, 2011, at 11:22 PM, John Robinson wrote: >> >>> I can't say for sure but of late the 50 meg. download has some issues. >>> Each time you use Speedtest.net indeed you are getting the 50 but when you >>> go to a site you sit there and wait and wait, then it loads. I don't know >>> if Insight is having to choke it down to accommodate some sites or if there >>> is some other issue, I will call Monday but it is ridiculous the latency, >>> even with email. Now the Google Finance site loads in an instant, I just >>> loaded the Lexus site and it was instant, Ford was instant, GM instant, >>> Progressive instant, Geico instant, Amazon waited for many seconds, Canon a >>> small delay, Dodge a slight delay. Some of these are there as soon as you >>> let off the key, others have a slight hesitancy and some take forever. >> >> What DNS are you using? I have found that changing away from the Insight DNS >> to OpenDNS or the Google Public DNS makes a big difference. Another thing >> you could try is to add sites you always use to your local /etc/hosts file. >> That bypasses DNS entirely because your machine always looks there first. >> >> But, there's not much you can do about the inherent latency of the Internet >> and the servers you talk to. That's why I don't think faster connections are >> such a big deal, unless you're running lots of computers or are constantly >> downloading mega-files from a really fast site. >> >> There are a few drastic things you can do if you're sufficiently rabid for >> speed, and I've tried some them just to tinker. For example, you can use >> your own caching DNS server or even a Squid proxy. They made a noticeable >> difference back in the halcyon dial-up days of yore, but stopped being so >> useful when broadband arrived. >> >> >> >> _______________________________________________ >> MacGroup mailing list >> [email protected] >> http://www.math.louisville.edu/mailman/listinfo/macgroup > > > _______________________________________________ > MacGroup mailing list > [email protected] > http://www.math.louisville.edu/mailman/listinfo/macgroup
_______________________________________________ MacGroup mailing list [email protected] http://www.math.louisville.edu/mailman/listinfo/macgroup
