ITCwiki - User contributions [en]

IEEE 802.1x Port-Based Authentication

2010-05-12T15:59:37Z

Kalarsford:

'''IEEE 802.1x Port-Based Authentication'''

IEEE 802.1x is a standard for port-based network access control. It is an authentication method for devices attempting to connect to a LAN. It's purpose is to prevent unauthorized devices from joining and accessing resources on the network.

802.1x authentication involves 3 devices:

1. Client device

2. Authenticator

3. Authentication Server

The '''client device''', a laptop for example, must be running client software compliant with IEEE 802.1x. Windows XP, Windows Vista and Windows 7 all offer such software.

The '''authenticator''' can be a ethernet switch and can also come in the form of a wireless access point.

The '''authentication server''' is usually a host running software that supports both RADIUS and EAP protocols.

EAP = Extensible Authentication Protocol
RADIUS = Remote Authentication Dial In User Service networking protocol

The authenticator prevents the client device from accessing the network until the client device's identity has been authorized. The client device will need to provide credentials, such as a username & password, to the authenticator. The authenticator will forward the credentials to the authentication server for verification. If the credentials supplied are deemed to be valid by the authentication server, the client is allowed to access the network

Once a client device is plugged into a port on the switch (authenticator) the authentication process may begin. The authenticator will transmit EAP-Request Identity frames to the client device. (The client can also initiate authentication by sending a EAPOL-Start frame to the authenticator. The autheticator would then reply with an EAP-Request Identity frame). The client device will respond with a EAP-Response Identity frame that contains identity information such as a username and password. The authenticator will send the response from the client to the authentication server in the form of a RADIUS Access Request packet. At this point the authentication server and client must agree upon an EAP method to use for authentication. Once an agreement is made, EAP requests and Responses are sent between the client and server until the server responds with an EAP-Success message or an EAP-Failure message. Once authentication is successful the authenticator sets the port in the authorized state and traffic is allowed. If authentication is not successful, the port remains in a unauthorized state. When the client decides to log off, it will then send an EAPOL-logoff message to the authenticator and the port is once again set to a unauthorized state.

'''SWITCH CONFIGURATION for IEEE 802.1x Authentication'''

Step 1: Enter global configuration mode

Switch# '''configure terminal'''

Step 2: Enable AAA

Switch(config)# '''aaa new-model'''

Step 3: Create an IEEE 802.1x authentication method list

Switch(config)# '''aaa authentication dot1x group radius'''

Step 4: Enable IEEE 802.1x authentication globally on the switch

Switch(config)# '''dot1x system-auth-control'''

Step 5: Specify the port connected to the client that you want enabled for IEEE 802.1x authentication

Switch(config)# '''interface fa0/6'''

Step 6: Enable IEEE 802.1x authentication on the port

Switch(config-if)# '''dot1x port-control auto'''

Use the "'''show dot1x'''" command to verify the entries you made and save your configurations.

The following command must also be added to the switch for communication with the Radius Server (authentication server). The command is '''"radius-server host (hostname | ip address) auth-port (port-number) key (string)'''. Either a hostname or ip address may be entered. For the auth-port, you need to specify the UDP destination port for authentication requests within the range of 0 to 65536. The key string is a text string that must be the same as the encryption key used on the radius server. Below is an example configuration.

Switch(config)# '''radius-server host 172.16.0.1 auth-port 1520 key ccna123
'''

IEEE 802.1x Port-Based Authentication

2010-05-12T02:07:44Z

Kalarsford:

'''IEEE 802.1x Port-Based Authentication'''

IEEE 802.1x is a standard for port-based network access control. It is an authentication method for devices attempting to connect to a LAN. It's purpose is to prevent unauthorized devices from joining and accessing resources on the network.

802.1x authentication involves 3 devices:

1. Client device

2. Authenticator

3. Authentication Server

The '''client device''', a laptop for example, must be running client software compliant with IEEE 802.1x. Windows XP, Windows Vista and Windows 7 all offer such software.

The '''authenticator''' can be a ethernet switch and can also come in the form of a wireless access point.

The '''authentication server''' is usually a host running software that supports both RADIUS and EAP protocols.

EAP = Extensible Authentication Protocol
RADIUS = Remote Authentication Dial In User Service networking protocol

The authenticator prevents the client device from accessing the network until the client device's identity has been authorized. The client device will need to provide credentials, such as a username & password, to the authenticator. The authenticator will forward the credentials to the authentication server for verification. If the credentials supplied are deemed to be valid by the authentication server, the client is allowed to access the network

Once a client device is plugged into a port on the switch (authenticator) the authentication process may begin. The authenticator will transmit EAP-Request Identity frames to the client device. (The client can also initiate authentication by sending a EAPOL-Start frame to the authenticator. The autheticator would then reply with an EAP-Request Identity frame). The client device will respond with a EAP-Response Identity frame that contains identity information such as a username and password. The authenticator will send the response from the client to the authentication server in the form of a RADIUS Access Request packet. At this point the authentication server and client must agree upon an EAP method to use for authentication. Once an agreement is made, EAP requests and Responses are sent between the client and server until the server responds with an EAP-Success message or an EAP-Failure message. Once authentication is successful the authenticator sets the port in the authorized state and traffic is allowed. If authentication is not successful, the port remains in a unauthorized state. When the client decides to log off, it will then send an EAPOL-logoff message to the authenticator and the port is once again set to a unauthorized state.

'''SWITCH CONFIGURATION for IEEE 802.1x Authentication'''

Step 1: Enter global configuration mode

Switch# '''configure terminal'''

Step 2: Enable AAA

Switch(config)# '''aaa new-model'''

Step 3: Create an IEEE 802.1x authentication method list

Switch(config)# '''aaa authentication dot1x group radius'''

Step 4: Enable IEEE 802.1x authentication globally on the switch

Switch(config)# '''dot1x system-auth-control'''

Step 5: Specify the port connected to the client that you want enabled for IEEE 802.1x authentication

Switch(config)# '''interface fa0/6'''

Step 6: Enable IEEE 802.1x authentication on the port

Switch(config-if)# '''dot1x port-control auto'''

Use the "'''show dot1x'''" command to verify the entries you made and save your configurations.

The following command must also be added to the switch for communication with the Radius Server (authentication server). The command is '''"radius-server host (hostname | ip address) auth-port (port-number) key (string)'''. Either a hostname or ip address may be entered. For the auth-port, you are to specify the UDP destination port for authentication requests from a range of 0 to 65536. The key string is a text string that must match the encryption key used on the radius server. Below is an example configuration.

Switch(config)# '''radius-server host 172.16.0.1 auth-port 1520 key ccna123
'''

IEEE 802.1x Port-Based Authentication

2010-05-12T02:07:12Z

Kalarsford:

'''IEEE 802.1x Port-Based Authentication'''

IEEE 802.1x is a standard for port-based network access control. It is an authentication method for devices attempting to connect to a LAN. It's purpose is to prevent unauthorized devices from joining and accessing resources on the network.

802.1x authentication involves 3 devices:

1. Client device

2. Authenticator

3. Authentication Server

The '''client device''', for example a laptop, must be running client software compliant with IEEE 802.1x. Windows XP, Windows Vista and Windows 7 all offer such software.

The '''authenticator''' can be a ethernet switch and can also come in the form of a wireless access point.

The '''authentication server''' is usually a host running software that supports both RADIUS and EAP protocols.

EAP = Extensible Authentication Protocol
RADIUS = Remote Authentication Dial In User Service networking protocol

The authenticator prevents the client device from accessing the network until the client device's identity has been authorized. The client device will need to provide credentials, such as a username & password, to the authenticator. The authenticator will forward the credentials to the authentication server for verification. If the credentials supplied are deemed to be valid by the authentication server, the client is allowed to access the network

Once a client device is plugged into a port on the switch (authenticator) the authentication process may begin. The authenticator will transmit EAP-Request Identity frames to the client device. (The client can also initiate authentication by sending a EAPOL-Start frame to the authenticator. The autheticator would then reply with an EAP-Request Identity frame). The client device will respond with a EAP-Response Identity frame that contains identity information such as a username and password. The authenticator will send the response from the client to the authentication server in the form of a RADIUS Access Request packet. At this point the authentication server and client must agree upon an EAP method to use for authentication. Once an agreement is made, EAP requests and Responses are sent between the client and server until the server responds with an EAP-Success message or an EAP-Failure message. Once authentication is successful the authenticator sets the port in the authorized state and traffic is allowed. If authentication is not successful, the port remains in a unauthorized state. When the client decides to log off, it will then send an EAPOL-logoff message to the authenticator and the port is once again set to a unauthorized state.

'''SWITCH CONFIGURATION for IEEE 802.1x Authentication'''

Step 1: Enter global configuration mode

Switch# '''configure terminal'''

Step 2: Enable AAA

Switch(config)# '''aaa new-model'''

Step 3: Create an IEEE 802.1x authentication method list

Switch(config)# '''aaa authentication dot1x group radius'''

Step 4: Enable IEEE 802.1x authentication globally on the switch

Switch(config)# '''dot1x system-auth-control'''

Step 5: Specify the port connected to the client that you want enabled for IEEE 802.1x authentication

Switch(config)# '''interface fa0/6'''

Step 6: Enable IEEE 802.1x authentication on the port

Switch(config-if)# '''dot1x port-control auto'''

Use the "'''show dot1x'''" command to verify the entries you made and save your configurations.

The following command must also be added to the switch for communication with the Radius Server (authentication server). The command is '''"radius-server host (hostname | ip address) auth-port (port-number) key (string)'''. Either a hostname or ip address may be entered. For the auth-port, you are to specify the UDP destination port for authentication requests from a range of 0 to 65536. The key string is a text string that must match the encryption key used on the radius server. Below is an example configuration.

