Installing & Configuring SharePoint Server 2007

In this post, I'll demonstrate with words and screen shots how to install and get working a portal using Microsoft Office SharePoint Server 2007. Installing this product is not difficult, but it does require some forethought and planning. You can use this post as a reference for getting your version of MOSS 2007 installed.

First, you'll need Windows 2003 Server, fully patched and ready to go. I believe I've seen blog postings recently that indicate that you can install MOSS07 on a Vista server. I'll leave that discussion for other threads and posts.

Once you have the operating system ready to go, you'll want to start by running the setup.exe for MOSS 2007. Figure 1 illustrates that after you start the installation process, you'll need to enter a valid product identification key code. This key code can be found on the download site and should have been a part of what you did to get the software in the first place.

Figure 1: Product Identification Key Code Input Screen

After entering the product identification key code, click Continue. The next screen is the licensing agreement screen. Now, I always recommend that you read the licensing agreement since it is a legal document and you are bound by its' terms. But I also recognize that in the 10+ years I've been in this industry, I've never seen an agreement that I didn't agree with.............if you get my drift.

Figure 2: Licensing Agreement Screen.

Be sure to select the "I accept the terms of this agreement" check box and then click Continue.

The next screen will give you the chance to select which type of installation you wish to commit. The Basic installation is used for those who:

• Need to install everything on a single server

• Do not need to grow into a multi-server farm

• Need a quick, easy deployment during installation with lead administrative effort

The Advanced option is selected by those who wish to install MOSS 2007 selecting some of the customizable features. In this illustration, we'll select the Advanced option and follow that route.

Figure 3: Installation Type Selection Screen

After clicking on the Advanced button, you'll find that the selections default to StandAlone (Figure 4). However, we'll choose Complete. The meaning of the three options is as follows:

• Complete: Enables all of the options for one server to offer the entire range of MOSS 2007 services and features to the network. You can scale out this deployment, start and stop services on this server and use a SQL server to host your databases.

• Web Front End: Enables only those options that allows the server to run as a web front end server. What this means is that server is merely the entry and exit point (or one of them among the other WFE servers) for the farm. The actual servers that users will consume will be hosted on other servers (presumably). This cannot be the first choice of a farm unless you plan on installing other servers in the farm to offer the services and features that users will want to consume.

• Stand-Alone: Similar to complete, this option enables all of the services and features for the MOSS 2007 farm, but assumes that there is no SQL server, so the MSDE engine is installed locally on this server. You cannot scale out this server into a larger MOSS 2007 farm.

Note that in reality, all of the MOSS 2007 binaries are installed in all three choices. All these choices really do is (pragmatically, not technically) turn on and off the code that is required for the server to fulfill the functions that have been assigned to it. Note also that you can select the location where the binaries should be installed in the File Location tab and then sign up to give feedback directly to Microsoft if you'd like to do this.

Make your selections, then click Install Now.

Figure 4: Server Type Selection Screen

During the installation, you'll be presented with a status bar that is illustrated in Figure 5.

Figure 5: Installation Status Screen

After installation has completed, you'll be given the chance to run through the SharePoint Products and Technologies Configuration Wizard (Figure 6). You'll use this wizard to commit the initial configuration options for your new SharePoint farm.

Figure 6: Entry screen to the SPPT Configuration Wizard. Note that you can come back to this screen using the Administration menus that automatically install with the SharePoint Server binaries

One you start the SPPT wizard, you'll receive a pop-up box (Figure 7) that will inform you that certain services are going to be stopped. Be sure it is a good time to stop these services before moving on with the configuration options for your farm.

Figure 7: Informational Pop-Up Box

The following set of screens in the SPPT Configuration Wizard are design to help you setup the farm. In Figure 8, you'll be able to create a new farm or join and existing farm. Farm membership, at the server level, is determined by which servers are using the same configuration database in SQL and which servers are not. In my illustration, I want to create a new farm, so I select the "No, I want to create a new server farm" radio button. If I had wanted to connect to an existing farm, I would have selected the other radio button.

