Windows Network Problem Solver

Click here to go to the main article: Windows Network Problem Solver

Below you find the discussion of the main article below. You can participate by adding a new comment or replying to existing comments.

Vote for the main article:

Connections tab in Internet Options (control panel)

Tue, 2013-10-22 18:00 by lcarver

Sometimes the Connections tab is hidden, in the Internet Options / Internet Properties.

I don't know all of the reasons why this may occur, but one culprit is VPN client software (e.g. AnyConnect ).
This is one reference to the issue ... KB 272449

Other references :
AnyConnect 2.5 release notes
Support thread 2016013

NOTE: Sometimes you will find the offending registry value in HKLM ( i.e. local machine ) and sometimes you will find it in HKCU ( i.e. current user ).

For anyone trying to troubleshoot a situation and need to inspect the Internet Properties (and you may find the Connections tab is not there in the usual "control panel" GUI), this is very important to know.
Larry

WINS

Thu, 2010-08-26 12:24 by gwardell

Hi, the Windows Network Problem Solver is a great articla and from what I read really through.

My only comment is that it didn't even mention WINS.

In my case I went through all of the steps and still the Network Palces couldn't list the hosts. Nor would net view work.

But when doing the ipconfig /all I noticed that no WINS server was listed. It should have been. I had recently had to reconfigure my router and had omitted setting the Serve Netbos Name Server. After putting that in I was able to browse the domain and Net View worked again.

I assume that putting the proper IP address into the TCP/IP properties would also work but I'm using DHCP and several machine were affected.

I've never really understood why wins is still needed after moving to Active Directory. Seems rather odd to me.

Rare problem

Thu, 2010-08-26 13:58 by admin

To my knowledge WINS has more or less been replaced by DNS. WINS problems are rarely reported, and few people understand them well.

But if you wanted to write a short text about known WINS problems, symptoms, and solutions, I could tie that into the main article.

Workgroup can not browse internet working prblm only to wireless

Sun, 2010-06-13 09:30 by upalakshitha

Local name resolution not working only for wireless adapter,can ping to local Pc's ip addresses & can access from Ip addresses.internet is working and can ping to out side.no any issue for wired network ,can ping with host pc name and can access local network.i coonet wireless after disable lan connection.reinstall wireless drivers also.Reset Windows Firewall,Reinstall File & Printer sharing Tcp/ip.When i add a local PC name for host file then can ping & access to hostname. Kaspersky is Exit.
I enabled NetBios over TCP/IP also
Workgroup contains 15 PCs ,Windows XP

Selections?

Mon, 2010-06-14 11:02 by admin

What does the Windows Network Problem Solver say in the Selections line (above the three buttons)?

Restoring the network when the workgroup is invisible

Tue, 2010-01-26 16:22 by rickhale24

I have found that my spyware program's registry fixer is corrupting my settings for the network. THe only solution I have found is to right click on "my network places" on "properties" , then right click on my computers LAN or Wireless Connection (depending on how I connect to the network) to properties again, and you will 2 tabs. Within the "general" tab, uninstall both "Client for Microsft Networks" and "File and Printer Sharing", (refuse the 1st restart, but restart after uninstalling the "File and Printer Sharing". After rebooting, repeat the above steps and this time install both "client" and "file sharing" again. and you should see your workgroup again.

Careful with registry cleaners

Tue, 2010-01-26 19:07 by admin

I have yet to see a registry cleaner program that does exactly what it is meant to do. Perhaps registry cleaners are altogether useless, as the registry rarely slows down a computer perceptibly, even if it is full of stuff that is no longer needed. The registry is pretty fast.

"Manage My Network Passwords" missing - learn from my goof

Wed, 2009-10-07 16:07 by Aquinas