Switch(config)# '''radius-server host 172.16.0.1 auth-port 1520 key ccna123
'''

IEEE 802.1x Port-Based Authentication

2010-05-12T02:06:41Z

Kalarsford:

'''IEEE 802.1x Port-Based Authentication'''

IEEE 802.1x is a standard for port-based network access control. It is an authentication method for devices attempting to connect to a LAN. It's purpose is to prevent unauthorized devices from joining and accessing resources on the network.

802.1x authentication involves 3 devices:

1. client device

2. Authenticator

3. Authentication Server

The '''client device''', for example a laptop, must be running client software compliant with IEEE 802.1x. Windows XP, Windows Vista and Windows 7 all offer such software.

The '''authenticator''' can be a ethernet switch and can also come in the form of a wireless access point.

The '''authentication server''' is usually a host running software that supports both RADIUS and EAP protocols.

EAP = Extensible Authentication Protocol
RADIUS = Remote Authentication Dial In User Service networking protocol

The authenticator prevents the client device from accessing the network until the client device's identity has been authorized. The client device will need to provide credentials, such as a username & password, to the authenticator. The authenticator will forward the credentials to the authentication server for verification. If the credentials supplied are deemed to be valid by the authentication server, the client is allowed to access the network

Once a client device is plugged into a port on the switch (authenticator) the authentication process may begin. The authenticator will transmit EAP-Request Identity frames to the client device. (The client can also initiate authentication by sending a EAPOL-Start frame to the authenticator. The autheticator would then reply with an EAP-Request Identity frame). The client device will respond with a EAP-Response Identity frame that contains identity information such as a username and password. The authenticator will send the response from the client to the authentication server in the form of a RADIUS Access Request packet. At this point the authentication server and client must agree upon an EAP method to use for authentication. Once an agreement is made, EAP requests and Responses are sent between the client and server until the server responds with an EAP-Success message or an EAP-Failure message. Once authentication is successful the authenticator sets the port in the authorized state and traffic is allowed. If authentication is not successful, the port remains in a unauthorized state. When the client decides to log off, it will then send an EAPOL-logoff message to the authenticator and the port is once again set to a unauthorized state.

'''SWITCH CONFIGURATION for IEEE 802.1x Authentication'''

Step 1: Enter global configuration mode

Switch# '''configure terminal'''

Step 2: Enable AAA

Switch(config)# '''aaa new-model'''

Step 3: Create an IEEE 802.1x authentication method list

Switch(config)# '''aaa authentication dot1x group radius'''

Step 4: Enable IEEE 802.1x authentication globally on the switch

Switch(config)# '''dot1x system-auth-control'''

Step 5: Specify the port connected to the client that you want enabled for IEEE 802.1x authentication

Switch(config)# '''interface fa0/6'''

Step 6: Enable IEEE 802.1x authentication on the port

Switch(config-if)# '''dot1x port-control auto'''

Use the "'''show dot1x'''" command to verify the entries you made and save your configurations.

The following command must also be added to the switch for communication with the Radius Server (authentication server). The command is '''"radius-server host (hostname | ip address) auth-port (port-number) key (string)'''. Either a hostname or ip address may be entered. For the auth-port, you are to specify the UDP destination port for authentication requests from a range of 0 to 65536. The key string is a text string that must match the encryption key used on the radius server. Below is an example configuration.

Switch(config)# '''radius-server host 172.16.0.1 auth-port 1520 key ccna123
'''

IEEE 802.1x Port-Based Authentication

2010-05-12T02:06:02Z

Kalarsford:

'''IEEE 802.1x Port-Based Authentication'''

IEEE 802.1x is a standard for port-based network access control. It is an authentication method for devices attempting to connect to a LAN. It's purpose is to prevent unauthorized devices from joining and accessing resources on the network.

802.1x authentication involves 3 devices.

1. A client device
2. A Authenticator
3. A Authentication Server

The '''client device''', for example a laptop, must be running client software compliant with IEEE 802.1x. Windows XP, Windows Vista and Windows 7 all offer such software.

The '''authenticator''' can be a ethernet switch and can also come in the form of a wireless access point.

The '''authentication server''' is usually a host running software that supports both RADIUS and EAP protocols.

EAP = Extensible Authentication Protocol
RADIUS = Remote Authentication Dial In User Service networking protocol

The authenticator prevents the client device from accessing the network until the client device's identity has been authorized. The client device will need to provide credentials, such as a username & password, to the authenticator. The authenticator will forward the credentials to the authentication server for verification. If the credentials supplied are deemed to be valid by the authentication server, the client is allowed to access the network

Once a client device is plugged into a port on the switch (authenticator) the authentication process may begin. The authenticator will transmit EAP-Request Identity frames to the client device. (The client can also initiate authentication by sending a EAPOL-Start frame to the authenticator. The autheticator would then reply with an EAP-Request Identity frame). The client device will respond with a EAP-Response Identity frame that contains identity information such as a username and password. The authenticator will send the response from the client to the authentication server in the form of a RADIUS Access Request packet. At this point the authentication server and client must agree upon an EAP method to use for authentication. Once an agreement is made, EAP requests and Responses are sent between the client and server until the server responds with an EAP-Success message or an EAP-Failure message. Once authentication is successful the authenticator sets the port in the authorized state and traffic is allowed. If authentication is not successful, the port remains in a unauthorized state. When the client decides to log off, it will then send an EAPOL-logoff message to the authenticator and the port is once again set to a unauthorized state.

'''SWITCH CONFIGURATION for IEEE 802.1x Authentication'''

Step 1: Enter global configuration mode

Switch# '''configure terminal'''

Step 2: Enable AAA

Switch(config)# '''aaa new-model'''

Step 3: Create an IEEE 802.1x authentication method list

Switch(config)# '''aaa authentication dot1x group radius'''

Step 4: Enable IEEE 802.1x authentication globally on the switch

Switch(config)# '''dot1x system-auth-control'''

Step 5: Specify the port connected to the client that you want enabled for IEEE 802.1x authentication

Switch(config)# '''interface fa0/6'''

Step 6: Enable IEEE 802.1x authentication on the port

Switch(config-if)# '''dot1x port-control auto'''

Use the "'''show dot1x'''" command to verify the entries you made and save your configurations.

The following command must also be added to the switch for communication with the Radius Server (authentication server). The command is '''"radius-server host (hostname | ip address) auth-port (port-number) key (string)'''. Either a hostname or ip address may be entered. For the auth-port, you are to specify the UDP destination port for authentication requests from a range of 0 to 65536. The key string is a text string that must match the encryption key used on the radius server. Below is an example configuration.