Figure 8: Connect to a server farm configuration screen in the SPPT Wizard

After making our selection in Figure 8 and then clicking Next, I'm taken to the next screen illustrated in Figure 9. On this screen, I can enter the following configuration values:

• The SQL database server name. I'm not clear if this is the host name or netbios name, but I suspect this is the host name. However, you don't need the FQDN here, but you do need name resolution to this server or SQL Instance.

• The farm configuration database name is needed in the next input box. Note that the screen just asks for a name, but you need to understand you're entering the most persistent database name for the entire farm - the farm configuration database name. Be sure this name supports your database naming convention. You should decide the name of this database in advance of getting to this screen

• The database access account will need to be a member of the local admins group on each SharePoint server along with having db_creator and db_security permissions in SQL. I would suggest you have an account setup just for this purpose in your Active Directory and that you have a strong password associated with this account.

Figure 9: Configuration Database Settings Screen in the SPPT Wizard

in Figure 10, you'll be asked to decide which type of security settings you want to use for your farm. First, you can specify a pre-selected port number for central administration to run on or you can allow the wizard to randomly assign a port number. As you can see, this instance of the wizard randomly selected 17386 as the port number for Central Administration (CA). If you want CA to run on a different port, then select the check box and enter the desired port number.

The issue of NTLM vs. Kerberos is one that you may at some point wish to consider. Do you want the CA application to run using NTLM (NT Lan Manager) for security authentication or Kerberos? If the latter, there are some special configurations you'll need to complete for your Active Directory (AD) before Kerberos will work. I'm finding that most administrators are happy with NTLM, though those in a larger and more secure implementations are increasingly using Kerberos. For purposes of my illustration here, I'm selecting NTLM.

Figure 10: Configure SharePoint Web Application configuration screen in SPPT Wizard

After you click Next, you'll be given a status bar that indicates how the SharePoint configuration is going. Depending on the type of server you're installing and the options you're installing, you could have as few as seven tasks or as many as eleven. Figure 11 illustrates the progress screen. Note that the caption below the status bar will inform you about the configuration actions that are being executed during this process.

Figure 11: Configuration status bar screen in the SPPT Wizard

After the configurations have been executed and committed to the SQL Server database, we finally get to CA where we can further configure our farm. We can start and stop services (Figure 12) on this server and then create web applications. In order to have portal, you'll first need to start the Office SharePoint Server Search service and then create a Shared Services Provider (SSP). I'll start the search service.

Figure 12: Services configuration screen in CA

When the search service is started, you're presented with another web page for search configuration administration that needs to be completed before the search service can start. The configuration options are pretty clear. Out of the shoot, you'll use this server for both indexing and servicing queries from users until you can get enough servers in your farm to quarantine those options in your farm. Select a location that has enough disk space for your indexes. You should plan on a space allotment of 20% relative to the amount of information you wish to index. You'll also need to input an email address, a service account and whether or not there is a dedicated WFE for all crawling activities. For now, in my illustration, since this is the first server in the farm, I'll accept the defaults and click OK.

Figure 13: Search configuration screen

After starting the search service, the next thing I need to do is create a SSP. In order to do this, I'll navigate to the Application tab in CA, click Create or Extend a Web Application, then click Create a New Web Application, then make the configurations necessary that you see in Figure 14. Most of this is pretty self-explanatory, so I won't go through each input in detail. Suffice to say that I've done two things not illustrated here. First, after creating this web application, I then web back into CA, selected the Create or Configure Core Farm Services, then selected New SSP (Figure 15) and then filled in the configuration information for the new SSP. All of the options on that page are self-explanatory, except that you must select an Index server for the SSP to operate.

Backtracking just a bit, you can't have an Index server unless the Search services is started. So, that's why I illustrated starting the search services first, then creating an SSP, then creating a portal.

Figure 14: Configuring the new web application to host the portal

Figure 15: Illustration of the SSP management interface where you can select to create a New SSP.

