Solved WINS has stopped working from Windows 7 to Windows XP

[timxtg]

Hi Everyone

This is a bit of a strange one. At my place of work, most of our computers are on Windows 7 and some are on Windows 10. However, two computers are on Windows XP. (They need to be on XP because of some legacy software which is running on them.)

For some unknown reason, my computer (which is on Windows 7) has stopped being able to resolve the computer names of the Windows XP computers into their IP addresses. So, for example, if I attempt to access a shared folder on \\computernameofwindowsxpcomputer, I get an error message saying "Windows cannot access \\computernameofwindowsxpcomputer" and the error code is 0x80004005. However, if I attempt to access a shared folder on \\ipaddressofwindowsxpcomputer, it succeeds. Also, if I attempt to access a shared folder on \\computernameofwindows7computer, it succeeds. It therefore seems that the WINS on my computer has stopped working with Windows XP computers.

None of the other computers on our network have developed this problem and my computer did not have this problem up until a few days ago.

Does anyone on this forum know the cause and solution to this problem?

Thank you very much.

Kind regards

Tim

 

[iko22]

Hello,

Had you looked in Device Manager? Open Device Manager and select View > Show hidden devices, then navigate down the Device Tree to the Network Adapters node. Especially look for multiple instances of the Microsoft 6to4 adapter. If you find multiple instances, then delete all of these and re-boot the computer.

 

[timxtg]

Hello,

Had you looked in Device Manager? Open Device Manager and select View > Show hidden devices, then navigate down the Device Tree to the Network Adapters node. Especially look for multiple instances of the Microsoft 6to4 adapter. If you find multiple instances, then delete all of these and re-boot the computer.

Hi Iko22

Thank you very much for your reply.

I have clicked on "Show hidden devices" but I can't see any 6to4 adapters.

 

[timxtg]

Hi Everyone

Does anyone have any other possible solutions to this that I can try?

Thank you very much.

 

[samuria]

Can you connect via its IP if so add it to the host file

 

[timxtg]

Can you connect via its IP if so add it to the host file

Hi Samuria

Thank you very much for your reply.

Yes I can but I would prefer to fix the underlying problem properly as opposed to applying a surface fix.

 

[samuria]

Does xp have NetBIOS running and which PC is the master browser

 

[timxtg]

Does xp have NetBIOS running and which PC is the master browser

Yes, the XP machines do have NetBIOS running. I'm not sure what you mean by "master browser". I would be very grateful if you could explain.

Thank you very much.

 

[johnmeyer]

Gosh, I just "necro'd" a thread from years ago in order to post about this exact problem. I did that because, last night, I think I solved it. Here is what I posted in that other thread. Hopefully it will fix your problems. However, you do have a slightly different problem because it sounds like you can get to the XP computers by typing "192.168.1.44" (or similar) by NOT by typing "\\polywellwin7-64". However, try the following and see if it helps.

1. Turn off IPv6 IP protocol in adapter settings. If you have both wireless and wired (on a laptop), do them both. This is, by far, the most important change. (Obviously you need to keep IPv4).

2. Change WORKGROUP name to WORK and then, after it has "taken," change it back to WORKGROUP. This is an ancient bug in Windows, going back to Win98. Doing this forces Windows to rebuild all the references to WORKGROUP.

3. Do NOT create a Homegroup, and if one was created, then make the change to leave it. (I actually don't know why MS created the Homegroup concept.)

4. File sharing connections: change from 128-bit to "40- or 56-bit encryption." This is mandatory.

5. Change the network from Home to Work. This is probably the least important change, and I'm not sure it is needed, so do this one last.

You'll need to re-boot in order for these changes to take effect and, hopefully, cure the problem.

 

[samuria]

When you look for pcs on the network widows doesntsearch for them it asks the master browser for the list if the MB hasnt got it in its database its not found. As a pc comes on line it can take 10+mins for it to register. This scanner often kicks things into life and shows the master browser NetBScanner - NetBIOS scanner

 

[timxtg]

Gosh, I just "necro'd" a thread from years ago in order to post about this exact problem. I did that because, last night, I think I solved it. Here is what I posted in that other thread. Hopefully it will fix your problems. However, you do have a slightly different problem because it sounds like you can get to the XP computers by typing "192.168.1.44" (or similar) by NOT by typing "\\polywellwin7-64". However, try the following and see if it helps.

1. Turn off IPv6 IP protocol in adapter settings. If you have both wireless and wired (on a laptop), do them both. This is, by far, the most important change. (Obviously you need to keep IPv4).

2. Change WORKGROUP name to WORK and then, after it has "taken," change it back to WORKGROUP. This is an ancient bug in Windows, going back to Win98. Doing this forces Windows to rebuild all the references to WORKGROUP.

3. Do NOT create a Homegroup, and if one was created, then make the change to leave it. (I actually don't know why MS created the Homegroup concept.)

4. File sharing connections: change from 128-bit to "40- or 56-bit encryption." This is mandatory.

5. Change the network from Home to Work. This is probably the least important change, and I'm not sure it is needed, so do this one last.

You'll need to re-boot in order for these changes to take effect and, hopefully, cure the problem.

Hi John

Thank you very much for your reply.

I have tried everything you have suggested but unfortunately it has not worked.

When you look for pcs on the network widows doesntsearch for them it asks the master browser for the list if the MB hasnt got it in its database its not found. As a pc comes on line it can take 10+mins for it to register. This scanner often kicks things into life and shows the master browser NetBScanner - NetBIOS scanner

Hi Samuria

Thank you very much for your reply.

I have downloaded NetBScanner and it successfully shows all of the computer names on the network including the XP machines. However, I am still not able to access the XP machines via their computer names. There are two master browsers on the network, my computer and one of the XP machines. My impression is that some aspect of WINS has gone wrong.

 

[iko22]

My impression is that some aspect of WINS has gone wrong.

How to manually recreate a wins database

 

[timxtg]

How to manually recreate a wins database

Hi Everyone

Thank you, Iko22, very much for the link.

I have Managed to solve this problem. It turns out I had the wrong subnet mask. I had 255.255.0.0. I have now corrected it to 255.255.255.0 and I can now access the XP machines via their computer names.

Thank you everyone for your replies.

EDIT: I would be very grateful if other people who have this problem would let me know if this solution solves it.