initial 'identifying - no internet access' problem now 'failed to access NetBT driver'

mickl01

Honorable
Nov 20, 2012
7
0
10,510
I have two desktop computers (W7) wired to a DSL 3780 (D link router). I also have a laptop computer accessing the router wireless. All working fine for many months until last week. One of the desktops could not access the internet, constantly trying to identify the router. The network adaptor was set at automatically obtaining an IP. After lots of browsing, I decided to set it up to a static IP address (192.168.1.6), with the gateway as (192.168.1.1). This solved the problem of internet access. Now on that computer I can see the other computers, but I cannot access the shared files. Also the router has a USB port which I have attached a hard drive as a central store. The desktop cannot see the router. The other computers are functioning as normal, they see everything and can access each others shared files, but cannot access the desktop with the problem. I have set the enable 'NetBIOS over TCP/ip', but when I run 'ipconfig/all' from the dos prompt it shows the NetBIOS over tcpip to be disabled. Also trying 'nbtstat -RR' shows 'failed to access NetBT server'. I have browsed lots of sites and checked that the required Services.msc are running. I use Microsoft Essentials/Windows Firewall. Suspecting a virus carried out a complete scan/ ran Spybot 2/Malwarebytes. Problem still there. Any ideas?
 
The only change to the other wired network computer is that is obtaining its IP address automatically. If I change it to a static (192.168.1.4), it works correctly.
 
What I am saying is I have one computer working and one not. They both had the same settings. One then came up with a problem 'identifying', which I overcame with changing it's settings to a static IP, but that has now given another problem of not accessing network devices.
 
How about I try this from a different route. Ignore the second problem. I have two computers, both on W7 accessing the same router. Both set at obtaining IP address automatically. Why is one jamming up at identifying the network and the other works perfect?
Where is the faulty one getting it's automatic IP address from?
 
If I go to 'Change advanced sharing settings' in the 'Network sharing centre. The 'network discovery' is turned off. If I change this to 'on' and save the changes, nothing happens. When I go back to the sharing settings it has reverted back to off. Seems the same as setting NetBIOS over TCPIP problem. Something is over-riding these settings.
 
Thanks scout_03 for your efforts. The machine in question is doing lots of funny things. It has 'lost' system restore points, so my only option is a complete re install. Clean windows 7 works fine, now going to add other software.