I was very confused as to why the "Related Tasks" section, which contains the "Manage My Network Passwrds" was missing when I was trying to save a password for a network connection (aka "Mapped drive). After some head scratching and poking around, I realized I had over-looked fact that one can only manage (i.e., "store") the passwords for the user you are logged in as. Once I logged in as the user whose password I wanted to "manage", things were as expected.

So hopefully someone can benefit from my mistake.

--Get on SoapBox--
This kind of mistake, even though a "user error", further reinforces to me the fact that a program should display all options, and then tell you why you cannot access a particular option, as opposed to just hiding the option from you. Since this design approach will certainly clutter up the user interface, and perhaps confuse novice users, perhaps a compromise of sorts could be reached in that there would be an option to show all disabled options.
Thank you for listening,
--/Get off SoapBox--

Agree

Wed, 2009-10-07 16:24 by admin

I agree entirely. Reality, unfortunately, is different. There is a lot of crap out there, and even companies that have shown quality products often let quality lapse.

Workgroup not accessible (XP)

Mon, 2009-10-05 18:50 by Prius John

My problem has not been solved via this website but still I was impressed by its potential.
Workgroup not accessible can have a lot of causes, one even more complex than the other. In my case I knew what caused it, but I had to find the solution via the internet.
My search started with the string: "Computers near me accidentally deleted" and I found a lot of results.
My computer uses Windows XP as operating system, but some comments said that XP did not have "Computers near me". This may be the case with a new install, but when you upgrade from Windows 2000 to XP it has.
A suggestion of someone to check the Network card properties brought the solution.
The missing "Computers near me" tree in "Entire Network" showed the following symptoms:

  • Workgroup not accessible: My Computer System Properties tab "Computer Name" showed the "Network ID" button grayed out as was "Workgroup" via the "Change" button.
  • Shares and other network computers were not visible as the workgroup was not available
  • The computer where this occurred was accessible from other computers

The solution was: reinstall "Client for Microsoft Networks". This did not bring back "Computers near me" but instead it added "Microsoft Windows Network" to "Entire Network" in "My Network Places" together with the workgroup. This is probable the difference between 2000 and XP. Deleting "Computers near me" caused deletion of the "Client for Microsoft Windows" resulting in in-accessibility of related workgroups.

Interesting problem

Mon, 2009-10-05 19:23 by admin

Thanks for reporting this. It will be helpful for others who stumble into the same problem.

If I remember correctly, in either Windows NT or Windows 2000 there were at least two different Windows networking clients to choose from, and it was not quite clear which one was appropriate for which situation. This also caused a few problems at the time.

Now works in all browsers

Sun, 2009-08-02 12:41 by admin

I have rewritten the Javascript code to make it fully compatible with all browsers, as long as they have Javascript enabled at all.

Technical background

I have removed the old and meager ISKEET library and replaced it first with jQuery and later, after finding jQuery's own problems, with hopefully elegant custom code.

Tested successfully on the latest versions of Internet Explorer, Firefox, and Google Chrome.

If you feel like testing, there are three areas to test:

  1. When a checkbox or button is clicked, i.e. enabled or disabled, a red, small popup should roll down directly to the right, showing the resulting number of hits.
  2. The three buttons should open and close the chapters underneath. A closed chapter is shown as just one line.
  3. Each chapter can be closed and opened individually by clicking on the square symbol with the plus sign to the left of the chapter heading. Directly after that clickable plus sign there should be a relevance number, which appears after any checkbox has been clicked once and then stays there and changes its value according to which checkboxes are checked.

The most difficult part to program initially seemed to be the positioning of the "hits" popup, which was severely browser-dependent. I tried various approaches, but ended up adding click event listeners to all checkboxes and buttons to memorize where the user last clicked, then position the hits popup just to the right of the last-clicked element.

Take Two

Tue, 2009-03-03 22:02 by Urge

Alright, I'm an idiot. I was using Firefox with no script and I disabled it but didn't pay attention to the fact that I needed to be using IE. I'm trying again in IE. I tried the NET USE tool and got this response: System error 1130 has occured. Not enough server storage is available to process this command.

"When the authentication fails, you'd be authenticated as Guest, but the administrative share C$ doesn't allow Guest access, it only allows administrator access, so you can use the C$ share to test administrator access."

This did not let me access computer B(from A) I got the same message as in my original post. I just tried to access comp B from network places, was I supposed to do something different with C$?

"Remember, on Windows XP Professional with Simple File Sharing disabled and using NTFS (New Technology File System) you have to check access rights twice—once for the share and once for folders, files, or printers. The former are set on the share tab; look for the button there. If you have set the object permissions properly, you can simply set the share permissions to Everyone, Full access."

This area is where I might be confused, I'm not sure if I'm setting permisssions in all the right places .

I looked at and tried all the suggestions but still no joy.

Urge

Not enough server storage

Tue, 2009-03-03 22:43 by admin

Why don't you just fill in the form, which asks you specifically for this error message? The page gives you the precise answer.

You could also enter "not enough server storage", including the quotes, into the search box in the top right corner.

not enough human hard drive storage

Wed, 2009-03-04 03:30 by Urge

In my defense I thought the error message "Not enough server storage is available to process this command. Not enough memory to complete transaction. Close some applications and retry." was all one error message. But I do cop to not paying enough attention. Thanks for putting up with my poor performance and helping out cause that fixed it, I can share both ways on all computers now.

Urge

Great

Wed, 2009-03-04 07:25 by admin

Congratulations! Anything that leads to success must be good. (:-)

This is a peculiar problem that keeps cropping up in many networks. That is why the Network Problem Solver page devotes one of the form checkboxes to it.

The general problem is that there are many different causes of networking problems, and so the diagnosis is awkward and time-consuming.

I should make the page Firefox-compatible or perhaps W3C-standards-conformant, but haven't found the time.

WinXP file sharing problems

Tue, 2009-03-03 19:41 by Urge

I have a LAN with 3 computers connected to the internet thru a dsl modem and interconnected with a 5 way switch. Two of the computers are running WinXP PRO SP3 and the 3rd is running A hybrid Win98 OS 98SE2ME. All the computers can see each other, ping each other by ip address and name and see the folders to be shared. Computer A (WinXP) cannot access shared content from computer B (WinXP) but can share files back and forth with computer C (98SE2ME). Computer B can access shared files with A and C. Computer C can share files back and forth with computer A but not with computer B.
When I try to access a shared folder on computer B from computer A I get the following error message: \\comp.B\share is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

Not enough server storage is available to process this command.

When I try to access a shared folder on computer B from computer C I get the following error message:
\\comp B\share is not accessible. not enough memory is available. Quit some programs (I have barely anything running on the C computer). I have 327 MB memory on comp. C, 512 MB memory on comp B and 2 GB memory on comp A.

I went thru the Windows Network Problem Solver (twice) but it was unable to solve my problem. It also didn't display any numbers In front of each headline indicating how helpful any particular section might be or any +/- symbols on the left side to open or close any chapter (although all the chapters were open I believe unless they don't even appear).

