I have an old fileserver that has begun selectively accepting connections...  One machine can reach it and a machine next to it seems to not be able to reach it...  Any ideas or thoughts about this?...   very weird
Who is Participating?

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

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.

yo_beeDirector of Information TechnologyCommented:
Have you looked at the event logs for any errors (both on the server and client that is unable to connect)?
That would be one of the first places I would start to look.

While the one that can connect, can you confirm they have a constant connection while the other client that cannot connect is trying?
jorge diazSECommented:
What type of connections are you establishing to the server? http, ftp, smb, etc? I'd start by pinging the server from the computer i can't connect from, if it replies then you move to the application level, is part of domain? is it that you just don't see in the network? If you can't ping it from the computer you have problems from but you can from the other computer then check to make sure you are part of the same network..

that's the basic trobleshooting, post your findings so we'll tell what to do next..

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
DavidAuthor Commented:
Some additional info...
I can ping it from any machine.
SMB I guess..
when I open a folder and type  \\Fileserver and press enter, I usually connect to the machine and am presented with a share I can double click on.
Some machines now get that from it when they try to reach out.
Other machines however - \\fileserver and enter just gets them an error in a box that pops up that says Windows cannot access \\fileserver.

I just perused the event logs and see nothing of consequence that seems to have anything to do with this.

I guess if I can't get this resolved COB today, I'll just build a replacement Fileserver...
I'd just like to avoid that though, even though its a fairly simple job as this system is coming offline in about 6 weeks anyway.

Was hoping for a simple fix...  :-)
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

yo_beeDirector of Information TechnologyCommented:
What if you used the IP address rather than the NetBIOS name?  That may point to DNS as an issue.

Then there can always be hardware issues focused on the NIC.
DavidAuthor Commented:
Final comment - I found that somewhere higher up in the foodchain a GPO was pushed which blocked the SMBv1 on my Windows 2003 server....  So my "selectively" part was associated with when machines were getting the updated policy.  thanks for the help!
yo_beeDirector of Information TechnologyCommented:
Good find.
That maybe the smoking gun.
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 Server 2003

From novice to tech pro — start learning today.