Rebuilding and Bridges
For : Microsoft Windows
by : je.saist
| This guide covers two problems that may be encountered while
working with the TCP/IP Stack of Windows based Operating Systems. First
if the rebuilding of a the TCP/IP stack, the second covers Network
Bridges. Rebuilding the TCP/IP Stack In Windows NT Rebuilding the TCP/IP Stack is
just about the last step that can be taken at the Tier I level to solve
connection problems before escalating a call to Tier II. This can be
done if the CU is pulling an invalid IP address, or is pulling a
169.x.x.x ip address after the other techniques for addressing a 169
error have been completed. However, if the customer is pulling a
169.x.x.x ip address, do ensure that the hardware is working by making
sure the computer does recieve a Media
State Media Disconnected Error when the modem is not plugged
into the computer.
1: Click on start
2: Click on Control Panel 3: By this time the computer's control panel should be in classic view for Windows XP. If it is not, get in classic view. 4: Double click on Network Connections 5: Right click on the affected local area connection 6: Once in the local area connection properties, uncheck all the boxes that are listed for the connection. 7: These will include, but may not be limited to A: Client for Microsoft Networks
B: File and Printer Sharing for Microsoft Networks C: Internet Protocol (TCP/IP) D: QoS Packet Scheduler 8: Once the boxes are unchecked,
hit OK
9: Turn the computer off 10: Unplug the power cord to the cable modem. 11: Turn the computer back on 12: Leave the modem unplugged 13: When the computer loads, go back to the control panel 14: Go back to Network Connections 15: Right click again on the Local Area Connection 16: Put checks back in all of the boxes. 17: Hit Ok 18: Turn the computer off 19: Plug the modem back in 20: Turn the computer back on when the modem has connected 21: Click on Start 22: Click on run 23: type in cmd 24: Type Ipconfig into the Dos box 25: Obtain connection information. The customer will probably ask
what was the point of attempting this series of steps. The following
explanation can be offered.
Explanation: The Microsoft Windows Operating System uses the TCP/IP stack released under the BSD license, developed by Berkley University. When troubleshooting this TCP/IP stack, one of the tricks available to to remove the stack from the Windows Operating System, recreate the TCP/IP stack, and allow Microsoft Windows to treat the TCP/IP stack as a new connection. While not the same as reinstalling drivers for a device, doing so may allow Microsoft Windows to compensate for or overright errored data that may have been preventing a valid connection. The point of leaving the modem unplugged is to make sure that the computer does not attempt to assign an address right after the creation of the TCP/IP stack. In other words, we want Microsoft Windows to build the TCP/IP connection without relying on legacy data that may possibly still be in the system. Plugging the modem back in before turning the computer on after rebuilding the stack should allow for the computer to continue to treat the connection as a new device, and therefor allow a connection to be established. If the computer still is pulling a 169 though, there are little things left that can actually be addressed aside from a problem at the code level of the Microsoft Windows Operating System.. Rebuilding the TCP/IP Stack in Windows 9X To Be Completed Network Bridges To be Completed  |