ass#3

Answer #1.
To install and configure the TCP/IP network protocol on Windows 2000, Windows XP, and Windows Server 2003:
1. Click Start –>Settings –>Control Panel.
2. On the control panel, double-click Network and Dial-Up Connections.
3. Right-click Local Area Connection.
4. Click Properties.
Note:
If Internet Protocol (TCP/IP) does not appear in the list, do the following:
a. Click Install.
b. Select Protocol, and then click Add.
c. Select Internet Protocol (TCP/IP).
d. Click OK. This returns you to the Local Area Connection Properties window.
5. Select Internet Protocol (TCP/IP), and then click on Properties.
6. Select Using the Following IP Address.
Note:
Check with your network administrator to determine the correct settings for this tab. If your PC does not automatically obtain IP and DNS addresses, do the following:
o Enter the IP address of your PC (for example, 199.5.83.205).
o Enter the subnet mask (for example, 255.255.255.0).
o Enter the default gateway (for example, 199.5.83.1).
o Enter the preferred DNS server (for example, 199.5.100.75).
o Enter the alternate DNS server (for example, 199.5.100.76).
7. If you are using a Windows Internet Name Server, click the Advanced tab, select WINS Address, and do the following:
. Click Add .
a. Enter the primary WINS server (for example, 199.5.83.205).
b. Enter the secondary WINS server (for example, 199.5.83.206).
c. The remaining settings should remain as the defaults.
8. Click OK on the Local Area Connection Properties window. It is not necessary to restart your PC.
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/rzaij/rzaijw95tcp.htm
Answer #2.

The following are steps to resolve, or at least isolate the source of common issues. Assume nothing; go through each step so you can check it off the list.
.
Network Connectivity Problems
1. Check the Lights

Does the NIC have a link? Check the NIC link light and then make sure the OS is also aware of the link by going into the Network and Dial-up settings, right click on the link and select Status. The number of packets received should be about the same as the number of packets sent; if not, then you are not receiving traffic from the LAN.

Does the switch have a link? Go to the switch or log in to the management console and verify that the switch is also aware of the link.
2. IP Troubleshooting

Run ipconfig /all to find your current IP.

If your IP starts with 169.x.y.z this IP has been auto-selected by Windows because the system cannot successfully connect to a DHCP server. A client with a 169.x.y.z address will be unable to do anything until it receives a real IP address.

DHCP Enabled: Yes or No? If yes, do you have an valid IP address, subnet mask, and default gateway? If you do, skip to Link Troubleshooting. If not, enable DHCP and run ipconfig /renew.

Make sure the DHCP server has addresses to hand out and that the service is running.

DHCP Enabled: No, is your IP address valid on the network? Ping the default gateway. If the ping fails, it is most likely because the subnet mask is wrong or the IP address is conflicting with another device. Check the subnet mask and try another IP.
3. Link Troubleshooting

If there is still no link, go into the NIC configuration and make sure it is set to Auto negotiate. If the NIC is already set to auto negotiate and there is no link, try changing the link speed to 100/Full, 10/Full, 100/Half, 10/Half.
4. Still no link? Call support; you have a real issue.
Internet Connection Problems
1. You have an IP address, right? Run ipconfig /all just to be sure, then ping the default gateway. If you cannot ping the default gateway, go back to the link troubleshooting section.
2. If you can ping the gateway but cannot access any websites, run tracert IP address of an external system -d to verify that IP routing is occurring. Do not use a DNS name, use an IP address since you may be having DNS problems. If the tracert dies after a few hops, your upstream connection may be down, run tracert against another host. When that fails, call your ISP.
3. If the tracert to an IP works, but you still cannot browse the web, sounds like a DNS problem. Run nslookup and query for the FQDN that you are trying to connect to, try a few other common sites like Google.com, MSN.com, or CNN.com. If those queries are working, restart your system, restart the firewall and/or router, and try again to connect.
4. Still nothing? Call the experts.
http://www.esxinc.com/ESX/Basic-Troubleshooting.asp?SnID=2