Once the SSP is created and the web application for the portal has been created, you can then create the portal. The way to do this is to navigate to CA and then click Create Site Collection. Be sure the http://portal is selected in the drop down list in the upper right-hand portion of the screen (Figure 16). Note that on this screen, you'll need to ensure that you are creating the site collection at the root by selecting the "Create Site at this URL" where the URL path is "root", not in the Sites managed path. Also, if you scroll down, you'll need to select the Corporate Intranet Site under the Publishing tab. Microsoft has renamed the Portal to Corporate Intranet Site and placed it under the Publishing tab for web content publishing purposes. BTW, even though I don't illustrate it here, be sure to give the site a title.

Figure 16: Create Site Collection Screen

At this point, you should now have a new portal, ready to aggregate, organize and present content for your enterprise, division or department.

SOURCE : www.mindsharpblogs.com

How can I transfer some or all of the FSMO Roles from one DC to another?

Windows 2000/2003 Active Directory domains utilize a Single Operation Master method called FSMO (Flexible Single Master Operation), as described in Understanding FSMO Roles in Active Directory

In most cases an administrator can keep the FSMO role holders (all 5 of them) in the same spot (or actually, on the same DC) as has been configured by the Active Directory installation process. However, there are scenarios where an administrator would want to move one or more of the FSMO roles from the default holder DC to a different DC.

Moving the FSMO roles while both the original FSMO role holder and the future FSMO role holder are online and operational is called Transferring, and is described in this article.

The transfer of an FSMO role is the suggested form of moving a FSMO role between domain controllers and can be initiated by the administrator or by demoting a domain controller. However, the transfer process is not initiated automatically by the operating system, for example a server in a shut-down state. FSMO roles are not automatically relocated during the shutdown process - this must be considered when shutting down a domain controller that has an FSMO role for maintenance, for example.

In a graceful transfer of an FSMO role between two domain controllers, a synchronization of the data that is maintained by the FSMO role owner to the server receiving the FSMO role is performed prior to transferring the role to ensure that any changes have been recorded before the role change.

However, when the original FSMO role holder went offline or became non operational for a long period of time, the administrator might consider moving the FSMO role from the original, non-operational holder, to a different DC. The process of moving the FSMO role from a non-operational role holder to a different DC is called Seizing, and is described in the Seizing FSMO Roles article.

You can transfer FSMO roles by using the Ntdsutil.exe command-line utility or by using an MMC snap-in tool. Depending on the FSMO role that you want to transfer, you can use one of the following three MMC snap-in tools:

• Active Directory Schema snap-in
• Active Directory Domains and Trusts snap-in
• Active Directory Users and Computers snap-in

To transfer the FSMO role the administrator must be a member of the following group:

FSMO Role	Administrator must be a member of
Schema	Schema Admins
Domain Naming	Enterprise Admins
RID	Domain Admins
PDC Emulator
Infrastructure

Transferring the RID Master, PDC Emulator, and Infrastructure Masters via GUI

To Transfer the Domain-Specific RID Master, PDC Emulator, and Infrastructure Master FSMO Roles:

1. Open the Active Directory Users and Computers snap-in from the Administrative Tools folder.
2. If you are NOT logged onto the target domain controller, in the snap-in, right-click the icon next to Active Directory Users and Computers and press Connect to Domain Controller.
3. Select the domain controller that will be the new role holder, the target, and press OK.
4. Right-click the Active Directory Users and Computers icon again and press Operation Masters.
5. Select the appropriate tab for the role you wish to transfer and press the Change button.
6. Press OK to confirm the change.
7. Press OK all the way out.

Transferring the Domain Naming Master via GUI

To Transfer the Domain Naming Master Role:

1. Open the Active Directory Domains and Trusts snap-in from the Administrative Tools folder.
2. If you are NOT logged onto the target domain controller, in the snap-in, right-click the icon next to Active Directory Domains and Trusts and press Connect to Domain Controller.
3. Select the domain controller that will be the new role holder and press OK.
4. Right-click the Active Directory Domains and Trusts icon again and press Operation Masters.
5. Press the Change button.
6. Press OK to confirm the change.
7. Press OK all the way out.

