|What part of "The reason I mentioned the TCP/IP stack is because I suspect that might be the issue based on the the description you provided of what is happening." are you not understanding??????????|
Any way on the other hand I have reset both "cmd- intsh int and winsock catalog.
Good for you. However, that's not what I told you to do is it.
This has not solved the problem.
I'm not surprised and I could have told you neither would work which is why I didn't mention doing that.
I ran SFC /scannow, it paused at several things, however, I do not have any of the original CD's to insert.
Again, good for you. However, SFC is not going to fix the issue. You'll notice I didn't mention running SFC in any of my responses either. There's a reason for it. That reason being, I know it won't fix your issue.
Now, whether or not you understand my plain English answer to your repeated question about the TCP/IP stack, try doing what I said. I'm going to repeat myself (which I hate) and this is the very last time I'm going to attempt to help you since your obtuseness is frustrating me and I'm finished with you as of completing this response:
1) Uninstall the TCP/IP stack, reboot your computer, reinstall the TCP/IP stack and reboot if necessary. Test DHCP
2) If #1 does not fix the issue, go into Device Manager and uninstall the network interface, reboot and reinstall the interface. After reinstalling it, ensure you have the most recent and up-to-date drivers for the device.
It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.