Koozali.org: home of the SME Server
Obsolete Releases => SME Server 9.x => Topic started by: bas60 on July 23, 2018, 10:29:27 PM
-
Unable to access SME Server 9.2 iBays since 17th July on both Windows 10 and Windows 7
Nothing changed on SME Server side
Today created a NEW iBay with EVERYONE Read Access
Still can't!!
SAMBA issue?
What can I check ?
-
Unable to access SME Server 9.2 iBays since 17th July on both Windows 10 and Windows 7
Clearly you haven't bothered doing the most basic search of the forums.
Please go and have a read and then come back if you have any queries.
-
Clearly you haven't bothered doing the most basic search of the forums.
Please go and have a read and then come back if you have any queries.
I'm sure I haven't researched this extensively
the machine is used as Backup Target - an identical machine was set up so we have 2 system with RAID1
BTW: on the same LAN so same Workstations
The other machine is working OK
I checked SMB1 on Windows 10
Windows 10 update - UNFORTUNATELY... so anything can happen any time :(
checked stored credentials
On 1 Windows 10 I reset the Network stack - no luck
Windows 7 is set NEVER to update (we manually update these once every 3 months)
(On one of the Windows 7 machine - I used Powershell script to FORCE SMB1 but still no luck)
-
I don't think you have looked at all.
Certainly barely need a search.
Look down the list of posts.
You may just notice a few. How about;
Xp/Win 10 problems
W10 will not connect to 9.2 domain
Go to the next page.
SME 9.2 and Win 10
Is it really that hard??
And go read the bug links too.
Sorry, but there is little anyone is going to do to help you if you don't start helping yourself.
-
I don't think you have looked at all.
Certainly barely need a search.
Look down the list of posts.
You may just notice a few. How about;
Xp/Win 10 problems
W10 will not connect to 9.2 domain
Go to the next page.
SME 9.2 and Win 10
Is it really that hard??
And go read the bug links too.
Sorry, but there is little anyone is going to do to help you if you don't start helping yourself.
Hi,
I'm NOT using a Domain - just a basic Samba Share
But YES, I did look at the XP/Win 10 Problems post
I have come across SMBv1.0 issue & have enabled it on Windows 10
Windows 7 - NOT had a problem before
Point to note is the other SME9.2 server - identical setup (restored SME BACKUP before putting any data )
BOTH SME9.2 are on the SAME LAN - BOTH worked 17th - one won't let Windows 7 or 10 connect (NO XP's)
ALL windows computer were able to Backup to BOTH SME 9.2 boxes until 17th
NO update on SME9.2
I setup FreeNAS with CIF's about a month ago.... That seems to work and I'm reconfiguring all my backup to that
only reason for not moving to FreeNAS was backup data to USB is a pain. Backup to another FreeNAS was an option
-
Make sure you read all the threads, bugs and other links.
It isn't just domain logons that can be affected, and it isn't necessarily just SMB v1. Have you looked at the M$ patch mentioned elsewhere?
The next question is what happened on the 17th? Clearly something did.
If you are sure SME wasn't updated then what about the clients? Logically something must have changed on them.
What do your logs tell you? Both Win and SME.
Note as mentioned elsewhere this is not per se a SME problem. It is a M$ Windoze v Linux problem. You are just a sacrificial pawn in a turf war.
-
Windows 7 is set NEVER to update (we manually update these once every 3 months)
I run a LOT of W7/32 machines and they are experiencing no problems so I don't think your issue is related to the plethora of recent posts on NT style domain issues. Additionally since you have two SME servers and one still works it throws out most of the replies you have received.
Have you restarted the malfunctioning SME server?
Can you ping the malfunctioning SME server?
What is the result of running the net view command in a CMD box on the windows machines?