Transferring the Schema Master via GUI

To Transfer the Schema Master Role:

1. Register the Schmmgmt.dll library by pressing Start > RUN and typing:

regsvr32 schmmgmt.dll

1. Press OK. You should receive a success confirmation.
2. From the Run command open an MMC Console by typing MMC.
3. On the Console menu, press Add/Remove Snap-in.
4. Press Add. Select Active Directory Schema.
5. Press Add and press Close. Press OK.
6. If you are NOT logged onto the target domain controller, in the snap-in, right-click the Active Directory Schema icon in the Console Root and press Change Domain Controller.
7. Press Specify .... and type the name of the new role holder. Press OK.
8. Right-click right-click the Active Directory Schema icon again and press Operation Masters.
9. Press the Change button.
10. Press OK all the way out.

Transferring the FSMO Roles via Ntdsutil

To transfer the FSMO roles from the Ntdsutil command:

Caution: Using the Ntdsutil utility incorrectly may result in partial or complete loss of Active Directory functionality.

1. On any domain controller, click Start, click Run, type Ntdsutil in the Open box, and then click OK.

Microsoft Windows [Version 5.2.3790] (C) Copyright 1985-2003 Microsoft Corp.  C:\WINDOWS>ntdsutil ntdsutil:

1. Type roles, and then press ENTER.

ntdsutil: roles fsmo maintenance:

Note: To see a list of available commands at any of the prompts in the Ntdsutil tool, type ?, and then press ENTER.

1. Type connections, and then press ENTER.

fsmo maintenance: connections server connections:

1. Type connect to server , where is the name of the server you want to use, and then press ENTER.

server connections: connect to server server100 Binding to server100 ... Connected to server100 using credentials of locally logged on user. server connections:

1. At the server connections: prompt, type q, and then press ENTER again.

server connections: q fsmo maintenance:

1. Type transfer . where is the role you want to transfer.

For example, to transfer the RID Master role, you would type transfer rid master:

Options are:

Transfer domain naming master Transfer infrastructure master Transfer PDC Transfer RID master Transfer schema master

1. You will receive a warning window asking if you want to perform the transfer. Click on Yes.
2. After you transfer the roles, type q and press ENTER until you quit Ntdsutil.exe.
3. Restart the server and make sure you update your backup.

What is FSMO Roles?(Flexible Single Master Operations)

There are times when you may need to change the Domain Controller which holds one of the 5 FSMO roles. Either you could be facing a disaster recovery, where you have lost the first Windows 2003 Domain Controller, or you are organized and want to get the most out of your Active Directory Forest. Although you rarely need to deal with Microsoft's FSMO, there is the feeling that knowledge of these Operation Masters gives you power over your Windows 2003 Servers.

Background of Operations Masters

For most Active Directory operations, Windows 2003 uses the multiple master model. The benefit is you can add a computer, or change a user's password on any domain controller. For example, if you have three domain controllers, you can physically create a new computer account in the NTDS.dit database on any of the three. Within five minutes (15 seconds in Windows 2003), the new computer object will be replicated to the other two domain controllers.

Technically, the Microsoft multiple master model uses a change notification mechanism. Occasionally problems arise if two administrators perform duplicate operations before the next replication cycle. For example, you created an OU called Accounts last week, today at the same instant you create new users in that OU, another administrator on another DC, deletes that OU. Active Directory does it's best to obey both administrators. It deletes the OU and creates the Users, but as it cannot create the Users in the OU because it was deleted, the result is the users are added to the orphaned objects in the 'LostAndFound' folder. You can troubleshoot what has happed by locating the 'LostAndFound' folder in Active Directory Users and Computers.

From the View Menu in Active Directory Users and Computer,
click: Advanced Features.

It was worth investigating how Active Directory handles orphaned objects because the point of FSMO is that a few operations are so critical that only one domain controller can carry out that process. Imagine what would happen if two administrators tried to make different changes to the same schema object - chaos. That is why administrators can only change the schema on one Domain Controller. Emulating a PDC is the most famous example of such a Single Master Operation; creating a new child domain would be another example.