Switch(config)# '''radius-server host 172.16.0.1 auth-port 1520 key ccna123
'''

IEEE 802.1x Port-Based Authentication

2010-05-12T02:05:31Z

Kalarsford:

'''IEEE 802.1x Port-Based Authentication'''

IEEE 802.1x is a standard for port-based network access control. It is an authentication method for devices attempting to connect to a LAN. It's purpose is to prevent unauthorized devices from joining and accessing resources on the network.

802.1x authentication involves 3 devices:

1. A client device
2. A Authenticator
3. A Authentication Server

The '''client device''', for example a laptop, must be running client software compliant with IEEE 802.1x. Windows XP, Windows Vista and Windows 7 all offer such software.

The '''authenticator''' can be a ethernet switch and can also come in the form of a wireless access point.

The '''authentication server''' is usually a host running software that supports both RADIUS and EAP protocols.

EAP = Extensible Authentication Protocol
RADIUS = Remote Authentication Dial In User Service networking protocol

The authenticator prevents the client device from accessing the network until the client device's identity has been authorized. The client device will need to provide credentials, such as a username & password, to the authenticator. The authenticator will forward the credentials to the authentication server for verification. If the credentials supplied are deemed to be valid by the authentication server, the client is allowed to access the network

Once a client device is plugged into a port on the switch (authenticator) the authentication process may begin. The authenticator will transmit EAP-Request Identity frames to the client device. (The client can also initiate authentication by sending a EAPOL-Start frame to the authenticator. The autheticator would then reply with an EAP-Request Identity frame). The client device will respond with a EAP-Response Identity frame that contains identity information such as a username and password. The authenticator will send the response from the client to the authentication server in the form of a RADIUS Access Request packet. At this point the authentication server and client must agree upon an EAP method to use for authentication. Once an agreement is made, EAP requests and Responses are sent between the client and server until the server responds with an EAP-Success message or an EAP-Failure message. Once authentication is successful the authenticator sets the port in the authorized state and traffic is allowed. If authentication is not successful, the port remains in a unauthorized state. When the client decides to log off, it will then send an EAPOL-logoff message to the authenticator and the port is once again set to a unauthorized state.

'''SWITCH CONFIGURATION for IEEE 802.1x Authentication'''

Step 1: Enter global configuration mode

Switch# '''configure terminal'''

Step 2: Enable AAA

Switch(config)# '''aaa new-model'''

Step 3: Create an IEEE 802.1x authentication method list

Switch(config)# '''aaa authentication dot1x group radius'''

Step 4: Enable IEEE 802.1x authentication globally on the switch

Switch(config)# '''dot1x system-auth-control'''

Step 5: Specify the port connected to the client that you want enabled for IEEE 802.1x authentication

Switch(config)# '''interface fa0/6'''

Step 6: Enable IEEE 802.1x authentication on the port

Switch(config-if)# '''dot1x port-control auto'''

Use the "'''show dot1x'''" command to verify the entries you made and save your configurations.

The following command must also be added to the switch for communication with the Radius Server (authentication server). The command is '''"radius-server host (hostname | ip address) auth-port (port-number) key (string)'''. Either a hostname or ip address may be entered. For the auth-port, you are to specify the UDP destination port for authentication requests from a range of 0 to 65536. The key string is a text string that must match the encryption key used on the radius server. Below is an example configuration.

Switch(config)# '''radius-server host 172.16.0.1 auth-port 1520 key ccna123
'''

IEEE 802.1x Port-Based Authentication

2010-05-12T02:01:29Z

Kalarsford: Created page with ''''IEEE 802.1x Port-Based Authentication''' IEEE 802.1x is a standard for port-based network access control. It is an authentication method for devices attempting to connect to…'

'''IEEE 802.1x Port-Based Authentication'''

IEEE 802.1x is a standard for port-based network access control. It is an authentication method for devices attempting to connect to a LAN. It's purpose is to prevent unauthorized devices from joining and accessing resources on the network.

802.1x authentication involves 3 devices:

1. Client Device
2. Authentication Server
3. Authenticator

The '''client device''', for example a laptop, must be running client software compliant with IEEE 802.1x. Windows XP, Windows Vista and Windows 7 all offer such software.

The '''authenticator''' can be a ethernet switch and can also come in the form of a wireless access point.

The '''authentication server''' is usually a host running software that supports both RADIUS and EAP protocols.

EAP = Extensible Authentication Protocol
RADIUS = Remote Authentication Dial In User Service networking protocol

The authenticator prevents the client device from accessing the network until the client device's identity has been authorized. The client device will need to provide credentials, such as a username & password, to the authenticator. The authenticator will forward the credentials to the authentication server for verification. If the credentials supplied are deemed to be valid by the authentication server, the client is allowed to access the network

Once a client device is plugged into a port on the switch (authenticator) the authentication process may begin. The authenticator will transmit EAP-Request Identity frames to the client device. (The client can also initiate authentication by sending a EAPOL-Start frame to the authenticator. The autheticator would then reply with an EAP-Request Identity frame). The client device will respond with a EAP-Response Identity frame that contains identity information such as a username and password. The authenticator will send the response from the client to the authentication server in the form of a RADIUS Access Request packet. At this point the authentication server and client must agree upon an EAP method to use for authentication. Once an agreement is made, EAP requests and Responses are sent between the client and server until the server responds with an EAP-Success message or an EAP-Failure message. Once authentication is successful the authenticator sets the port in the authorized state and traffic is allowed. If authentication is not successful, the port remains in a unauthorized state. When the client decides to log off, it will then send an EAPOL-logoff message to the authenticator and the port is once again set to a unauthorized state.

'''SWITCH CONFIGURATION for IEEE 802.1x Authentication'''

Step 1: Enter global configuration mode

Switch# '''configure terminal'''

Step 2: Enable AAA

Switch(config)# '''aaa new-model'''

Step 3: Create an IEEE 802.1x authentication method list

Switch(config)# '''aaa authentication dot1x group radius'''

Step 4: Enable IEEE 802.1x authentication globally on the switch

Switch(config)# '''dot1x system-auth-control'''

Step 5: Specify the port connected to the client that you want enabled for IEEE 802.1x authentication

Switch(config)# '''interface fa0/6'''

Step 6: Enable IEEE 802.1x authentication on the port

Switch(config-if)# '''dot1x port-control auto'''

Use the "'''show dot1x'''" command to verify the entries you made and save your configurations.

The following command must also be added to the switch for communication with the Radius Server (authentication server). The command is '''"radius-server host (hostname | ip address) auth-port (port-number) key (string)'''. Either a hostname or ip address may be entered. For the auth-port, you are to specify the UDP destination port for authentication requests from a range of 0 to 65536. The key string is a text string that must match the encryption key used on the radius server. Below is an example configuration.