I have been thru multiple forums and guides and tried everything (well, maybe not everything or it would be working now). Computer B would seem to be the problem. I installed WinXP on this computer within the last month and other than this networking problem everything seems to be fine. I currently have windows firewall disabled on both WinXP computers and I am not using any other firewall. I have Avira free antivirus running on both WinXP computers (the Windows 98 comp doesn't have any antivirus on it and doesn't go online). I have simple file sharing disabled and I have gone thru the permissions several times but I can't see anything there that would cause this (but I could be wrong). I am totally at a loss for ideas on what to do next. If I've left out any info or missed anything let me know. I would be very greatful for any advice.

Thanks, Urge

What does the first paragraph say?

Tue, 2009-03-03 20:29 by admin

When you open the main article, what does the first paragraph say?

Thanks for Ending our Frustration

Thu, 2009-01-22 07:18 by Scruffy

My father called me to help him fix a problem with his wireless connection.

He was vacationing at a rental home and had been using the internet via their wireless router when he got some sort of virus. After fixing the virus he couldn't get onto the internet any more. At first we thought it was a wireless problem, and spent a long time trying to diagnose it, but after connecting the computer directly to the router, we discovered that his ability to do any networking was gone.

I won't go into all the things we tried, but here are the diagnostics: He couldn't renew his IP address. He could ping localhost, but not anywhere on the internet. The error said he couldn't contact the DHCP server.

We tried repairing Winsock with

netsh winsock reset

--that didn't seem to help.

Then, after setting a restore point for safety, we repaired the IP stack with

netsh int ip reset c:\resetlog.txt

as recommended. That fixed it....he was able to get back on the internet.

