No network provider accepted the given network path - not by name or ip

Howdy,
I officially am throwing in the towel on this one. I have 4 windows 2003 standard servers all running exact same patch levels, hardware, etc. Each server has a primary and secondary interface. There is a primary prodution network and a secondary backup network (10.0.0.x)

Last Sunday 3 stopped being able to talk to the samba server across the backup network but they can still talk to each other. To my knowledge nothing has changed at all. After looking around, trying various solutions on all 3 that are having problems 2 are working again but I honestly don't know what fixed them.

The W2K3KLmhostsTimeout.bat that I find all over the internet didn't work and I am very hesitant to run the svc /scannow. I have tried a bunch of things and searched here as well as googled till I couldn't stand it anymore.

To re-iterate I have 2 Buffalo Terastations that run samba. Only 1 has this issue as all can connect to the other with no problem. As I mentioned 2 of the 3 with issues just started working so I am stuck with 1 that can't reach that device. That device is where my disk backups happen so my server can't be backed up till this is fixed.

Has anyone seen this? I have a strong feeling it's related to netbios or lmhosts but I am pretty ignorant. Also of note it does not connect by name or IP at all on servers when they are wigging out. I can connect to the management interface of the device on port 80 with NO issues at all so I know connectivity exists.

Suggestions?
2drewsAsked:
Who is Participating?
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.

2drewsAuthor Commented:
After stopping work on this issue after posting here I thought and thought and thought about the problem. I sat down and looked very carefully at the advanced TCP/IP Properties and started comparing the different settings. The one server that was still having issues had 1 radio button different than the others.

Under the WINS tab, the "NetBIOS setting" was set to "Disable NetBIOS over TCP/IP" and I changd it to Enable instead and BOOM it all started working. :)
0
NopiusCommented:
heh, the main question why this was working before you changed this radio button?
Anyway you may ask to reclaim points in community support area.
0
2drewsAuthor Commented:
I believe someone else must have made the change but I find it more likely this was the result of a patch or software registration.
0
AnnieModCommented:
PAQed with points refunded (500)

AnnieMod
Cleanup Admin
0

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
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 Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.