Switch(config)# '''radius-server host 172.16.0.1 auth-port 1520 key ccna123
'''

User:Kalarsford

2010-03-05T22:01:53Z

Kalarsford: moved User:Kalarsford to Network Access Control

#REDIRECT [[Network Access Control]]

Network Access Control

2010-03-05T22:01:53Z

Kalarsford: moved User:Kalarsford to Network Access Control

'''NETWORK ACCESS CONTROL'''

'''What is Network Access Control?'''

A simple definition of Network Access Control (NAC) can be described as a networking solution that controls, secures, and restricts access to a computer network. In a nutshell, NACs primary function is to allow you to create a policy that defines what devices can join your network and what resources those devices can access once they are on your network. However, NAC can provide other services as well such as device discovery, virtual LAN management, provide LAN access to visitors, and switch management.

NAC provides a way to protect a network from security problems that originate from the "inside". This is helpful as network security policies are often focused on preventing attacks from the outside with the use of a firewall and anti-virus software and often leave the door open for easy access to network resources from users on the "inside". For example, an outside client or even a visitor to your company may have access to available ports on your network. The computer the guest connects to a port on your network does not have any firewall or anti-virus software. So, after he connects to your network, he surfs the internet, picks up a virus and it turn possibly infects your entire network with the virus. NAC can help prevent this situation from occurring.

'''What can you do with NAC?'''

'''Control Access To Your Network:'''

NAC uses a set of rules to define and implement a policy that describes how to secure access to network ports by devices when they intially attempt to access the network. For example, when a computer connects to a port on your network, it will not be permitted to access anything on the network unless it meets the requirements of the defined policy. An example of a requirement that must be met may be that a computer must have anti-virus software installed on it. If a computer meets all the requirements of the policy, then it will be allowed access to network resources and the internet. However, just because a computer may meet the requirements of a policy, it doesn't mean they will have access to all available resources. NAC can be set up to allow certain computers to have access to only certain things. NAC can also be set up to only allow certain devices on the network.

NAC policy is basically set up and defined by a network administrator. There is no standard policy. A policy can be created by an administrator to suit the specific needs of their company.

'''Device Discovery'''

NAC can also be used to find out what devices are currently connected to your network. NAC can be set up to query switches for a list of devices currently connected to the switch ports. Information about the port, port number, last vlan and last date used can be created and stored. Reports can be generated from this information gathered. Also, the devices connected to the ports can be scanned as well, and you can obtain information such as what operating system a certain device is running. Device discovery can be a useful tool and provide you with an iventory of devices on your network.

'''Virtual LAN Management'''

VLAN Management can be made easier by using NAC. For example, if a company re-organizes and decides to move computers to different locations, with a NAC application you wouldn't need to change the configurations on the switches to reflect the changes in the re-organizing. You could use the NAC applications GUI and make configuration changes with the simple use of drop-down lists, etc. Also, if there was ever a need to create a temporary VLAN for the use of a meeting, special project, etc, you could do so using a NAC GUI rather than having to configure and cable switches and PCs.

'''LAN Access for Guests/Visitors'''

NAC can also be used to allow access to network resources and the internet to company guests or visitors. Policies can be created to grant access to certain network resources. Policies can be created on a per-port basis so depending upon which port the visitor connects to, they will only have access to resources allowed in the policy. Policies can also be created that will deny all access to any unkown device and also trigger alerts when an unkown device connects to a port. You could also set up a policy to deny access to any unkown device, except in certain areas such as a meeting room or lobby.

'''Switch Management'''

NAC application GUIs make it easy to configure your switches even for the most inexperienced users. And for experienced users, NAC application GUIs can really cut down the time required to configure and manage your switches.

----

Network Access Control

2010-03-04T19:24:11Z

Kalarsford:

Network Access Control

2010-03-04T18:58:41Z

Kalarsford:

'''NETWORK ACCESS CONTROL'''

'''What is Network Access Control?'''

A simple definition of Network Access Control (NAC) can be described as a networking solution that controls, secures, and restricts access to a computer network. In a nutshell, NACs primary function is to allow you to create a policy that defines what devices can join your network and what resources those devices can access once they are on your network. However, NAC can provide other services as well such as device discovery, virtual LAN management, provide LAN access to visitors, and switch management.

NAC provides a way to protect a network from security problems that originate from the "inside". This is helpful as network security policies are often focused on preventing attacks from the outside with the use of a firewall and anti-virus software and often leave the door open for easy access to network resources from users on the "inside". For example, an outside client or even a visitor to your company may have access to available ports on your network. The computer the guest connects to a port on your network does not have any firewall or anti-virus software. So, when he connects to your network, surfs the internet and picks up a virus that may possibly infect your entire network. NAC can help prevent this situation from occurring.

'''What can you do with NAC?'''

'''Control Access To Your Network:'''

NAC uses a set of rules to define and implement a policy that describes how to secure access to network ports by devices when they intially attempt to access the network. For example, when a computer connects to a port on your network, it will not be permitted to access anything on the network unless it meets the requirements of the defined policy. An example of a requirement that must be met may be that a computer must have anti-virus software installed on it. If a computer meets all the requirements of the policy, then it will be allowed access to network resources and the internet. However, just because a computer may meet the requirements of a policy, it doesn't mean they will have access to all available resources. NAC can be set up to allow certain computers to have access to only certain things. NAC can also be set up to only allow certain devices on the network.

NAC policy is basically set up and defined by a network administrator. There is no standard policy. A policy can be created by an administrator to suit the specific needs of their company.

'''Device Discovery'''

NAC can also be used to find out what devices are currently connected to your network. NAC can be set up to query switches for a list of devices currently connected to the switch ports. Information about the port, port number, last vlan and last date used can be created and stored. Reports can be generated from this information gathered. Also, the devices connected to the ports can be scanned as well, and you can obtain information such as what operating system a certain device is running. Device discovery can be a useful tool and provide you with an iventory of devices on your network.

'''Virtual LAN Management'''

VLAN Management can be made easier by using NAC. For example, if a company re-organizes and decides to move computers to different locations, with a NAC application you wouldn't need to change the configurations on the switches to reflect the changes in the re-organizing. You could use the NAC applications GUI and make configuration changes with the simple use of drop-down lists, etc. Also, if there was ever a need to create a temporary VLAN for the use of a meeting, special project, etc, you could do so using a NAC GUI rather than having to configure and cable switches and PCs.

'''LAN Access for Guests/Visitors'''

NAC can also be used to allow access to network resources and the internet to company guests or visitors. Policies can be created to grant access to certain network resources. Policies can be created on a per-port basis so depending upon which port the visitor connects to, they will only have access to resources allowed in the policy. Policies can also be created that will deny all access to any unkown device and also trigger alerts when an unkown device connects to a port. You could also set up a policy to deny access to any unkown device, except in certain areas such as a meeting room or lobby.

'''Switch Management'''

NAC application GUIs make it easy to configure your switches even for the most inexperienced users. And for experienced users, NAC application GUIs can really cut down the time required to configure and manage your switches.

----

Network Access Control

2010-03-04T18:58:01Z

Kalarsford:

'''NETWORK ACCESS CONTROL'''
'''
What is Network Access Control?'''

A simple definition of Network Access Control (NAC) can be described as a networking solution that controls, secures, and restricts access to a computer network. In a nutshell, NACs primary function is to allow you to create a policy that defines what devices can join your network and what resources those devices can access once they are on your network. However, NAC can provide other services as well such as device discovery, virtual LAN management, provide LAN access to visitors, and switch management.

NAC provides a way to protect a network from security problems that originate from the "inside". This is helpful as network security policies are often focused on preventing attacks from the outside with the use of a firewall and anti-virus software and often leave the door open for easy access to network resources from users on the "inside". For example, an outside client or even a visitor to your company may have access to available ports on your network. The computer the guest connects to a port on your network does not have any firewall or anti-virus software. So, when he connects to your network, surfs the internet and picks up a virus that may possibly infect your entire network. NAC can help prevent this situation from occurring.

'''What can you do with NAC?'''

'''Control Access To Your Network:'''

NAC uses a set of rules to define and implement a policy that describes how to secure access to network ports by devices when they intially attempt to access the network. For example, when a computer connects to a port on your network, it will not be permitted to access anything on the network unless it meets the requirements of the defined policy. An example of a requirement that must be met may be that a computer must have anti-virus software installed on it. If a computer meets all the requirements of the policy, then it will be allowed access to network resources and the internet. However, just because a computer may meet the requirements of a policy, it doesn't mean they will have access to all available resources. NAC can be set up to allow certain computers to have access to only certain things. NAC can also be set up to only allow certain devices on the network.

NAC policy is basically set up and defined by a network administrator. There is no standard policy. A policy can be created by an administrator to suit the specific needs of their company.

'''Device Discovery'''

NAC can also be used to find out what devices are currently connected to your network. NAC can be set up to query switches for a list of devices currently connected to the switch ports. Information about the port, port number, last vlan and last date used can be created and stored. Reports can be generated from this information gathered. Also, the devices connected to the ports can be scanned as well, and you can obtain information such as what operating system a certain device is running. Device discovery can be a useful tool and provide you with an iventory of devices on your network.

'''Virtual LAN Management'''

VLAN Management can be made easier by using NAC. For example, if a company re-organizes and decides to move computers to different locations, with a NAC application you wouldn't need to change the configurations on the switches to reflect the changes in the re-organizing. You could use the NAC applications GUI and make configuration changes with the simple use of drop-down lists, etc. Also, if there was ever a need to create a temporary VLAN for the use of a meeting, special project, etc, you could do so using a NAC GUI rather than having to configure and cable switches and PCs.

'''LAN Access for Guests/Visitors'''

NAC can also be used to allow access to network resources and the internet to company guests or visitors. Policies can be created to grant access to certain network resources. Policies can be created on a per-port basis so depending upon which port the visitor connects to, they will only have access to resources allowed in the policy. Policies can also be created that will deny all access to any unkown device and also trigger alerts when an unkown device connects to a port. You could also set up a policy to deny access to any unkown device, except in certain areas such as a meeting room or lobby.

'''Switch Management'''

NAC application GUIs make it easy to configure your switches even for the most inexperienced users. And for experienced users, NAC application GUIs can really cut down the time required to configure and manage your switches.

----

Network Access Control

2010-03-04T18:56:30Z

Kalarsford: Created page with 'NETWORK ACCESS CONTROL What is Network Access Control? A simple definition of Network Access Control (NAC) can be described as a networking solution that controls, secures, an…'

NETWORK ACCESS CONTROL

What is Network Access Control?

A simple definition of Network Access Control (NAC) can be described as a networking solution that controls, secures, and restricts access to a computer network. In a nutshell, NACs primary function is to allow you to create a policy that defines what devices can join your network and what resources those devices can access once they are on your network. However, NAC can provide other services as well such as device discovery, virtual LAN management, provide LAN access to visitors, and switch management.

NAC provides a way to protect a network from security problems that originate from the "inside". This is helpful as network security policies are often focused on preventing attacks from the outside with the use of a firewall and anti-virus software and often leave the door open for easy access to network resources from users on the "inside". For example, an outside client or even a visitor to your company may have access to available ports on your network. The computer the guest connects to a port on your network does not have any firewall or anti-virus software. So, when he connects to your network, surfs the internet and picks up a virus that may possibly infect your entire network. NAC can help prevent this situation from occurring.

What can you do with NAC?

Control Access To Your Network:

NAC uses a set of rules to define and implement a policy that describes how to secure access to network ports by devices when they intially attempt to access the network. For example, when a computer connects to a port on your network, it will not be permitted to access anything on the network unless it meets the requirements of the defined policy. An example of a requirement that must be met may be that a computer must have anti-virus software installed on it. If a computer meets all the requirements of the policy, then it will be allowed access to network resources and the internet. However, just because a computer may meet the requirements of a policy, it doesn't mean they will have access to all available resources. NAC can be set up to allow certain computers to have access to only certain things. NAC can also be set up to only allow certain devices on the network.

NAC policy is basically set up and defined by a network administrator. There is no standard policy. A policy can be created by an administrator to suit the specific needs of their company.

Device Discovery

NAC can also be used to find out what devices are currently connected to your network. NAC can be set up to query switches for a list of devices currently connected to the switch ports. Information about the port, port number, last vlan and last date used can be created and stored. Reports can be generated from this information gathered. Also, the devices connected to the ports can be scanned as well, and you can obtain information such as what operating system a certain device is running. Device discovery can be a useful tool and provide you with an iventory of devices on your network.

Virtual LAN Management

VLAN Management can be made easier by using NAC. For example, if a company re-organizes and decides to move computers to different locations, with a NAC application you wouldn't need to change the configurations on the switches to reflect the changes in the re-organizing. You could use the NAC applications GUI and make configuration changes with the simple use of drop-down lists, etc. Also, if there was ever a need to create a temporary VLAN for the use of a meeting, special project, etc, you could do so using a NAC GUI rather than having to configure and cable switches and PCs.

LAN Access for Guests/Visitors

NAC can also be used to allow access to network resources and the internet to company guests or visitors. Policies can be created to grant access to certain network resources. Policies can be created on a per-port basis so depending upon which port the visitor connects to, they will only have access to resources allowed in the policy. Policies can also be created that will deny all access to any unkown device and also trigger alerts when an unkown device connects to a port. You could also set up a policy to deny access to any unkown device, except in certain areas such as a meeting room or lobby.

Switch Management

NAC application GUIs make it easy to configure your switches even for the most inexperienced users. And for experienced users, NAC application GUIs can really cut down the time required to configure and manage your switches.

VMWare Setup

2009-12-16T02:32:00Z

Kalarsford:

= '''VMware Setup Instructions''' =

'''Step 1:  Locate VMware folder in C:'''

*Click My Computer
*Click on C: drive
*Click on VMWare

 

'''Step 2:  Make a copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on the "B143 B144 VM 3-13-09" folder and select copy

