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?
jorge diazConnect With a Mentor SECommented:
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..
yo_beeConnect With a Mentor Director 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?
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...  :-)
Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

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

All Courses

From novice to tech pro — start learning today.