Hosting IPv6 Website on Snow Leopard Server

I'm currently going through the IPv6 Certification offered by Hurricane Electric just for kicks and giggles. I already have a IPv6 tunnel running on my Time Capsule router(since my ISP is not providing IPv6 addresses yet) and have a valid IPv6 address manually assigned to my Snow Leopard Server.
I created an AAAA record (ipv6) on my external DNS host that points to the IPv6 address of my server. I also created a website at using the ipv6 subdomain, made sure the site pointed to the IPv6 address of the server and that it was hosted on TCP port 470 (I'm assuming this is the website port for IPv6 - at least Snow Leopard Server thinks so). I also made sure this port was being forwarded from my router.
When testing my website by using an external website tester it says that my AAAA hostname is correct but that it can't reach my website via IPv6. I did make sure to have an appropriate CNAME record for ipv6 on my internal DNS server but I can't add records - at least through Server Admin GUI - for IPv6 addresses. I know this isn't supported via Server Admin GUI but I can't find any documentation on how to add IPv6 addresses for the internal DNS server and if this is even necessary.
I can reach the site when I'm on my internal network - though I'm not sure if I'm reaching it via IPv6 or IPv4. Does anyone have any information or experience on hosting an IPv6 website on Snow Leopard Server?

I found the issue was that I was blocking all incoming connections via IPv6. I edited the firewall to allow ports 80 and 443 and also changed the site to use port 80 (I don't know why Server Admin changed the port to 470 when choosing the IPv6 address) and I was then able to access the website via IPv6.

Similar Messages

Hosting website on Your own Mac or Mac OSX Snow Leopard Server?

I have been looking at ways of hosting my websites on my own Mac - how could I do this other than purchasing a copy of Mac OSX Snow Leopard Server?
I know you can turn on file sharing, but how can you display your sites?
Can you host more than one site with domain names and does this mean that you would be able to ditch web hosting with a company if the sites were hosted on Mac or Mac OSX Server?
Thanks for any help that anyone can give me with this.

Ethmoid wrote:
I know you can turn on file sharing, but how can you display your sites?
The key appears to be turning on Web Sharing within Sys Pref's Sharing pane. Also, THIS Apple page says: +"Every Mac user has a Sites folder in the home directory automatically configured for local hosting within Apache."+ And the following Apple doc says: +"You can also share a website on your computer by placing files in /Library/WebServer/Documents on your hard disk."+:
_Mac OS X 10.6 Help — Sharing a website on your computer_
The second of these two articles is old, but still may be useful:
_How to Turn Your Mac Into a Web Server_
_Apache Web-Serving with Mac OS X: Part 1_
And this article asks the qstn:
_Should I host my own web server?_
...More articles related to hosting a website on your Mac may be found HERE.

Does Snow Leopard Server come with a website design software

I'm running Snow Leopard Server on my Mac Mini-We've decided to take our website in house, and have set it up on the server. The site was created by someone for us and is in HTML files. Is there software that came already on our server that will permit us to edit the files, or do we have to buy additional software? I don't see iWeb on our server. Thanks.

iWeb works, but many sites will find it limiting (eg: no imports) or will outgrow it.
The typical evolution is from static HTML web pages and CSS and such along to some sort of web content management system (CMS). That might be home-grown, open-source, or commercial, and most of the CMS packages can be "themed" to present a particular appearance. Static HTML doesn't scale, and gets fussy to manage.
If static HTML is your chosen path, then Web (HTML) editors are widely available, and do get discussed here on occasion. Some that are mentioned include Adobe Macromedia Dreamweaver, RapidWeaver, Webacappella, Freeway, etc. (Google for details, reviews, trials, etc)
Migrating your server in-house means maintaining the server and its security, keeping any CMS you pick current, and getting DNS and some other pieces in place, and run-of-the-mill stuff like regular backups and monitoring disk space, and dealing with the usual network and hardware errors.
One of the other options (as differentiated from operating fully in-house) is to host your web site and related pieces on one of various hosting providers. (That outsources a bunch of the "fun" here, and usually for little money.)

Configure DNS on Snow Leopard Server for Web Hosting

Hi Everyone,
I put together an article on my blog about Snow Leopard DNS setup for web hosting. http://www.mkahn.com/?p=279
I'll be revising it over the next few weeks to make it more informative based around feedback. Let me know if you have any questions or trouble setting up DNS on Snow Leopard Server for web hosting.

Thanks for your replies. I realize I'm not making clear the way this network is configured . Also, the only services running on the Snow Leopard server are (at this time):
dhcpd - in the 10.136.31.x range;
dns - same as before;
planned to add are:
Open Directory (for network logins)
Software update;
Web (only on the 10.136.31.x Ethernet);
mySQL (localhost only - for moodle);
NAT is not set up on the Snow Leopard server itself. We have an outside router, a Cisco 2811. This router provides routing for both the public IP range, and the NAT range is configured in this router. The forwarding dns is located in LR and Fayetteville. So what I need is dns on Snow Leopard to forward outside queries to the state DNS servers, and resolve the local NAT IP only for Open Directory and a set of Snow Leopard clients.
Is this going to be possible?

RSS feed from Snow Leopard server

I want to host an RSS feed from my server. What settings would be necessary to accomplish this?

The first things to do would be to download a program that will maintain your RSS feed. Podcast spitter from the app store was the top hit when I did a search. I've not used it, but it appears that it'll do the trick.
Next, just create a website using the web service in Snow Leopard Server.
Point Podcast Spitter at the share that hosts your web site and that should do the trick.
When you upload your RSS feed, all the stuff needed to make it an RSS feed should go with it.
Granted it's a VERY thinned out version of the steps needed to take, but the concepts are correct.
If you need a more detailed description, write back with more info about how your server is set up and how it's connected to the internet.
HTH
-Graham

Snow Leopard Server - SSL Certificate Issue

Hi. I am hoping someone can shine some light into an issue I am currently experiencing with SSL Certificates on the Snow Leopard Server which hosts out websites. This past weekend an SSL certificate pertaining to our primary domain expired which caused users to receive error messages prior to accessing the website ... the error message stated "the site's security certificate has expired!"
I have since renewed the certificate via networksolutions.com and applied it on the Mac server. The certificate was applied successfully and i have added the certificate the sites along with restarting the apache to take in the settings. However, the certificate is not propagating out at all. I have also restarted the mac server as well in case there was something in the cache causing issues but unfortunately, the issue still exists.
I have also removed the certificate entirely and reapplied it from scartch to make sure the original certificate wasn't causing any issues.
Has anyone else incurred a similar issue or would anyone have any insight on how to possibly resolve the issue?
Thank you!

Just a quick update. the DNS seems fine but I am getting errors in the logs as follows.
May 12 09:37:34 server jabberd/sm[2084]: version: jabberd sm 2.1.24.1-326.5
May 12 09:37:34 server org.jabber.jabberd[2082]: ERROR: router died. Shutting down server.
May 12 09:37:34 server com.apple.launchd[1] (org.jabber.jabberd): Throttling respawn: Will start in 10 seconds
May 12 09:37:34 server jabberd/sm[2084]: attempting connection to router at 127.0.0.1, port=5347
May 12 09:37:34 server jabberd/sm[2084]: shutting down
May 12 09:38:45 server jabberd/sm[2167]: version: jabberd sm 2.1.24.1-326.5
May 12 09:38:45 server jabberd/sm[2167]: attempting connection to router at 127.0.0.1, port=5347
May 12 09:38:45 server jabberd/sm[2167]: shutting down
May 12 09:38:45 server org.jabber.jabberd[2165]: ERROR: router died. Shutting down server.
May 12 09:38:45 server com.apple.launchd[1] (org.jabber.jabberd): Throttling respawn: Will start in 10 seconds
I checked the the crash report which has the follow kernal issue.
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x000000010011adb0
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Any ideas?

Snow Leopard Server DNS setup

Where is there a step by step setup for making my Snow Leopard Server with DNS? Essentially, I am looking to setup a mail server but seem to be missing what information I need to gather from the folks that host my domain and how to point traffic to my network.

When I started setting up my first Mac OS X Servers a few years ago I had to completely retrain my brain because the MacOS does not follow the traditional nomenclature of Windows Active Directory and DNS setup. That being said like AD for Windows MacOS relies very very heavily on a healthy and properly running DNS system, both internally and externally. So one great resource I found was about 10+ hours of training on Leopard Server over to Lynda.com. I think you can sign up for a month long membership but it's well worth the investment if your looking for some basics thru advanced setup of Leopard Server. Now SLS is much much easier at the setup and deployment and some of the fundamentals of the setup interface have changed greatly (as an improvement) but the videos are still very applicable.
Basically it comes down to the following steps in order to get your website/e-mail/wiki services working.
1. Purchase your .whatever with a registrar, godaddy, doster, network solutions ect...
2. Make sure you have a fully routable PUBLIC IP address from your ISP that you can assign to the WAN (internet side of your router)
3. Contact your ISP and ask then to create an rDNS entry for your .something to the IP address they assigned you. Usually this will look like xxx.xxx.xxx ---> mail.mydomain.com when you test later on.
4. Modify the DNS records with your registrar to point the MX & A record to your new IP. You will log in create an A record for mail.mydomain.com ---> xxx.xxx.xxx (your public IP on router) and then you will create an MX record for e-mail which will simply be mail.mydomain.com with a value of 10 (there is usually a screen for this).
5. Once all the DNS is setup and working properly (Can take several days for these changes to take affect and be visible by your ISP) then you can begin the configuration of your router. You will need to determine what IP internally you want your Mac to be. Usually 10.0.0.1 or 192.168.1.1 or other and document that. Program your router to port forward ports 25,110, 80, 143 to the IP that you decided your Mac will be at so those services will be publicly available to you to user. Otherwise nobody will ever be able to send you e-mail or visit your site.
6. This is a good time to check your work and settings by visiting www.mxtoolbox.com and you verify your rDNS (setup by ISP) and your DNS (Setup by you) before beginning your setup of OS X SLS. If everything checks out then start the install if not STOP HERE and fix it because it will haunt you in the long run.
7. Start the install of SLS and at some point the system will get you to the screens at which you input your domain information. If all was setup properly up to now SLS will auto-populate the domain and local hostname of your Mac Server. U can change the local hostname if you wish but the domain name information should reflect your rDNS and A record information of mail.mydomain.com and you can hit next and proceed with the rest of the install.
8. Once up and running you will need to make a small adjustment to the alias of your e-mail. For some reason the engineers at Apple left a flaw in (my opinion) that is as such. Whenever you send e-mail it will go as [email protected] instead of what you really want which is [email protected]. So follow this post below and you will be all fixed up in a jiffy.
http://discussions.apple.com/message.jspa?messageID=10110723#10110723
Hope this helps.

How to resolve network issue or dns to access web page on snow leopard server?

I have my network setup like as follows:
internet > router 1 > ethernet ports > switch > router 2
I have a mac osx snow leopard server connected to "router 1", but it is so slow when accessing a web page hosted on the server from a browser on a workstation connected to either router 1 or router 2?
Is there a problem with my network setup or maybe because I changed the name to newservername.local?

@Jeff and @Camelot,
I think it is a DNS issue. I completely reset the DNS settings on server and the local name with the steps below, but now cannot access the site hosted on the server at all
I used a modified version of http://www.mkahn.com/2010/09/configuring-dns-on-mac-os-x-10-6-snow-leopard-serve r-for-hosting/ to reset the server set
1. Stop DNS Service in Server Admin
2. Close Server Admin
3. Obtain 10.6 DNS Default files (below)
4. Overwrite the DNS files with DNS Default files:
/etc/dns/loggingOptions.conf.apple
/etc/dns/options.conf.apple
/etc/dns/publicView.conf.apple
/var/named/named.ca/etc/named.conf
/var/named/named.local
/var/named/localhost.zone
5. Restart your server
All machines have 1ms ping responses within the network including this snow leopard server that I am trying to setup. There is another test web server that return pages instantly within this network so I doubt it is a network issue, but a DNS issue.

How do I create a virtual directory in Snow Leopard Server Admin program?

Hi, how do you use the server admin program in snow leopard server to create an apache virtual directory? I can't see it in the applet anywhere. Thank you.

Well this is what I thought too but I don't think I'm doing something right. I have a default website on port 80 and I created a second site on the same port. They are two different websites. One is the initial one that comes stock with the osx. The second one I created.
When I browse to my server I get the second site. How can I get the default to be the one that points to the mail, wiki, calendar stuff, while my second domain is something totally different.
http://myserver (should be the default stuff like mail.)
http://myserver/mysecondsite (should be my other stuff.)
The problem is that when I go to http://myserver it is going to http://myserver/mysecondsite
What am I doing wrong? Thank you.

How do I remotely access my Snow Leopard server from my Mountain Lion MacBook Air

Does anyone know of an idiot's guide to setting up a VPN to access my server? I'm running Snow Leopard server in the office and I'd like to be able to access the server, probably just from one computer (MacBook Air runnung Mountain Lion) from home.
I'm not sure if it complicates things or not, but the office is in an area with poor broadband and so the internet connection is via satellite broadband. The set up is a satellite modem into a Gigabit router and the server is connected to the router via an unmanaged switch.
As an aside, I'm considering changing this set up so that the modem plugs into a Time Capsule and the server will connect directly into the TC. The desktops will then run into the server via the unmanaged switch or wirelessly via TC - any thoughts on the best set up here? Are cables into a switch better/worse than using TC's wireless facility.
Is this something that I, as a reasonably competent computer operator but definitely not an IT expert, could do, or should I get someone in to set it up for me?
Thanks in advance
Jim

VPNs aren't particularly special or weird or secret or such. They're "just" a network connection. A sometimes very fussy network connection, but a network connection.
My preference is to use a firewall that includes an embedded VPN server. This for several reasons, as it avoids trying to forward the VPN through a device that's using NAT [1], and it means you can connect to multiple devices on the target LAN, and you can connect even if the OS X Server box is down.
Other folks will forward the VPN through NAT, and use the VPN server that's available in various versions of OS X Server.
Forwarding a VPN through NAT does work, but can also sometimes not work. NAT can cause some types of VPNs to get tossed off when (for instance) there's a second VPN connection arriving.
In various cases everything connects and works the first time, and in other cases it's trial-and-error.
With a VPN-capable firewall (which is a step above your average residential firewall), usually configuring the firewall as a L2TP server or the Cisco protocol, if you want to use the standard OS X or iOS clients. Or PPTP — which is easier to get working — but less secure. Once the firewall and the VPN server is set up — and that's where most of the "fun" is — then the set-up in Network Preferences is (usually) pretty simple.
There are thousands of OS X VPN set-up articles around, but the details all hinge on the particular VPN server, and whether you're going to try to push the VPN through (for instance) that Tome Capsule and its NAT. Until you sort out your VPN target and/or VPN client, and what sort of attacks you're securing against...
As for this case, satellite latency is large. The latency involved is the time it takes to the command or the text from your local Mac to the satellite ~35,786 kilometers up and then ~35,786 kilometers back down, and then the response back again. That's about a quarter second, each way, at the speed of light. Transferring big files is fine (once the connection is open and the transfer gets rolling), but anything interactive — such as a typical use of a VPN — is going to have a noticable lag.
Yes, it'll be easiest to get somebody to work through your requirements and expectations, and initially set this up for you. Or you can use this as an opportunity to read about and learn more about IP routing and networking and VPNs, too.
[1] VPNs seek to ensure that the network connection is secure, and from a known client IP source address to the IP address of the target VPN server. NAT explicitly obscures the network connections, and often has multiple client hosts located behind one IP address. Put another way, the VPN and NAT software implementations are working at cross-purposes.

I've got Snow Leopard Server, but don't need the server functions. What to do?

This is somewhat complicated, so please bear with me. My Mac Pro was running OS X 10.5 and required updating. But we have legacy Power PC apps (mainly FreeHand) that we want to continue using, even though Mountain Lion doesn't support them.
As a solution, I'm going to run Snow Leopard Server in emulation on Parallels 8 Desktop. I would rather have used plain old Snow Leopard instead of the server version, but Apple's EULA only allows 10.6 Server to run in emulation.
So, I got Snow Leopard Server and have used it to upgrade 10.5. Eventually, (once I get everything working properly), I'll upgrade that to Mountain Lion and use SL Server in Parallels emulation to run the old Mac apps we can't do without.
But I've run into a problem I didn't anticipate: I don't have a clue about running a server.
I'm having trouble setting it up so the other Mac user in my department can access a shared folder. Also, I want the login window to display the list of users, but that option is grayed out.
What I'd like to do is strip out all the server functions and just run as if 10.6.8 was a standard version of Snow Leopard, which I'm familiar with. If that's not practical, please explain how to get sharing to work since that's the main problem.
I've tried turning off the services listed in the Server Preferences (iCal, Mail, etc.) but that hasn't fixed the problems. I think there may be server functions running that I haven't found preventing me from fixing the problems. Or it could be something else entirely (as I said, no clue).

DON'T MAKE A MOUNTAIN (lion?) OUT OF A MOLEHILL!
Several points in response to your post, in chronological order, not necessarily in order of importance:
• It was a common Urban Myth that Snow Leopard (client's) EULA prohibited its virtualization in Lion or Mt. Lion on a Mac! That myth has been largely debunked in the last 18 months.
Here are detailed instructions on how to install Snow Leopard client into Parallels 7 or 8:
http://forums.macrumors.com/showthread.php?t=1365439
That being said, and being the author of the aforementioned thread, I STRONGLY recommend that, where possible, you use Snow Leopard Server in favor of Snow Leopard client. This will side step some later corruption problems that can arise from the improper use and shutting down of this Parallels partition.
Historically, this thread was written when Apple sold Snow Leopard Server for $499+ or ceased sales altogether. Now, Apple has rendered the (now diminishing) debate over the EULA moot, by its recent release of Snow Leopard Server to the US & Canadian community for $20; leaving those who cannot purchase SLS (or get someone to purchase it for them) to continue to follow the instructions in my thread (or asking me to purchase SLS for them and forward it to them; my preferred course of action!).
• I ALWAYS recommend that data files be stored on the real Mac's HDs and NOT in a virtualized world. This is easy to accomplish and establishes a backup regimine (Time Machine, etc.) that will protect the users data. Lost applications are easily restored from their installer discs.
• In practice I find that using SLS in Parallels 8 is the same as using SL client in Parallels. I have even removed the Server apps from the Dock so as to not be confused by them.
So, your solution is to establish a "shared folder" on the hard drive of the Mac that is hosting Parallels. When in SLS in Parallels you will have access to your shared folder, ironically through Parallels' "Shared Folders" feature that is now present in Mac OS Guest installs on version 8 (see the "Shared Folders" SERVER on the right side of the screenshot, below).
When using Freehand MX or other PowerPC apps, save your data files into your shared folder through access to it by Parallels' Shared Folders. Other users on your network will have access to the SAME data files, through their customary use of file sharing to access your shared folder from your Mac's hard drive.
IGNORE the Server applications in the Applications folder...
Freehand MX running in Snow Leopard Server installed into Parallels 8 for use in Lion or Mt. Lion:
[click on image to enlarge]
Postscript: your post was so easy to follow!

DNS Configured-Best Practice on Snow Leopard Server?

How many of you configure and run DNS on your Snow Leopard server as a best practice, even if that server is not the primary DNS server on the network, and you are not using Open Directory? Is configuring DNS a best practice if your server has a FQDN name? Does it run better?
I had an Apple engineer once tell me (this is back in the Tiger Server days) that the servers just run better when DNS is configured correctly, even if all you are doing is file sharing. Is there some truth to that?
I'd like to hear from you either way, whether you're an advocate for configuring DNS in such an environment, or if you're not.
Thanks.

Ok, local DNS services (unicast DNS) are typically straightforward to set up, very useful to have, and can be necessary for various modern network services, so I'm unsure why this is even particularly an open question. Which leads me to wonder what other factors might be under consideration here; of what I'm missing.
The Bonjour mDNS stuff is certainly very nice, too. But not everything around supports Bonjour, unfortunately.
As for being authoritative, the self-hosted out-of-the-box DNS server is authoritative for its own zone. That's how DNS works for this stuff.
And as for querying other DNS servers from that local DNS server (or, if you decide to reconfigure it and deploy and start using DNS services on your LAN), then that's how DNS servers work.
And yes, the caching of DNS responses both within the DNS clients and within the local DNS server is typical. This also means that there is need no references to ISP or other DNS servers on your LAN for frequent translations; no other caching servers and no other forwarding servers are required.

Are there any problems with Snow Leopard Server (Xserve) and PPC Clients

Hi,
are there any problems identified yet with Snow Leopard Server, installed on a Xserve and PPC Clients running Mac OS X Tiger and Leopard?
Currently I have a Xserve Intel running Leopard Server and about 12 Mac Minis PPC running Mac OS X Tiger and Mac OS X Leopard. The Xserve serves services like DNS, OpenDirectory, Software Update Server, NetBoot, etc. All users have Home Directories stored on the Xserve.
Now I want to install Snow Leoaprd Server on the Xserve, but I wonder if there are any problems using the PPC Clients? I have read something like this on a german website.
Thanks!

We've actually found that the Server 10.6.3 DVD does an amazingly smooth job of upgrading 10.5.8. We've been upgrading our production servers and nothing has gone wrong yet. Snow Leopard employs an archive and install method of upgrading which results in an install which is very close to a clean install. So it's been very convenient for us because our servers are used as Windows PDCs and it's a pain in the *** to have to re-join all PCs to the domain if we start from scratch.

Creating a versatile DNS and redirection service on Snow Leopard Server

For the few of us who use Snow Leopard Server as a main DNS for our small network, the following is a workflow that I would like to share with the board for creating redirection services to not just sites found on the locally hosted apache but also external sites.
+IF you are adding a second domain name, the reverse domain lookup will not appear and you will need to add a Machine/A record with the fully qualified domain "domainname.com." (don't forget the . at the end) into the new zone and it will point to the "server" Machine/A record ip address.+
*DNS Portion* : (ServerAdmin > DNS > Zones >
Add Zone > Primary > Create a fully Qualified Domain name and dns "server" in the Machine / A Record
Create the (add Record > Alias/ CNAME) subdomain pointing to the server.domainname.com e.g. (library)
*Web / Apache Portion :*
Create a new site (ServerAdmin > Web > Sites > Plus button)
With General > host name exactly as spelled in above subdomain in full (library.domainname.com)
Select Web Folder where the site is hosted
If you are creating a redirection, create a folder on the server, add an index.php (with the script below)
Add Alias with the same subdomain as number 2
_PHP script :_
<?php
$location = "http://example.net";
header("Location: ".$location, "301 Moved Permanently");
?>
// Edit the "http://example.net" to which ever e.g. "http://apple.com"
_Alternatively you can also mask the page with :_
<html>
<head>
<title>Same Title As Your Homepage</title>
<script type="text/javascript">
function changeTitle()
if (top.frames['main'].document.title)
top.document.title=top.frames['main'].document.title;
</script>
</head>
<frameset>
<frame name="main" src="http://actual-url.anotherhost.com/page.html"scrolling="auto" target="main" ONLOAD="changeTitle();">
<noframes>
<body>
Place a suitable message here for people with browsers that can't read frames.
</body>
</noframes>
</frameset>
</html>

Ok, local DNS services (unicast DNS) are typically straightforward to set up, very useful to have, and can be necessary for various modern network services, so I'm unsure why this is even particularly an open question. Which leads me to wonder what other factors might be under consideration here; of what I'm missing.
The Bonjour mDNS stuff is certainly very nice, too. But not everything around supports Bonjour, unfortunately.
As for being authoritative, the self-hosted out-of-the-box DNS server is authoritative for its own zone. That's how DNS works for this stuff.
And as for querying other DNS servers from that local DNS server (or, if you decide to reconfigure it and deploy and start using DNS services on your LAN), then that's how DNS servers work.
And yes, the caching of DNS responses both within the DNS clients and within the local DNS server is typical. This also means that there is need no references to ISP or other DNS servers on your LAN for frequent translations; no other caching servers and no other forwarding servers are required.

Snow Leopard Server fails when I restart my Mac Pro

I have a new Mac Pro that I've been running Snow Leopard Server on. When I restarted my computer it wouldn't boot up. It would only get to the screen with the apple symbol and the spinning dial under it. I had to totally reset up the computer and server software. 2 weeks later the same thing happened and I had to reset it all up again! A week later the same thing happened so I just gave up and installed Snow Leopard. I was using the computer as a "regular computer" meaning I had all my music, photos, other apps.... but nothing was installed or changed the day and the day before it failed. I didn't even have time to set up web hosting and all that crap. I was just browsing the web using Safari.
And yes everything was up to date.
I would love to go back to Server but I'm not going through all that crap again!!
Any ideas for what the problem could be would be great!
one last thing. Finder froze the last time which is why I had to restart; if that helps anyone.
but please leave a message even if you think it wouldn't affect it.

I would suspect your jumpers settings are wrong. These are cable select...try that not slave/master

Hosting IPv6 Website on Snow Leopard Server

Similar Messages

Maybe you are looking for