[[File:Vm5.JPG]]

 

'''Step 3:  Paste your copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on an open area in the VMWare folder and select paste.  Process will take 10-15 minutes to complete.

[[File:Vm3.JPG]]

*Rename folder
*Only the user who created this folder will be able to use it

 

'''Step 4:  Open VMWare Workstation'''

*Click Start / All Programs / VMWare
*Click VMWare Workstation

 

'''Step 5:  Open Existing VM or Team'''

*Click on "Open Existing VM or Team"

[[File:Vm1.JPG]]

*Open the folder that you created in Step 3
*Double Click on "Windows XP SP3.vmx"

[[File:Vm2.JPG]]

*Under the "Device" tab make sure the "network adapter" is set to "bridged"

[[File:bridged.jpg]]

*Under "Commands" click on "Power on this Virtual Machine". You can also click the green arrow in the toolbar.

[[File:Vm6.JPG]]

*Prompt will ask you if you "moved" or "copied" the virtual machine.  Select "I copied it".

[[File:Vm4.JPG]]

*Windows XP setup wizard will appear. Follow steps to complete setup.

 

'''*Process must be done on each computer that you log in on to be able to run VMWare.'''

'''*To run multiple VMWare workstations on same computer, make an extra copy of the "B143 B144 VM 3-13-09" folder.'''

'''*Make sure under the "network connections" for the PC you are using, the wireless connection is disabled. Otherwise, VMWare may not run properly.

VMWare Setup

2009-12-16T02:25:21Z

Kalarsford:

= '''VMware Setup Instructions''' =

'''Step 1:  Locate VMware folder in C:'''

*Click My Computer
*Click on C: drive
*Click on VMWare

 

'''Step 2:  Make a copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on the "B143 B144 VM 3-13-09" folder and select copy

[[File:Vm5.JPG]]

 

'''Step 3:  Paste your copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on an open area in the VMWare folder and select paste.  Process will take 10-15 minutes to complete.

[[File:Vm3.JPG]]

*Rename folder
*Only the user who created this folder will be able to use it

 

'''Step 4:  Open VMWare Workstation'''

*Click Start / All Programs / VMWare
*Click VMWare Workstation

 

'''Step 5:  Open Existing VM or Team'''

*Click on "Open Existing VM or Team"

[[File:Vm1.JPG]]

*Open the folder that you created in Step 3
*Double Click on "Windows XP SP3.vmx"

[[File:Vm2.JPG]]

*Under the "Device" tab make sure the "network adapter" is set to "bridged"

[[File:bridged.jpg]]

*Under "Commands" click on "Power on this Virtual Machine" (next to the green arrow).

[[File:Vm6.JPG]]

*Prompt will ask you if you "moved" or "copied" the virtual machine.  Select "I copied it".

[[File:Vm4.JPG]]

*Windows XP setup wizard will appear. Follow steps to complete setup.

 

'''*Process must be done on each computer that you log in on to be able to run VMWare.'''

'''*To run multiple VMWare workstations on same computer, make an extra copy of the "B143 B144 VM 3-13-09" folder.'''

'''*Make sure under the "network connections" for the PC you are using, the wireless connection is disabled. Otherwise, VMWare may not run properly.

File:Vm6.JPG

2009-12-16T02:24:32Z

Kalarsford: uploaded a new version of "File:Vm6.JPG"

File:Vm6.JPG

2009-12-16T02:20:36Z

Kalarsford:

VMWare Setup

2009-12-16T02:18:42Z

Kalarsford:

= '''VMware Setup Instructions''' =

'''Step 1:  Locate VMware folder in C:'''

*Click My Computer
*Click on C: drive
*Click on VMWare

 

'''Step 2:  Make a copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on the "B143 B144 VM 3-13-09" folder and select copy

[[File:Vm5.JPG]]

 

'''Step 3:  Paste your copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on an open area in the VMWare folder and select paste.  Process will take 10-15 minutes to complete.

[[File:Vm3.JPG]]

*Rename folder
*Only the user who created this folder will be able to use it

 

'''Step 4:  Open VMWare Workstation'''

*Click Start / All Programs / VMWare
*Click VMWare Workstation

 

'''Step 5:  Open Existing VM or Team'''

*Click on "Open Existing VM or Team"

[[File:Vm1.JPG]]

*Open the folder that you created in Step 3
*Double Click on "Windows XP SP3.vmx"

[[File:Vm2.JPG]]

*Under the "Device" tab make sure the "network adapter" is set to "bridged"

[[File:bridged.jpg]]

*Under "Commands" click on "Power on this Virtual Machine" (next to the green arrow).
*Prompt will ask you if you "moved" or "copied" the virtual machine.  Select "I copied it".

[[File:Vm4.JPG]]

*Windows XP setup wizard will appear. Follow steps to complete setup.

 

'''*Process must be done on each computer that you log in on to be able to run VMWare.'''

'''*To run multiple VMWare workstations on same computer, make an extra copy of the "B143 B144 VM 3-13-09" folder.'''

'''*Make sure under the "network connections" for the PC you are using, the wireless connection is disabled. Otherwise, VMWare may not run properly.

File:Vm5.JPG

2009-12-16T02:18:05Z

Kalarsford:

VMWare Setup

2009-12-16T02:13:27Z

Kalarsford:

= '''VMware Setup Instructions''' =

'''Step 1:  Locate VMware folder in C:'''

*Click My Computer
*Click on C: drive
*Click on VMWare

 

'''Step 2:  Make a copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on the "B143 B144 VM 3-13-09" folder and select copy

 

'''Step 3:  Paste your copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on an open area in the VMWare folder and select paste.  Process will take 10-15 minutes to complete.