The Five FSMO Roles

There are just five operations where the usual multiple master model breaks down, and the Active Directory task must only be carried out on one Domain Controller. FSMO roles:

1. PDC Emulator - Most famous for backwards compatibility with NT 4.0 BDC's. However, there are two other FSMO roles which operate even in Windows 2003 Native Domains, synchronizing the W32Time service and creating group policies. I admit that it is confusing that these two jobs have little to do with PDCs and BDCs.

2. RID Master - Each object must have a globally unique number (GUID). The RID master makes sure each domain controller issues unique numbers when you create objects such as users or computers. For example DC one is given RIDs 1-4999 and DC two is given RIDs 5000 - 9999.

3. Infrastructure Master - Responsible for checking objects in other other domains. Universal group membership is the most important example. To me, it seems as though the operating system is paranoid that, a) You are a member of a Universal Group in another domain and b) that group has been assigned Deny permissions. So if the Infrastructure master could not check your Universal Groups there could be a security breach.

4. Domain Naming Master - Ensures that each child domain has a unique name. How often do child domains get added to the forest? Not very often I suggest, so the fact that this is a FSMO does not impact on normal domain activity. My point is it's worth the price to confine joining and leaving the domain operations to one machine, and save the tiny risk of getting duplicate names or orphaned domains.

5. Schema Master - Operations that involve expanding user properties e.g. Exchange 2003 / forestprep which adds mailbox properties to users. Rather like the Domain naming master, changing the schema is a rare event. However if you have a team of Schema Administrators all experimenting with object properties, you would not want there to be a mistake which crippled your forest. So its a case of Microsoft know best, the Schema Master should be a Single Master Operation and thus a FSMO role.

How many FSMO Domain controllers in your Forest?

Three of the FSMO roles (1. 2. and 3.) are held in each domain, whilst two (4. 5.) are unique to the entire forest. Thus, if you have three domains there will be 3 PDC emulators, but only 1 Schema Master.

Checking which DC holds which FSMO role

RID, PDC, Infrastructure (1. 2. and 3.)

You can discover which server holds the Operation Master by opening Active Directory Users and Computers, Right click your Domain and select Properties, Operations Masters.

Domain Naming Master (4.)

To see the Domain Naming Master (4.), navigate to the little used, Active Directory Domains and Trusts, Right click your Domain and select Properties, Operations Masters.

Schema Master (5.)

The Schema Master (5.) is the most difficult FSMO to find. The reason is the Schema snap-in is hidden by default. Perhaps is this is Microsoft saying - don't mess with the object definitions. However, you can reveal the Schema and its FSMO settings thus:

1) Register the Schema Snap with this command, RUN regsvr32 schmmgmt.dll

2) Run MMC, File menu, Add\Remove Snap-in, click the Add button and select,
Active Directory Schema

3) Select Active Directory Schema, Right Click, Operations Master.

Assigning Multiple IP Address in Vista/XP/2000/2003

There are several ways to set up multiple IP addresses on a Computer

1. To have multiple network interface cards (NICs) on your computer and to assign a different IP address to each card.

2. To assign multiple IP addresses to a single NIC.

3. To combine 2 previous options: have multiple NICs with multiple IPs assigned to one or more of them.

By default, each network interface card (NIC) has its own unique IP address. However, you can assign multiple IP addresses to a single NIC.

How to assign multiple IP addresses to the same NIC

If you want to assign more than one IP address to a network card on Windows 2000/XP/Vista/2003, follow the steps below.

In Windows 2000

Right-click on My Network Places, choose Properties.

Right-click on the Local Area Connection, choose Properties.

In Windows XP

Right-click on My Network Places, choose Properties.

Right-click on the Local Area Connection, choose Properties.

In Vista

Click Start and click Control Panel.

Select Network and Internet, then Network and Sharing Center, and click Manage network connections from the list of tasks.

Right click your local area connection and click Properties.

