If you’re a Mac Poweruser and not already familiar with macports, this is great package I would highly recommend, especially if you’re a bit of a *nix terminal junkie.
Download and installation is a breeze. Click on the link for the dmg relative to your distro and it’s smooth sailing.
Once it’s installed however, you may run into a bit of a problem if you’re behind a corporate firewall.
sudo port -v selfupdate [MacPorts] #21034: Warning: No index(es) found! Have you synced your source indexes?
This message is followed by what may seem to be gibberish, but is actually informative logging telling you that rsync is being blocked.
I found numerous blogs and articles with no resolution to this issue, including one of the references below. Never fear! The solution is simple, and even outlined in the macports site.
First, make sure you are a sudo or root user, or you won’t have access to change the files necessary. (I outlined this in this article on my site).
After install make sure you close and reopen any terminal windows you have running.
1) Navigate to /opt/local/etc/macports.
2) sudo vi sources.conf
3) arrow down to the bottom line, bottom left corner, press “i” for insert then “#” key on your keyboard.
4) arrow to the end of the link and press return key on the keyboard
5) enter alternative url for macports tarball (without the quotes) “http://www.macports.org/files/ports.tar.gz [default]”
6) hit esc key on keyboard, then shift+: (colon) and finally “wq” which should exit you from vi and save changes
Voila! That’s it. You should now be able to update successfully. Note down any other errors you may encounter and happy porting. 8)
macports install, http://www.macports.org/install.php
macports alternative tarball sync, https://trac.macports.org/wiki/howto/PortTreeTarball
macports configuration files guide, http://guide.macports.org/chunked/internals.configuration-files.html
macports general howto, https://trac.macports.org/wiki/howto
Old Nabble Post with some similar user issues, http://old.nabble.com/-MacPorts—21034%3A-Warning%3A-No-index(es)-found!-Have-you-synced-your-source-indexes–td25264855.html
Changing default port of Microsoft SQL Server differs depending on the version. The following is for the latest version of MSSQL only.
If you’re using 2005, the steps are similar to those below, but the area you need to go is the SQL surface area configuration instead.
If you’re using 2000, it’s time to upgrade. 2000 is pretty out of date. We’ll probably be looking at something newer than SQL 2008 before long.
1) Goto: SQL Server Configuration Manager > SQL Server Services > (right click on your server instance) > Stop
2) Goto: SQL Server Configuration Manager > SQL Server Network Configuration > Protocols for [Instance Name] > Right click TCP/IP (make sure it’s enabled) > IP Addresses Tab
3) Once you’re at this tab find the IP that corresponds to the address of your network adapter that is connected to the router (IP1 in my case though on servers this could easily be variable).
4) Remove 0 from “TCP Dynamic Ports” and set the “TCP Port” field to the number you want (default is 1433). If you scroll to the bottom you will also note there is an “IPAll” which I also did the same for.
5) Change any firewall rules that may block the connection (add a new port in Windows firewall).
6) Restart service instance. (step 1)
Some blogs and articles I came across mention starting the SQL Server Browser, however, I would like to mention that although you should have this service running for a couple reasons, the above configuration works without the browser and doesn’t technically need it to connect remotely if you know exactly which port you’re connecting to.
To connect remotely on different port make sure TCP/IP is enabled for the server instance in configuration manager, and in management studio or your application connection string specify:
Note that a different port number is specified using a comma, not a : like you may have expected.
Microsoft KB, http://support.microsoft.com/kb/914277
As a general word of caution, if you have no experience with Cisco or other CLI based router admin (such as linux and red hat derivatives), I would not recommend diving in unless you have a lot of spare time on your hands in the event that you accidentally delete all routing tables or cause other serious problems!
Even in a professional business environment, due to some differences between IOS and hardware versions and the need to reboot for some settings to take effect, it’s always a good idea to perform changes after hours when critical business operations will not be interrupted by internet or service downtime.
Official Cisco IOS Manual, http://www.cisco.com/en/US/docs/ios/12_3/featlist/sec_vcg.html
Manipulate NAT and other general help references and top hits on Google for common Cisco beginner questions: