Windows 8 and 8.1 Forums

Unrepairable TCP/IP?

  1. #1


    Posts : 13
    Windows 8.1

    Unrepairable TCP/IP?


    At first, some simplified introduction.

    I have two laptops, one with Windows 7 and another with Windows 8.1 connected via Ethernet. I gave the first one IP 192.168.10.1 and 192.168.10.2 to the second one. This connection is shown as Unidentified network on both of them.

    When I ping
    192.168.10.2 from 192.168.10.1, I get Request timed out. The interesting thing is that on 192.168.10.2 in the connection status, the number of received bytes grows about the same amount (usually the same 296 bytes though it differs sometimes) as the number of sent bytes on 192.168.10.1 the moment I ping. And the number of sent bytes on 192.168.10.2 grows on 42 bytes while it's 60 for received on 192.168.10.1.

    When I ping 192.168.10.1 from 192.168.10.2, I get General failure. In fact, I always get General failure regardless of what I ping, even 127.0.0.1. And in these cases, the numbers of sent and received bytes do not change.

    Possibly worth noticing another thing, I'm not sure. When Default gateway is not defined, pinging address from another subnet like 192.168.1.1 gives "PING: transmit failed. General failure." unlike just "General failure" in the cases above.


    From Network Posting Tips:
    ipconfig /all
    Code:
    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : u38dt
       Primary Dns Suffix  . . . . . . . : 
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
    
    Ethernet adapter Ethernet:
    
       Connection-specific DNS Suffix  . : 
       Description . . . . . . . . . . . : ASIX AX88772B USB2.0 to Fast Ethernet Adapter
       Physical Address. . . . . . . . . : 9C-EB-E8-0F-2C-BA
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.10.2(Preferred) 
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Resetting TCP/IP & Flush DNS
    Hosts file hasn't changed since before the laptop was bought and was working properly, so nothing interesting there.
    Code:
    D:\>ipconfig /release 
    
    Windows IP Configuration
    
    The operation failed as no adapter is in the state permissible for 
    this operation.
    
    D:\>ipconfig /renew 
    
    Windows IP Configuration
    
    The operation failed as no adapter is in the state permissible for 
    this operation.
    
    D:\>ipconfig /flushdns 
    
    Windows IP Configuration
    
    Successfully flushed the DNS Resolver Cache.
    
    D:\>netsh winsock reset all 
    
    Sucessfully reset the Winsock Catalog.
    You must restart the computer in order to complete the reset.
    
    D:\>netsh int ip reset all 
    Resetting Global, OK!
    Resetting Interface, OK!
    Resetting Unicast Address, OK!
    Resetting Neighbor, OK!
    Resetting Path, OK!
    Resetting , failed.
    Access is denied.
    
    Resetting , OK!
    Restart the computer to complete this action.
    "Access is denied", as I have found on the Internet, is about registry node HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nsi\{eb004a00-9b1a-11d4-9123-0050047759bc}\26. When I enabled Full Controll permission for this node, I got this:
    Code:
    D:\>ipconfig /release 
    
    Windows IP Configuration
    
    The operation failed as no adapter is in the state permissible for 
    this operation.
    
    D:\>ipconfig /renew 
    
    Windows IP Configuration
    
    The operation failed as no adapter is in the state permissible for 
    this operation.
    
    D:\>ipconfig /flushdns 
    
    Windows IP Configuration
    
    Successfully flushed the DNS Resolver Cache.
    
    D:\>netsh winsock reset all 
    
    Sucessfully reset the Winsock Catalog.
    You must restart the computer in order to complete the reset.
    
    D:\>netsh int ip reset all 
    Resetting Global, OK!
    Resetting Interface, OK!
    Resetting Unicast Address, OK!
    Resetting Neighbor, OK!
    Resetting Path, OK!
    Resetting Route, OK!
    Resetting , OK!
    Restart the computer to complete this action.
    Either case did not solve the problem.

    I tried sfc /scannow:
    Code:
    Beginning system scan.  This process will take some time.
    
    Beginning verification phase of system scan.
    
    Verification 0% complete.
    [...]
    Verification 100% complete.
    
    Windows Resource Protection found corrupt files but was unable to fix some 
    of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For 
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not 
    supported in offline servicing scenarios.
    Log is attached. I couldn't find anything useful out of it but that's me.
    I tried dism as well but it did not work out. Either the case is too bad or I am too lame and need assistance. I really hope it's the latter.

    Please, help me figure this thing out.
    Thanks everyone of you in advance.

    P.S. I have got no backups prior the begining of this problem. And reinstalling Windows is the last thing I will do.
    P.S.S. This thread is refined version of Unidentified network with No internet access that was focused on another thing and led nowhere.


    Update:
    Forgot to mention, the firewall is disabled, the antivirus is uninstalled, safe mode with network is also affected by the problem.
    Unrepairable TCP/IP? Attached Files

      My System SpecsSystem Spec

  2. #2


    Central IL
    Posts : 3,468
    Linux Mint 17.2


    Your problem is because the IP's for the computers are outside of the IP range of the router. Simple fix. Let the router assign the proper IP's.
      My System SpecsSystem Spec

  3. #3


    Posts : 13
    Windows 8.1


    This is a PC-PC network, without router.
    And how come all these General failures, even for 127.0.0.1 on one of the PC's, just because of IP's being out of some range?
      My System SpecsSystem Spec

  4. #4


    So, you say this is a pc to pc network connection with no router...then did you use a cross over cable to connect the two pcs? I fnot, there is your problem. To network to pcs without a router, you will need to use a cross over cable so they can talk to each other.
      My System SpecsSystem Spec

  5. #5


    Central IL
    Posts : 3,468
    Linux Mint 17.2


    Quote Originally Posted by lesge View Post
    This is a PC-PC network, without router.
    And how come all these General failures, even for 127.0.0.1 on one of the PC's, just because of IP's being out of some range?
    127.0.0.1 is the Localhost IP. With no router, it is like trying to drive a car without a motor or any gas in it.
      My System SpecsSystem Spec

  6. #6


    Posts : 13
    Windows 8.1


    Quote Originally Posted by play2mefish View Post
    So, you say this is a pc to pc network connection with no router...then did you use a cross over cable to connect the two pcs? I fnot, there is your problem. To network to pcs without a router, you will need to use a cross over cable so they can talk to each other.
    I haven't seen the need of doing a crossover cable while connecting PCs in ages. But whatever, minus a couple of minutes and one connector, and I got the same result.

    Quote Originally Posted by broe23 View Post
    Quote Originally Posted by lesge View Post
    This is a PC-PC network, without router.
    And how come all these General failures, even for 127.0.0.1 on one of the PC's, just because of IP's being out of some range?
    127.0.0.1 is the Localhost IP. With no router, it is like trying to drive a car without a motor or any gas in it.
    Strange, on the other laptop I can drive that car even when ALL network adapters are disabled. And as far I as remember I have always been able to do that. Moreover, Wikipedia says
    The processing of any packets sent to a loopback address is implemented in the link layer of the TCP/IP stack. Such packets are never delivered to any network interface controller (NIC) or device driver, which permits testing of software in the absence of any hardware network interfaces.
    ...
    Any IP datagram with a source or destination address set to a loopback address must not appear outside of a computing system, or be routed by any routing device.
    Or we can even refer to the standard.
      My System SpecsSystem Spec

  7. #7


    Central IL
    Posts : 3,468
    Linux Mint 17.2


    If you are not using a router. You need a Cross-Over cable between the two PC's. With that, you would have to enable ICS (Internet Connection Sharing. So that the computers get assigned by Windows the proper IP's.

    Again, what you are doing and how you are doing. You are just going to be running around in circles. Suggest you use a router and skip this whole nonsense of trying to connect two PC's together with a Cross-Over Cable.
      My System SpecsSystem Spec

  8. #8


    Posts : 13
    Windows 8.1


    Quote Originally Posted by broe23 View Post
    If you are not using a router. You need a Cross-Over cable between the two PC's. With that, you would have to enable ICS (Internet Connection Sharing. So that the computers get assigned by Windows the proper IP's.
    As stated in the previous post, I made the cable a crossover. ICS is about sharing Internet, I am about simplest LAN, or, actually, about the specific PC with specific Windows.

    Quote Originally Posted by broe23 View Post
    Again, what you are doing and how you are doing. You are just going to be running around in circles. Suggest you use a router and skip this whole nonsense of trying to connect two PC's together with a Cross-Over Cable.
    No, this is exactly opposite of what I am doing. I am not trying to build a home network with Internet and stuff. I have it. And also I've got a problem with Windows on my laptop. And now I am disassembling this problem to find the source of it. I kind of found it, using, as well as others, that simple use case described in the first message. And I want to fix this problem however all I have tried did not help. And this primitive use case is supposed to help those who read this thread to understand what is going on.
      My System SpecsSystem Spec

  9. #9


    Central IL
    Posts : 3,468
    Linux Mint 17.2


    I have stated enough, but you are going to just insist on doing it your way. There is no disassembling to figure it out. There is no problem, other than you the end user, does not understand how ICS between two computers with a Cross-Over cable works. End of story
      My System SpecsSystem Spec

  10. #10


    Posts : 13
    Windows 8.1


    Quote Originally Posted by broe23 View Post
    I have stated enough, but you are going to just insist on doing it your way. There is no disassembling to figure it out. There is no problem, other than you the end user, does not understand how ICS between two computers with a Cross-Over cable works. End of story
    Yes, thank you broe23, I appreciate your time and attention. It would come out even better if only you weren't refusing to listen to my point.
      My System SpecsSystem Spec

Page 1 of 2 12 LastLast
Unrepairable TCP/IP?
Eight Forums Android App Eight Forums IOS App Follow us on Facebook