[[File:Vm3.JPG]]

*Rename folder
*Only the user who created this folder will be able to use it

 

'''Step 4:  Open VMWare Workstation'''

*Click Start / All Programs / VMWare
*Click VMWare Workstation

 

'''Step 5:  Open Existing VM or Team'''

*Click on "Open Existing VM or Team"

[[File:Vm1.JPG]]

*Open the folder that you created in Step 3
*Double Click on "Windows XP SP3.vmx"

[[File:Vm2.JPG]]

*Under the "Device" tab make sure the "network adapter" is set to "bridged"

[[File:bridged.jpg]]

*Under "Commands" click on "Power on this Virtual Machine" (next to the green arrow).
*Prompt will ask you if you "moved" or "copied" the virtual machine.  Select "I copied it".

[[File:Vm4.JPG]]

*Windows XP setup wizard will appear. Follow steps to complete setup.

 

'''*Process must be done on each computer that you log in on to be able to run VMWare.'''

'''*To run multiple VMWare workstations on same computer, make an extra copy of the "B143 B144 VM 3-13-09" folder.'''

'''*Make sure under the "network connections" for the PC you are using, the wireless connection is disabled. Otherwise, VMWare may not run properly.

VMWare Setup

2009-12-16T02:06:41Z

Kalarsford:

= '''VMware Setup Instructions''' =

'''Step 1:  Locate VMware folder in C:'''

*Click My Computer
*Click on C: drive
*Click on VMWare

 

'''Step 2:  Make a copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on the "B143 B144 VM 3-13-09" folder and select copy

 

'''Step 3:  Paste your copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on an open area in the VMWare folder and select paste.  Process will take 10-15 minutes to complete.

[[File:Vm3.JPG]]

*Rename folder
*Only the user who created this folder will be able to use it

 

'''Step 4:  Open VMWare Workstation'''

*Click Start / All Programs / VMWare
*Click VMWare Workstation

 

'''Step 5:  Open Existing VM or Team'''

*Click on "Open Existing VM or Team"

[[File:Vm1.JPG]]

*Open the folder that you created in Step 3
*Double Click on "Windows XP SP3.vmx"

[[File:Vm2.JPG]]

*Under the "Device" tab make sure the "network adapter" is set to "bridged"

[[File:bridged.jpg]]

*Under "Commands" click on "Power on this Virtual Machine" (next to the green arrow).
*Prompt will ask you if you "moved" or "copied" the virtual machine.  Select "I copied it".

[[File:Vm4.JPG]]

*Windows XP setup wizard will appear and follow steps to complete setup.

 

'''*Process must be done on each computer that you log in on to be able to run VMWare.'''

'''*To run multiple VMWare workstations on same computer, make an extra copy of the "B143 B144 VM 3-13-09" folder.'''

'''*Make sure under the "network connections" for the PC you are using, the wireless connection is disabled. Otherwise, VMWare may not run properly.

VMWare Setup

2009-12-16T02:06:16Z

Kalarsford:

= '''VMware Setup Instructions''' =

'''Step 1:  Locate VMware folder in C:'''

*Click My Computer
*Click on C: drive
*Click on VMWare

 

'''Step 2:  Make a copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on the "B143 B144 VM 3-13-09" folder and select copy

 

'''Step 3:  Paste your copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on an open area in the VMWare folder and select paste.  Process will take 10-15 minutes to complete.
[[File:Vm3.JPG]]

*Rename folder
*Only the user who created this folder will be able to use it

 

'''Step 4:  Open VMWare Workstation'''

*Click Start / All Programs / VMWare
*Click VMWare Workstation

 

'''Step 5:  Open Existing VM or Team'''

*Click on "Open Existing VM or Team"

[[File:Vm1.JPG]]

*Open the folder that you created in Step 3
*Double Click on "Windows XP SP3.vmx"

[[File:Vm2.JPG]]

*Under the "Device" tab make sure the "network adapter" is set to "bridged"

[[File:bridged.jpg]]

*Under "Commands" click on "Power on this Virtual Machine" (next to the green arrow).
*Prompt will ask you if you "moved" or "copied" the virtual machine.  Select "I copied it".

[[File:Vm4.JPG]]

*Windows XP setup wizard will appear and follow steps to complete setup.

 

'''*Process must be done on each computer that you log in on to be able to run VMWare.'''

'''*To run multiple VMWare workstations on same computer, make an extra copy of the "B143 B144 VM 3-13-09" folder.'''

'''*Make sure under the "network connections" for the PC you are using, the wireless connection is disabled. Otherwise, VMWare may not run properly.

VMWare Setup

2009-12-16T02:05:19Z

Kalarsford:

= '''VMware Setup Instructions''' =

'''Step 1:  Locate VMware folder in C:'''

*Click My Computer
*Click on C: drive
*Click on VMWare

 

'''Step 2:  Make a copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on the "B143 B144 VM 3-13-09" folder and select copy

 

'''Step 3:  Paste your copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on an open area in the VMWare folder and select paste.  Process will take 10-15 minutes to complete.
[[File:Vm3.JPG]]

*Rename folder
*Only the user who created this folder will be able to use it

 

'''Step 4:  Open VMWare Workstation'''

*Click Start / All Programs / VMWare
*Click VMWare Workstation

 

'''Step 5:  Open Existing VM or Team'''

*Click on "Open Existing VM or Team"
[[File:Vm1.JPG]]

*Open the folder that you created in Step 3
*Double Click on "Windows XP SP3.vmx"

[[File:Vm2.JPG]]

*Under the "Device" tab make sure the "network adapter" is set to "bridged"

[[File:bridged.jpg]]

*Under "Commands" click on "Power on this Virtual Machine" (next to the green arrow).
*Prompt will ask you if you "moved" or "copied" the virtual machine.  Select "I copied it".

[[File:Vm4.JPG]]

*Windows XP setup wizard will appear and follow steps to complete setup.

 

'''*Process must be done on each computer that you log in on to be able to run VMWare.'''

'''*To run multiple VMWare workstations on same computer, make an extra copy of the "B143 B144 VM 3-13-09" folder.'''

'''*Make sure under the "network connections" for the PC you are using, the wireless connection is disabled. Otherwise, VMWare may not run properly.

VMWare Setup

2009-12-16T02:04:17Z

Kalarsford:

= '''VMware Setup Instructions''' =

'''Step 1:  Locate VMware folder in C:'''

*Click My Computer
*Click on C: drive
*Click on VMWare

 

'''Step 2:  Make a copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on the "B143 B144 VM 3-13-09" folder and select copy

 

'''Step 3:  Paste your copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on an open area in the VMWare folder and select paste.  Process will take 10-15 minutes to complete.
[[File:Vm3.JPG]]

*Rename folder
*Only the user who created this folder will be able to use it

 

'''Step 4:  Open VMWare Workstation'''

*Click Start / All Programs / VMWare
*Click VMWare Workstation

 

'''Step 5:  Open Existing VM or Team'''

*Click on "Open Existing VM or Team"
[[File:Vm1.JPG]]

*Open the folder that you created in Step 3
*Double Click on "Windows XP SP3.vmx"

[[File:Vm2.JPG]]

*Under the "Device" tab make sure the "network adapter" is set to "bridged"

[[File:bridged.jpg]]

*Under "Commands" click on "Power on this Virtual Machine" (next to the green arrow).
*Prompt will ask you if you "moved" or "copied" the virtual machine.  Select "I copied it".

[[File:Vm4.JPG]]

*Windows XP setup wizard will appear and follow steps to complete setup.

 

'''*Process must be done on each computer that you log in on to be able to run VMWare.'''

'''*To run multiple VMWare workstations on same computer, make an extra copy of the "B143 B144 VM 3-13-09" folder.'''

'''*Make sure under the "network connections" for the PC you are using, the wireless connection is disabled. Otherwise, VMWare may not run properly.

File:Vm4.JPG

2009-12-16T02:02:51Z

Kalarsford:

VMWare Setup

2009-12-16T01:58:58Z

Kalarsford:

= '''VMware Setup Instructions''' =

'''Step 1:  Locate VMware folder in C:'''

*Click My Computer
*Click on C: drive
*Click on VMWare

 

'''Step 2:  Make a copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on the "B143 B144 VM 3-13-09" folder and select copy

 

'''Step 3:  Paste your copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on an open area in the VMWare folder and select paste.  Process will take 10-15 minutes to complete.
[[File:Vm3.JPG]]
*Rename folder
*Only the user who created this folder will be able to use it

 

'''Step 4:  Open VMWare Workstation'''

*Click Start / All Programs / VMWare
*Click VMWare Workstation

 

'''Step 5:  Open Existing VM or Team'''

*Click on "Open Existing VM or Team"
[[File:Vm1.JPG]]
*Open the folder that you created in Step 3
*Double Click on "Windows XP SP3.vmx"
[[File:Vm2.JPG]]
*Under the "Device" tab make sure the "network adapter" is set to "bridged"
[[File:bridged.jpg]]
*Under "Commands" click on "Power on this Virtual Machine" (next to the green arrow).
*Prompt will ask you if you "moved" or "copied" the virtual machine.  Select "I copied it".
*Windows XP setup wizard will appear and follow steps to complete setup.

 

'''*Process must be done on each computer that you log in on to be able to run VMWare.'''

'''*To run multiple VMWare workstations on same computer, make an extra copy of the "B143 B144 VM 3-13-09" folder.'''

'''*Make sure under the "network connections" for the PC you are using, the wireless connection is disabled. Otherwise, VMWare may not run properly.

File:Vm3.JPG

2009-12-16T01:58:01Z

Kalarsford: uploaded a new version of "File:Vm3.JPG"

File:Vm3.JPG

2009-12-16T01:56:30Z

Kalarsford:

VMWare Setup

2009-12-16T01:50:30Z

Kalarsford:

= '''VMware Setup Instructions''' =

'''Step 1:  Locate VMware folder in C:'''

*Click My Computer
*Click on C: drive
*Click on VMWare

 

'''Step 2:  Make a copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on the "B143 B144 VM 3-13-09" folder and select copy

 

'''Step 3:  Paste your copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on an open area in the VMWare folder and select paste.  Process will take 10-15 minutes to complete.
*Rename folder
*Only the user who created this folder will be able to use it

 

'''Step 4:  Open VMWare Workstation'''

*Click Start / All Programs / VMWare
*Click VMWare Workstation

 

'''Step 5:  Open Existing VM or Team'''

*Click on "Open Existing VM or Team"
[[File:Vm1.JPG]]
*Open the folder that you created in Step 3
*Double Click on "Windows XP SP3.vmx"
[[File:Vm2.JPG]]
*Under the "Device" tab make sure the "network adapter" is set to "bridged"
[[File:bridged.jpg]]
*Under "Commands" click on "Power on this Virtual Machine" (next to the green arrow).
*Prompt will ask you if you "moved" or "copied" the virtual machine.  Select "I copied it".
*Windows XP setup wizard will appear and follow steps to complete setup.

 

'''*Process must be done on each computer that you log in on to be able to run VMWare.'''

'''*To run multiple VMWare workstations on same computer, make an extra copy of the "B143 B144 VM 3-13-09" folder.'''

'''*Make under the network connections for the PC you are using, the wireless connection is disabled. Otherwise, VMWare may not run properly.

File:Vm2.JPG

2009-12-16T01:49:42Z

Kalarsford:

VMWare Setup

2009-12-16T01:47:49Z

Kalarsford:

= '''VMware Setup Instructions''' =

'''Step 1:  Locate VMware folder in C:'''

*Click My Computer
*Click on C: drive
*Click on VMWare

 

'''Step 2:  Make a copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on the "B143 B144 VM 3-13-09" folder and select copy

 

'''Step 3:  Paste your copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on an open area in the VMWare folder and select paste.  Process will take 10-15 minutes to complete.
*Rename folder
*Only the user who created this folder will be able to use it

 

'''Step 4:  Open VMWare Workstation'''

*Click Start / All Programs / VMWare
*Click VMWare Workstation

 

'''Step 5:  Open Existing VM or Team'''

*Click on "Open Existing VM or Team"
[[File:Vm1.JPG]]
*Open the folder that you created in Step 3
*Double Click on "Windows XP SP3.vmx"
*Under the "Device" tab make sure the "network adapter" is set to "bridged"
[[File:bridged.jpg]]
*Under "Commands" click on "Power on this Virtual Machine" (next to the green arrow).
*Prompt will ask you if you "moved" or "copied" the virtual machine.  Select "I copied it".
*Windows XP setup wizard will appear and follow steps to complete setup.

 

'''*Process must be done on each computer that you log in on to be able to run VMWare.'''

'''*To run multiple VMWare workstations on same computer, make an extra copy of the "B143 B144 VM 3-13-09" folder.'''

'''*Make under the network connections for the PC you are using, the wireless connection is disabled. Otherwise, VMWare may not run properly.

File:Vm1.JPG

2009-12-16T01:46:31Z

Kalarsford:

VMWare Setup

2009-12-16T01:44:08Z

Kalarsford:

= '''VMware Setup Instructions''' =

'''Step 1:  Locate VMware folder in C:'''

*Click My Computer
*Click on C: drive
*Click on VMWare

 

'''Step 2:  Make a copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on the "B143 B144 VM 3-13-09" folder and select copy

 

'''Step 3:  Paste your copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on an open area in the VMWare folder and select paste.  Process will take 10-15 minutes to complete.
*Rename folder
*Only the user who created this folder will be able to use it

 

'''Step 4:  Open VMWare Workstation'''

*Click Start / All Programs / VMWare
*Click VMWare Workstation

 

'''Step 5:  Open Existing VM or Team'''

*Click on "Open Existing VM or Team"
*Open the folder that you created in Step 3
*Double Click on "Windows XP SP3.vmx"
*Under the "Device" tab make sure the "network adapter" is set to "bridged"
[[File:bridged.jpg]]
*Under "Commands" click on "Power on this Virtual Machine" (next to the green arrow).
*Prompt will ask you if you "moved" or "copied" the virtual machine.  Select "I copied it".
*Windows XP setup wizard will appear and follow steps to complete setup.

 

'''*Process must be done on each computer that you log in on to be able to run VMWare.'''

'''*To run multiple VMWare workstations on same computer, make an extra copy of the "B143 B144 VM 3-13-09" folder.'''

'''*Make under the network connections for the PC you are using, the wireless connection is disabled. Otherwise, VMWare may not run properly.

VMWare Setup

2009-12-16T01:40:52Z

Kalarsford:

= '''VMware Setup Instructions''' =

'''Step 1:  Locate VMware folder in C:'''

*Click My Computer
*Click on C: drive
*Click on VMWare

 

'''Step 2:  Make a copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on the "B143 B144 VM 3-13-09" folder and select copy

 

'''Step 3:  Paste your copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on an open area in the VMWare folder and select paste.  Process will take 10-15 minutes to complete.
*Rename folder
*Only the user who created this folder will be able to use it

 

'''Step 4:  Open VMWare Workstation'''

*Click Start / All Programs / VMWare
*Click VMWare Workstation

 

'''Step 5:  Open Existing VM or Team'''

*Click on "Open Existing VM or Team"
*Open the folder that you created in Step 3
*Double Click on "Windows XP SP3.vmx"
*Under the "Device" tab make sure the "network adapter" is set to "bridged"
[[File:bridged.jpg]]
*Under "Commands" click on "Power on this Virtual Machine" (next to the green arrow).
*Prompt will ask you if you "moved" or "copied" the virtual machine.  Select "I copied it".
[[File:Icopiedit.jpg]]
*Windows XP setup wizard will appear and follow steps to complete setup.

 

'''*Process must be done on each computer that you log in on to be able to run VMWare.'''

'''*To run multiple VMWare workstations on same computer, make an extra copy of the "B143 B144 VM 3-13-09" folder.'''

'''*Make under the network connections for the PC you are using, the wireless connection is disabled. Otherwise, VMWare may not run properly.

VMWare Setup

2009-12-16T01:40:32Z

Kalarsford:

= '''VMware Setup Instructions''' =

'''Step 1:  Locate VMware folder in C:'''

*Click My Computer
*Click on C: drive
*Click on VMWare

 

'''Step 2:  Make a copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on the "B143 B144 VM 3-13-09" folder and select copy

 

'''Step 3:  Paste your copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on an open area in the VMWare folder and select paste.  Process will take 10-15 minutes to complete.
*Rename folder
*Only the user who created this folder will be able to use it

 

'''Step 4:  Open VMWare Workstation'''

*Click Start / All Programs / VMWare
*Click VMWare Workstation

 

'''Step 5:  Open Existing VM or Team'''

