![]() Would demonstrate whether DHCP service is what is failing from client side. If using DHCP, you could ping out and select an open IP, and set this as static for testing purposes. ![]() Also good to double-check whether you are using DHCP or static IP, correct subnet and gateway, and DNS. If you have access to a USB NIC adapter, you could add this as a secondary connection to verify whether network channel is viable. I have seen low cost HP laptop be unplugged while live, and then never connect until the "soft" configuration of onboard NIC is dumped and recreated. If you have viable connection to the NIC, next step might be to delete and recreate the network configuration. Since most network problems tend toward connectivity, I would start here and then move into drivers, client configuration, etc. crossover works from auto-negotiate connection but not on basic switch/hub) ? Do you have connect and activity indication on the NIC backplane? Is this connecting to wall jack or to a switch? Does the switch point auto-negotiate (i.e. ![]() Simple check on connectivity side might be test the PC with several different cables known good elsewhere. Remember that network connect relies on the component parts for Adaptor/driver, Client, and binding plus connectivity. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |