Ping Commands!

This comes from: http://www.computerhope.com/pinghlp.htm

ping

[-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS]
[-r count] [-s count] [[-j host-list] | [-k host-list]]
[-w timeout] destination-list

Options

-t - Pings the specified host until stopped.

To see statistics and continue - type Control-Break;
To stop - type Control-C.

-a - Resolve addresses to hostnames.
-n - countNumber of echo requests to send.
-l - sizeSend buffer size.
-f - Set Don't Fragment flag in packet.
-i TTL Time To Live.
-v TOS - Type Of Service.
-r count - Record route for count hops
-s count - Timestamp for count hops.
-j host-list - Loose source route along host-list.
-k host-list - Strict source route along host-list.
-w timeout - Timeout in milliseconds to wait for each reply.

Examples

ping localhost

Pings the local host, this will allow you to see if the computer is able to send information out and receive the information back. Note that this does not send information over a network but may allow you to see if the card is being seen.

ping xxx.xxx.xxx.xxx

Allows you to ping another computer where the x's are located are where you would place the IP address of the computer you are attempting to ping. If this is not able to complete this should relay back an unsuccessful message which could be an indication of cable issues, network card issues, hub issue, etc.

ping computerhope.com

PING computerhope.com (204.228.150.3) 56(84) bytes of data.
64 bytes from www.computerhope.com (204.228.150.3): icmp_seq=1 ttl=63 time=0.267 ms

--- computerhope.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.267/0.267/0.267/0.000 ms

Adding users to Project Server PWA site

To grant users access to the PS PWA site they need to be added via the Server Settings / Manage Users page in the PWA site. Simply adding them through Site Settings / Advanced Permissions will not work.

Installing Project Server 2007 on an existing MOSS farm with Kerberos enabled

I have a medium server farm running MOSS 2007. There are three servers (2 WFE, 1 Index & 1 SQL).

Note - Project Server cannot be uninstalled from a joint MOSS / PS installation

To install Project Server 2007:

1. Copy Project Server installer on to each server - i put them in C:\Temp
2. Quiesce the MOSS farm via Central Administration / Operations
3. Run the PS install files on each server in the farm
4. Unquiesce the farm
   
5. Run the MOSS configuration wizard on each server one by one

Start the Project Server Service:

1. Open Central Administration and select the Operations tab
2. Select Services on Server
3. Select the server you want to run the Project Server service
4. If the Project Server Service is not dispayed change the server role to Custom
   
   
   
   
5. Start the Project Server service

Provision the Project Server site:

1. Open Central Administration and navigate to Shared Services Administration
2. Open the SSP that on to which you want to provsion Project Web Access (PWA)
   
   
   
   
3. On the SSP homepage select Project Web Access Sites
4. Select Create Project Web Access Site
   
   
   
   
5. Select the MOSS web application to host the PWA
6. Assign a PWA path for example: projectserver
7. Assign the Administrator Account for the PS instance
8. Assign the primary database SQL server
9. Name the four PS databases
10. Click OK
11. When provisioning is complete Provisioned will appear in the status column - to refresh the status click Refresh Status
    
    
    
    
12. To enable access you must ensure that you have registered the server SPNs for Kerberos delegation and for the web application process accounts. Until you do this you will get an access denied error when you try to access the PWA site.
    
    

A theme with the name "CustomMySite 1011" and version already exists on the server.

You receive this error when trying to apply a custom theme to your SharePoint site:

"A theme with the name "CustomMySite 1011" and version already exists on the server. "

1. Open your site in SharePoint Designer.
2. Expand _themes and delete the CustomMySite theme folder
3. Re-apply the custom theme to your site.
   

Enabling MOSS Anonymous Access

1. From Central Administration > Application Management > Application Security > Authentication Providers, select a Web application and the zone you want to modify. This is usually default.

2. In the middle of the page, check Enable Anonymous Access and choose Save

3. All site collections in that Web application can now have anonymous access enabled.

4. Go to a site collection in the Web application you just enabled anonymous access for

5. From Site Actions > Site Settings, open Advanced Permissions

6. From the Settings drop-down menu, select Anonymous Access

7. For this example, enable anonymous access for Lists and Libraries and click OK

8. Browse to any document library in this site collection

9. From the Settings drop-down menu, select Document Library Settings

10. In the Permissions and Management column, select Permissions for this document library

11. From the Actions menu, select Edit Permissions to break inheritance

12. From the newly appeared Settings drop-down menu, select Anonymous Access

13. Check View Items and click OK.