*Click on "Open Existing VM or Team"
*Open the folder that you created in Step 3
*Double Click on "Windows XP SP3.vmx"
*Under the "Device" tab make sure the "network adapter" is set to "bridged"
[[File:bridged.jpg]]
*Under "Commands" click on "Power on this Virtual Machine" (next to the green arrow).
*Prompt will ask you if you "moved" or "copied" the virtual machine.  Select "I copied it".
[[File:Icpoiedit.jpg]]
*Windows XP setup wizard will appear and follow steps to complete setup.

 

'''*Process must be done on each computer that you log in on to be able to run VMWare.'''

'''*To run multiple VMWare workstations on same computer, make an extra copy of the "B143 B144 VM 3-13-09" folder.'''

'''*Make under the network connections for the PC you are using, the wireless connection is disabled. Otherwise, VMWare may not run properly.

File:Icopiedit.JPG

2009-12-16T01:39:41Z

Kalarsford:

VMWare Setup

2009-12-16T01:38:24Z

Kalarsford:

= '''VMware Setup Instructions''' =

'''Step 1:  Locate VMware folder in C:'''

*Click My Computer
*Click on C: drive
*Click on VMWare

 

'''Step 2:  Make a copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on the "B143 B144 VM 3-13-09" folder and select copy

 

'''Step 3:  Paste your copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on an open area in the VMWare folder and select paste.  Process will take 10-15 minutes to complete.
*Rename folder
*Only the user who created this folder will be able to use it

 

'''Step 4:  Open VMWare Workstation'''

*Click Start / All Programs / VMWare
*Click VMWare Workstation

 

'''Step 5:  Open Existing VM or Team'''

*Click on "Open Existing VM or Team"
*Open the folder that you created in Step 3
*Double Click on "Windows XP SP3.vmx"
*Under the "Device" tab make sure the "network adapter" is set to "bridged"
[[File:bridged.jpg]]
*Under "Commands" click on "Power on this Virtual Machine" (next to the green arrow).
*Prompt will ask you if you "moved" or "copied" the virtual machine.  Select "I copied it".
[[File:Example.jpg]]
*Windows XP setup wizard will appear and follow steps to complete setup.

 

'''*Process must be done on each computer that you log in on to be able to run VMWare.'''

'''*To run multiple VMWare workstations on same computer, make an extra copy of the "B143 B144 VM 3-13-09" folder.'''

'''*Make under the network connections for the PC you are using, the wireless connection is disabled. Otherwise, VMWare may not run properly.

VMWare Setup

2009-12-10T20:03:13Z

Kalarsford:

= '''VMware Setup Instructions''' =

'''Step 1:  Locate VMware folder in C:'''

*Click My Computer
*Click on C: drive
*Click on VMWare

 

'''Step 2:  Make a copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on the "B143 B144 VM 3-13-09" folder and select copy

 

'''Step 3:  Paste your copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on an open area in the VMWare folder and select paste.  Process will take 10-15 minutes to complete.
*Rename folder
*Only the user who created this folder will be able to use it

 

'''Step 4:  Open VMWare Workstation'''

*Click Start / All Programs / VMWare
*Click VMWare Workstation

 

'''Step 5:  Open Existing VM or Team'''

*Click on "Open Existing VM or Team"
*Open the folder that you created in Step 3
*Double Click on "Windows XP SP3.vmx"
*Under the "Device" tab make sure the "network adapter" is set to "bridged"
[[File:bridged.jpg]]
*Under "Commands" click on "Power on this Virtual Machine" (next to the green arrow).
*Prompt will ask you if you "moved" or "copied" the virtual machine.  Select "I copied it".
*Windows XP setup wizard will appear and follow steps to complete setup.

 

'''*Process must be done on each computer that you log in on to be able to run VMWare.'''

'''*To run multiple VMWare workstations on same computer, make an extra copy of the "B143 B144 VM 3-13-09" folder.'''

'''*Make under the network connections for the PC you are using, the wireless connection is disabled. Otherwise, VMWare may not run properly.

File:Bridged.jpg

2009-12-10T19:56:36Z

Kalarsford:

File:Bridged.JPG

2009-12-10T19:55:23Z

Kalarsford:

VMWare Setup

2009-12-10T19:53:33Z

Kalarsford:

= '''VMware Setup Instructions''' =

'''Step 1:  Locate VMware folder in C:'''

*Click My Computer
*Click on C: drive
*Click on VMWare

 

'''Step 2:  Make a copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on the "B143 B144 VM 3-13-09" folder and select copy

 

'''Step 3:  Paste your copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on an open area in the VMWare folder and select paste.  Process will take 10-15 minutes to complete.
*Rename folder
*Only the user who created this folder will be able to use it

 

'''Step 4:  Open VMWare Workstation'''

*Click Start / All Programs / VMWare
*Click VMWare Workstation

 

'''Step 5:  Open Existing VM or Team'''

*Click on "Open Existing VM or Team"
*Open the folder that you created in Step 3
*Double Click on "Windows XP SP3.vmx"
*Under the "Device" tab make sure the "network adapter" is set to "bridged"
[[File:Example.jpg]]
*Under "Commands" click on "Power on this Virtual Machine" (next to the green arrow).
*Prompt will ask you if you "moved" or "copied" the virtual machine.  Select "I copied it".
*Windows XP setup wizard will appear and follow steps to complete setup.

 

'''*Process must be done on each computer that you log in on to be able to run VMWare.'''

'''*To run multiple VMWare workstations on same computer, make an extra copy of the "B143 B144 VM 3-13-09" folder.'''

'''*Make under the network connections for the PC you are using, the wireless connection is disabled. Otherwise, VMWare may not run properly.

VMWare Setup

2009-12-09T16:11:59Z

Kalarsford:

= '''VMware Setup Instructions''' =

'''Step 1:  Locate VMware folder in C:'''

*Click My Computer
*Click on C: drive
*Click on VMWare

 

'''Step 2:  Make a copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on the "B143 B144 VM 3-13-09" folder and select copy

 

'''Step 3:  Paste your copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on an open area in the VMWare folder and select paste.  Process will take 10-15 minutes to complete.
*Rename folder
*Only the user who created this folder will be able to use it

 

'''Step 4:  Open VMWare Workstation'''

*Click Start / All Programs / VMWare
*Click VMWare Workstation

 

'''Step 5:  Open Existing VM or Team'''

*Click on "Open Existing VM or Team"
*Open the folder that you created in Step 3
*Double Click on "Windows XP SP3.vmx"
*Under the "Device" tab make sure the "network adapter" is set to "bridged"
*Under "Commands" click on "Power on this Virtual Machine" (next to the green arrow).
*Prompt will ask you if you "moved" or "copied" the virtual machine.  Select "I copied it".
*Windows XP setup wizard will appear and follow steps to complete setup.

 

'''*Process must be done on each computer that you log in on to be able to run VMWare.'''

'''*To run multiple VMWare workstations on same computer, make an extra copy of the "B143 B144 VM 3-13-09" folder.'''

'''*Make under the network connections for the PC you are using, the wireless connection is disabled. Otherwise, VMWare may not run properly.

VMWare Setup

2009-12-09T16:09:07Z

Kalarsford: Created page with '= '''VMware Setup Instructions''' = '''Step 1:  Locate VMware folder in C:''' *Click My Computer *Click on C: drive *Click on VMWare '''Step 2:  Make a cop…'

= '''VMware Setup Instructions''' =

'''Step 1:  Locate VMware folder in C:'''

*Click My Computer
*Click on C: drive
*Click on VMWare

 

'''Step 2:  Make a copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on the "B143 B144 VM 3-13-09" folder and select copy

 

'''Step 3:  Paste your copy of the "B143 B144 VM 3-13-09" folder'''

*Right click on an open area in the VMWare folder and select paste.  Process will take 10-15 minutes to complete.
*Rename folder
*Only the user who created this folder will be able to use it

 

'''Step 4:  Open VMWare Workstation'''

*Click Start / All Programs / VMWare
*Click VMWare Workstation

 

'''Step 5:  Open Existing VM or Team'''

*Click on "Open Existing VM or Team"
*Open the folder that you created in Step 3
*Double Click on "Windows XP SP3.vmx"
*Under "Commands" click on "Power on this Virtual Machine" (next to the green arrow).
*Prompt will ask you if you "moved" or "copied" the virtual machine.  Select "I copied it".
*Windows XP setup wizard will appear and follow steps to complete setup.

 

'''*Process must be done on each computer that you log in on to be able to run VMWare.'''

'''*To run multiple VMWare workstations on same computer, make an extra copy of the "B143 B144 VM 3-13-09" folder.'''