Thanks a million for your website and help. We did hours of other diagnostics and attempted fixes (e.g., uninstalling and re-installing the ethernet hardware via Device Manager, various WinXP connection repairs, both wireless and wired, etc.). My father--who is no computer expert--was very frustrated, as was I, trying to help him by phone.

Thanks for helping us solve the problem...my Dad thinks I'm a genius and neither of us have to give up any more hours of our lives on this stupid problem.

(And yes...I blame Bill Gates for this. My father's next computer will be a Mac.)

Thanks for reporting back

Thu, 2009-01-22 07:50 by admin

Good to hear what worked and what didn't work.

Finding out who is to blame is a long and difficult topic. Briefly, my take is that certainly Microsoft could do better, but, like most companies, they are in it for the money and don't do things out of friendliness. We might as well blame ourselves for accepting software flaws too easily.

In your case the immediate cause was probably not any Microsoft software at all, but some nasty piece of third-party software, possibly a virus-like intruder like adware. If so, Microsoft can only be blamed for not writing their operating system, Windows, such that it protects itself better, but that is not part of the current state of the technology, so blaming Microsoft is still a bit far-fetched.

Part of the blame should go to the general state of the software technology, which is not really good. Even with moderate complexity all programmers seem to be unable to produce high quality software. Wherever you look, and Apple is no exception, you find poor design, lots of errors, flaws, weaknesses, lack of orthogonality (two functions work by themselves, but not both together) and, most often, lack of functionality.

That said, Apple computers have their strengths. They are not for me (I have worked on them), but they may be a good choice for users who are not technically oriented and want an easy-to-use computer. Just don't believe that they are free of all those problems. They aren't.

Clarifying the blame game...

Thu, 2009-01-22 18:35 by Scruffy

I ended my comment with a little potshot at Microsoft, and I wanted to just clarify my statement.

I understand that Microsoft probably was not the immediate cause of the problem. Yes, they could build a more robust operating system, and I do have sympathy--thought it's not an excuse--that doing so is a difficult task.

What irks me so much is how relatively un-helpful Windows is in solving these problems. Yes, there are diagnostic tools available that I can learn about--assuming I'm willing to do Google searches and explore various websites and bulletin boards. The fact that I am required to visit numerous non-Microsoft sites to learn and (try to) understand all of these diagnostics, and then run around entering commands in a command window is truly absurd. Almost everything I did in my effort to solve this problem could have been done much easier and faster with the assistance of--or entirely by--Microsoft software.

For example, Windows could easily include a diagnostic that asked a host of questions (like your site) and then applies the IP stack fix after communicating to the user something to the effect of

"There seems to be a DHCP problem. One fix is to repair the IP stack (click here for an explanation). This can cause problems if [blah blah blah] but I can set a restore point so that you can roll back the system if there is a problem. Would you like me to set a restore point and try this fix?"

The fact that my internet search revealed hundreds of pages on the DHCP issue--including pages on this site--illustrates how widespread connection problems are.

The fact that we need sites like this one--and believe me, this site is truly a godsend--is because Microsoft doesn't take the frustrations caused by the OS limitations very seriously. They want to spend time "innovating"--i.e., creating new, flashy, feature-laden products that they can collect revenue for--rather than spend additional money on fixing or developing work-arounds for software problems their users encounter due to OS issues.

(And I haven't even discussed the issue of the dialog boxes. Everyone I know who has had a network problem invariably runs into a situation where they can't "find" a network dialog box they used earlier...because of the unwieldy and obtuse organization of network-related tasks/parameters.)

Generally, I try to give technology companies the benefit of the doubt--what they do is terribly complicated--and there are numerous instances where Microsoft does a good job. However, I think it's perfectly fair to say that Microsoft does not have a corporate culture that expresses concern for the user experience like Apple does. And for that I do blame BIll Gates and the Microsoft management.

OK...I didn't mean to turn this into a rant. I'm off my soapbox.

Again, thanks for your tools and assistance.

Nodding in agreement

Thu, 2009-01-22 21:24 by admin

I find myself nodding in agreement while reading your comment.

Problem solved

Thu, 2008-11-20 19:29 by james random

I have just added a new computer to my home network. I had intermittent problems with the new machine not being able to see any resources on the network or not being able to connect to the workgroup. Also, the new box was only accessible from the network using the IP address (not its host name). I have spent days (on and off) tinkering with network and firewall settings. It would start working and stop again - probably more because it was intermittent than anything else.

The only difference in the setup I could see was that ipconfig /all showed the node type as peer-to-peer. But I couldn't work out how to change this. Until I found your site and solved the problem in a few minutes. Thanks!

(I am guessing that the reason this value was set incorrectly might be because the machine was previously on a large network with a domain server, etc.)

Yes, that is the usual cause.

Thu, 2008-11-20 19:40 by admin

In this case the cause of the problem is a misconfigured WINS server that puts its unfavorable settings into all connected computers.

An old Windows problem, still not generally solved.

Workgroup is not accessible

Thu, 2008-11-13 01:24 by wmicket

I've been working on this problem, on and off, for a while now. I would get this error from my laptop when I connect it to my home network. Other computers on the network would would display the error message: "The network path was not found."

About 5 minutes after finding your site, I had the problem fixed!!

Thanks very much!! (Donation is on its way!!)

Great!

Thu, 2008-11-13 11:52 by admin

Good to hear. Thanks for reporting back.

Home network--access denied

Thu, 2008-07-24 04:18 by cbingham

This web site is great. I have a three-computer home network: #1 WinXP-home, #2 WinXP-Pro, and #3 Win98SE. #1 could access #2 and #3. #2 and #3 could access each other when #1 was powered off, but access was denied to anything on the network when #1 was on, even shared files on the home machine. Your questionnaire helped me determine that the problem was that the IPX protocol was enabled instead of TCP-IP on #1—a remnant of the computer’s previous life on a campus when Novell netware was installed. Thanks so much.

Glad to hear

Thu, 2008-07-24 16:49 by admin

The Windows Network Problem Solver web page was a difficult one-time effort, but since its creation it has helped innumerable users to solve network problems. I still think that this is one good way to go.

Great Help

Wed, 2008-06-04 16:15 by hasanzaboli

One of the best sites i have come across in recent times.

Marvelous job done.

So easy tofollow

Keep the good work going.

Hats of to you

Thanks

Wed, 2008-06-04 18:13 by admin

Good to hear.

Net Use Odditiy

Tue, 2008-05-13 18:18 by 2knights2

Hi,

Very nice compilation of network troubleshooting information. I just wanted to add that I saw a very odd behavior out of the "net use" program today that I've never seen before. When trying to access the C$ share from one XP SP3 machine to another (also XP SP3) I kept getting logon failures (error 1326), despite correct configuration and correct username/password combo.

I finally got it to work by giving the password as a command-line argument to net use, rather than having the program prompt me for the password. Odd! Perhaps it's a bug introduced in SP3; I don't know. At any rate, if you're having problems with net use, try giving the password as an argument. You'll at least be able to visually verify the password is correct and potentially avoid whatever issue I ran into, too.

--Scott

Interesting, thanks!

Tue, 2008-05-13 20:35 by admin

Does anybody else also observe this?

Just a thought—are there perhaps any very special characters in the password?

NetBIOS node type - differences between Solver and my system

Thu, 2008-02-07 09:55 by machekku

Hi, first of all, thanks for saving my problem with wrong NetBIOS node type - great tool!

Now, some comments.
I'm using WinXP Pro SP2, Polish language.
Most probably, node type 2 was set when using my laptop in a network with WINS server. Then I moved to other network without WINS server and the problem occured (local network names could not be resolved).

First of all, ipconfig /all did not show my node type (or it is translated in a very strange way and I couldn't find it).
Second thing, After I changed DhcpNodeType in registry by hand from 2 to 1 and used "Repair" button in connection status dialog, problem was solved. Without restarting!

Thanks again for help!

Thanks!

Thu, 2008-02-07 11:33 by admin

I don't know why ipconfig /all didn't show the NetBIOS node type.

Thank you for the hint that rebooting is not needed after changing the value. I think it should work also when removing the value, then repairing the connection.

I have changed the web page accordingly. As an early contributor you now have your own blog on this web site. Please have a look into the "Blogger" forum for details.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.