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
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
Then there can always be hardware issues focused on the NIC.
ASKER
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!
Good find.
That maybe the smoking gun.
That maybe the smoking gun.
ASKER
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... :-)