Windows Networking 101 and I'm failing the class! Can't ping a win 7 machine by name on the LAN anymore

Seems simple, but I'm stumped.

Network consists of
Linksys router
1 win Vista PC  (Machine name a)
1 Win 7 PC (Machine name B)
1 copier / scanner

for years now, the copier scanner could send scans to either machine (to shares called \\a\scans and \\b\scans).  Now 'something' happened and the scan to the B machine stopped working.

Some checking came up with these things:

From machine A, I can ping the B machine & access shares by IP address ONLY.  Pinging B by name gets 'ping request could not find host B

This I think are key:  2 different errors in the problem machine B system event log:

Source NetBT
Event ID 4321
Message:      
The name "WORKGROUP      :1d" could not be registered on the interface with IP address 192.168.1.116. The computer with the IP address 192.168.1.1 did not allow the name to be claimed by this computer.

and

source NetBT
Event ID 4319
Message:
Message:      
A duplicate name has been detected on the TCP network.  The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state.

Running that command on the problem machine gets:

C:\Windows\system32>nbtstat -n

Local Area Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

    No names in cache

Bluetooth Network Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

    No names in cache

Wireless Network Connection:
Node IpAddress: [192.168.1.116] Scope Id: []

                NetBIOS Local Name Table

       Name               Type         Status
    ---------------------------------------------
    WORKGROUP      <00>  GROUP       Registered
    B                            <00>  UNIQUE      Registered
    B                            <20>  UNIQUE      Registered
    WORKGROUP      <1E>  GROUP       Registered
    WORKGROUP      <1D>  UNIQUE      Registered
    ..__MSBROWSE__.<01>  GROUP       Registered
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

BembiCEOCommented:
I would assume, the Linksys router acts as DHCP, so clients get an IP address from it ??
Maybe its just a try to just shut down all machines, switch of the scanner, reboot the router, wait until the router is up (what can take some seconds, and switch on the machines and scanner again.
This deletes all the local caches and rebuilds them.
JohnBusiness Consultant (Owner)Commented:
Make sure printer/scanner devices are connected by Ethernet (preferably) and have Static IP addresses on your network so they do not get lost on network restart.

Make sure you are using just ONE WORKGROUP. You look like you have two or more. Make sure WORKGROUP on all computers is WORKGROUP.

Read through my article on Folder Sharing to get started.

http://www.experts-exchange.com/articles/16639/Folder-sharing-on-modern-machines.html
ANUPKUMAR NAIRManager IT InfrastructureCommented:
Being a workgroup Network an IP based approach will be better, Hostbased approach is recommended in a network where you have a DNS Server.
TEKDesignCEO/Consultant/OwnerCommented:
I would start by fixing your workgroup names
The name "WORKGROUP      :1d" could not be registered on the interface with IP address 192.168.1.116. The computer with the IP address 192.168.1.1 did not allow the name to be claimed by this computer.

I suggest a unique workgroup name, with no special characters in it, for all your computers (e.g. "MyWrkGp" or "MyNet") to isolate and differentiate your workgroup in the event foreign computers are plugged in to your physical network which can disrupt it.

Once you have your workgroup naming fixed, make sure your network discovery is "on" on all machines and that file sharing using passwords is working. make sure homegroup I snot turned "on" on Win7.

Beyond that using IP addresses as your UNCs may work best as they don't require the network Browser service to be used to resolve the names on each computer which consequentially some times doesn't work right when you have machines fighting for primary network Browser control of the network which can be a common issue on Workgroup networks. This isn't usually a problem on networks with a server on them because the server will usually have DNS and/or WINS running on it with takes care of the network name resolution.

You may also want to make sure that your router has the latest firmware on it and that your computer/device interfaces have unique IP addresses and device names on them so that they are not creating any other conflicts with duplicate names on the network.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
nobusCommented:
you can also try to rename the B PC - and use the new name for pinging
or setup a new user account - and test with that
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 7

From novice to tech pro — start learning today.