|
|
|
|
#1 |
|
Prospect
Join Date: Apr 2007
Posts: 3
|
OS X Server serving up web pages
Our office has a new OS X Tiger server (and I'm not a tech-savvy guy) but...
Since upgrading our server from OS X Jaguar to Tiger we've noticed that the eMac computers (all running OS X 10.3.9) on the network have all slowed down in their Internet functionality, while our newer MacBooks (running Tiger) and even the lone PC (running Windows XP) have all maintained their speedy Internet connections running through that same DSL connection, which first passes through our server. Both the good and bad Internet connections above share the same routers, LAN, switches, and cables. The only difference is the operating systems. When we switched to the new Tiger server the only things that changed was that operating system, but immediately we noticed the lag time in calling up web pages. The lag time s substantial (i.e., 10-30 sec. on the eMacs running Jaguar vs. 1 sec. on the MacBooks running Tiger and PC running Windows XP), and since we call up hundreds of pages/day we can save a lot of time by fixing this issue. I doubt the eMacs have an inherent problem, as they all worked great when we were running the Jaguar server, and the problem began when we so-called upgraded. My question is: Is there a setting on either the eMacs or the server that might improve this situation? |
|
|
|
|
|
#2 |
|
Hall of Famer
Join Date: Sep 2004
Location: Chicago, Illinois
Posts: 3,191
|
Jaguar is mighty old now. Any Panther machines around to see how they do?
Joe VanZandt |
|
|
|
|
|
#3 |
|
Moderator
Join Date: May 2003
Posts: 4,272
|
Saying "serving up web pages" is a bit of confusing. Do you mean that your server is acting as a gateway for the office internet connection, or that it's running a web server?
The only thing I can think of, which shouldn't make a difference, is messing with the IPv6 settings on the machines. Maybe turning IPv6 on or off would produce a change. However, I do want to say that using your server as your Internet gateway is usually a losing proposition anyway. It is much more efficient to use a dedicated firewall router. For starters, if you need to do server maintenance, no one loses their internet connections. And packet routing isn't competing with other tasks for computing resources. You also don't have to worry that a software update will have unintended consequences. |
|
|
|
|
|
#4 |
|
Prospect
Join Date: Apr 2007
Posts: 3
|
Dear giskard22,
Thank you so much for your reply. I wish I were more tech-savvy, so I appreciate you clarifying the terms for me. Yes, our server is a "gateway" and I'm glad to hear that this does not have to be the case. I'm going to speak to our MacIntosh consultant and the contractor who set up our network this way to have him set up a "firewall router" as you suggest. |
|
|
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|