Avatar of David
DavidFlag for United States of America asked on

Fileserver

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
Windows Server 2003

Avatar of undefined
Last Comment
yo_bee

8/22/2022 - Mon
SOLUTION
yo_bee

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
ASKER CERTIFIED SOLUTION
Jorge Diaz

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
ASKER
David

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...  :-)
yo_bee

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

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!
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
yo_bee

Good find.
That maybe the smoking gun.