In Windows 2003

Right-click on My Network Places, choose Properties.

Right-click on the Local Area Connection, choose Properties.

Highlight Internet Protocol (TCP/IP), click Properties.

If you use DHCP, you should disable it: click Use the following IP address and enter IP address, Subnet mask and Default ateway.Click Advanced… at the bottom.

Enter additional IP addresses: click the Add… button and enter a new IP address and Subnet mask.Repeat the procedure if there are additional IP Addresses to be added.

Click Add under “Default Gateways” and add the gateway addresses.I have entered My gateway address

Click OK 3 times to save the changes.

Test your IP Addresses

Open the command prompt (Start>Run>cmd) run the ipconfig command you can see multiple ip addresses on single network card

Exchange Server 2003

Exchange Server 2003 may be run on the Windows 2000 Server if the fourth service pack has already been installed. It may also be run on 32 bit Windows Server 2003. There is a new disaster recovery feature that is even better than before. It allows the server to experience less downtime. The Exchange Server 2003 received some features form Microsoft Mobile Information server as well. These include Outlook Mobile Access as well as ActiveSync. Improved versions of anti-spam and anti-virus were also included. Management tools for mailboxes and messages have been improved and Instant Messaging and Exchange Conferencing Server are now separate products. There are two versions available of Exchange Server 2003. These include the Enterprise edition and the Standard edition. There are many other features that are available on Exchange Server 2003.

Exchange Server 2007

When Exchange Server 2003 was released there were no immediate plans as to what would happen to the product. A 2005 edition was dropped and it was not until the end of 2006 that the new version was released. Some of the new features included integration of voicemail, improved filtering, Web service support, and Outlook Web Access interface. The new edition was run on a 64 bit x 64 version of Windows Server. This increases the performance significantly. There are quite a few improvements to Exchange Server 2007. These include better calendaring, improved web access, unified messages, and better mobility. From a system protection standpoint there is more clustering, antivirus, anti spam, and compliance included. The IT experience is improved overall with a 64-bit performance. Deployment is better; routing is simplified as well as the command line shell and GUI.

There have been many changes and improvements to the Exchange Server 2007 and it is better than ever. There are no definite plans as to what Microsoft has in store for Exchange Server but the next version will certainly be better than ever.

What is the Difference between Exchange 2003 and 2007?

Exchange 2003 and 2007 difference

· 2003 is 32 bit
· Single server base, No roles base
· Outlook Mobile Access (or OMA)
· Active sync
· Up-To-Date Notifications

Exchange 2003 with SP2

· Direct Push
· Global Address List lookup
· Mobile Admin

2007 exchange server Enhanced and Newly added features

· Has Power full command line Power shell for configuration
· Most of configuration is done through power shell
· Fast message retrieval
· Follow-up flags
· Meeting attendee information
· Enhanced Exchange Search
· Windows Share Point and file share document access
· Reset PIN/Password
· Enhanced PPC security
· Autodiscover for over the air (OTA) provisioning
· Out of Office
· Support for HTML messages

Missing/ Removed features in 2007 RTM due to stability Issue but available in SP1

· Information Rights Management (IRM)
· Support for S/MIME

Completely Removed Feature

· Outlook Mobile Access (OMA)

Exchange 2007 has Role base Infrastructure. These are:

Mailbox Role

· Stores Mailboxes and Public folder
. Client Access Client request for mail are fetched by this Role
· Browser-based clients using either the full-featured Outlook Web Access (OWA) or a new OWA Light client
· Mobile devices via Exchange ActiveSync (EAS)
· Phone devices via Outlook by Phone
· POP3 or IMAP4 clients, such as Outlook Express and Eudora

Hub Transport
Responsible for all internal mail flow

Inbound mail are accepted by Edge Transport and passed on to Mailbox server and all outbound mail is relayed from the Hub Transport to the Edge Transport and out to the Internet.

Edge transport

Edge Transport server handles all Internet-facing mail flow, which provides Simple Mail Transfer Protocol (SMTP) relay and smart host services for the Exchange organization.

Unified Messaging

Unified Messaging combines email, voicemail and fax into the Exchange Server databases, and makes this data available to mailbox users via both telephone and computer.

Exchange 2007 System Requirements

PROCESSER

· x64 architecture-based computer with Intel processor that supports Intel 64 architecture
· AMD processor that supports the AMD64 platform
· Intel Itanium IA64 processors not supported
· Intel Pentium or compatible 800-megahertz (MHz) or faster 32-bit processor (for testing and training purposes only; not supported in production)

Memory

· Minimum: 2 gigabytes (GB) of RAM for Single Roles
· 5 GB of RAM. if Roles are installed on single server.
· 8 megabytes (MB) of RAM per mailbox
· Minimum based on number of storage groups

Disk space

· At least 2.5 GB on the drive on which you install Exchange
· An additional 500 MB of available disk space for each Unified Messaging (UM) language pack that you plan to install
· 200 MB of available disk space on the system drive
· In Exchange 2007 RTM, a hard disk drive that stores the message queue database on an Edge Transport server or Hub Transport server with at least 4 GB of free space
· In Exchange 2007 SP1, a hard disk drive that stores the message queue database on an Edge Transport server or Hub Transport server with at least 500 MB of free space
· Disk partitions formatted as NTFS file systems.

Upgrade Tip

· It is not supported to upgrade Exchange 2007 RTM to Exchange 2007 SP1, and then upgrade your operating system to Windows Server 2008.
· Complete Fresh Installation of Ex-2007-SP1 on 2008 is supported

Protocol Numbers

• 0 HOPOPT IPv6 Hop-by-Hop Option
• 1 ICMP Internet Control Message
• 2 IGMP Internet Group Management
• 3 GGP Gateway-to-Gateway
• 4 IP IP in IP (encapsulation)
• 5 ST Stream
• 6 TCP Transmission Control
• 7 CBT CBT
• 8 EGP Exterior Gateway Protocol
• 9 IGP any private interior gateway (used by Cisco for their IGRP)
• 10 BBN-RCC-MON BBN RCC Monitoring
• 11 NVP-II Network Voice Protocol
• 12 PUP PUP
• 13 ARGUS ARGUS
• 14 EMCON EMCON
• 15 XNET Cross Net Debugger
• 16 CHAOS Chaos
• 17 UDP User Datagram
• 18 MUX Multiplexing
• 19 DCN-MEAS DCN Measurement Subsystems
• 20 HMP Host Monitoring
• 21 PRM Packet Radio Measurement
• 22 XNS-IDP XEROX NS IDP
• 23 TRUNK-1 Trunk-1
• 24 TRUNK-2 Trunk-2
• 25 LEAF-1 Leaf-1
• 26 LEAF-2 Leaf-2
• 27 RDP Reliable Data Protocol
• 28 IRTP Internet Reliable Transaction
• 29 ISO-TP4 ISO Transport Protocol Class 4
• 30 NETBLT Bulk Data Transfer Protocol
• 31 MFE-NSP MFE Network Services Protocol
• 32 MERIT-INP MERIT Internodal Protocol
• 33 SEP Sequential Exchange Protocol
• 34 3PC Third Party Connect Protocol
• 35 IDPR Inter-Domain Policy Routing Protocol
• 36 XTP XTP
• 37 DDP Datagram Delivery Protocol
• 38 IDPR-CMTP IDPR Control Message Transport Protocol
• 39 TP++ TP++ Transport Protocol
• 40 IL IL Transport Protocol
• 41 IPv6 Ipv6
• 42 SDRP Source Demand Routing Protocol
• 43 IPv6-Route Routing Header for IPv6
• 44 IPv6-Frag Fragment Header for IPv6
• 45 IDRP Inter-Domain Routing Protocol
• 46 RSVP Reservation Protocol
• 47 GRE General Routing Encapsulation
• 48 MHRP Mobile Host Routing Protocol
• 49 BNA BNA
• 50 ESP Encapsulating Security Payload
• 51 AH Authentication Header
• 52 I-NLSP Integrated Net Layer Security TUBA
• 53 SWIPE IP with Encryption
• 54 NARP NBMA Address Resolution Protocol
• 55 MOBILE IP Mobility
• 56 TLSP Transport Layer Security Protocol using Kryptonet key management
• 57 SKIP SKIP
• 58 IPv6-ICMP ICMP for IPv6
• 59 IPv6-NoNxt No Next Header for IPv6
• 60 IPv6-Opts Destination Options for IPv6
• 61 any host internal protocol
• 62 CFTP CFTP
• 63 any local network
• 64 SAT-EXPAK SATNET and Backroom EXPAK
• 65 KRYPTOLAN Kryptolan
• 66 RVD MIT Remote Virtual Disk Protocol
• 67 IPPC Internet Pluribus Packet Core
• 68 any distributed file system
• 69 SAT-MON SATNET Monitoring
• 70 VISA VISA Protocol
• 71 IPCV Internet Packet Core Utility
• 72 CPNX Computer Protocol Network Executive
• 73 CPHB Computer Protocol Heart Beat
• 74 WSN Wang Span Network
• 75 PVP Packet Video Protocol
• 76 BR-SAT-MON Backroom SATNET Monitoring
• 77 SUN-ND SUN ND PROTOCOL-Temporary
• 78 WB-MON WIDEBAND Monitoring
• 79 WB-EXPAK WIDEBAND EXPAK
• 80 ISO-IP ISO Internet Protocol
• 81 VMTP VMTP
• 82 SECURE-VMTP SECURE-VMTP
• 83 VINES VINES
• 84 TTP TTP
• 85 NSFNET-IGP NSFNET-IGP
• 86 DGP Dissimilar Gateway Protocol
• 87 TCF TCF
• 88 EIGRP EIGRP
• 89 OSPFIGP OSPFIGP
• 90 Sprite-RPC Sprite RPC Protocol
• 91 LARP Locus Address Resolution Protocol
• 92 MTP Multicast Transport Protocol
• 93 AX.25 AX.25 Frames
• 94 IPIP IP-within-IP Encapsulation Protocol
• 95 MICP Mobile Internetworking Control Protocol
• 96 SCC-SP Semaphore Communications Sec. Protocol
• 97 ETHERIP Ethernet-within-IP Encapsulation
• 98 ENCAP Encapsulation Header
• 99 any private encryption scheme
• 100 GMTP GMTP
• 101 IFMP Ipsilon Flow Management Protocol
• 102 PNNI PNNI over IP
• 103 PIM Protocol Independent Multicast
• 104 ARIS ARIS
• 105 SCPS SCPS
• 106 QNX QNX
• 107 A/N Active Networks
• 108 IPComp IP Payload Compression Protocol
• 109 SNP Sitara Networks Protocol
• 110 Compaq-Peer Compaq Peer Protocol
• 111 IPX-in-IP IPX in IP
• 112 VRRP Virtual Router Redundancy Protocol
• 113 PGM PGM Reliable Transport Protocol
• 114 any 0-hop protocol
• 115 L2TP Layer Two Tunneling Protocol
• 116 DDX D-II Data Exchange (DDX)
• 117 IATP Interactive Agent Transfer Protocol
• 118 STP Schedule Transfer Protocol
• 119 SRP SpectraLink Radio Protocol
• 120 UTI UTI
• 121 SMP Simple Message Protocol
• 122 SM SM
• 123 PTP Performance Transparency Protocol
• 124 ISIS over IPv4
• 125 FIRE
• 126 CRTP Combat Radio Transport Protocol
• 127 CRUDP Combat Radio User Datagram
• 128 SSCOPMCE
• 129 IPLT
• 130 SPS Secure Packet Shield
• 131 PIPE Private IP Encapsulation within IP
• 132 SCTP Stream Control Transmission Protocol
• 133 FC Fibre Channel
• 134 RSVP-E2E-IGNORE
• 135-254 Unassigned
• 255 Reserved