search for: winbound

We've had linux fileservers in our org for a long time and this roughly coincided with version 3.6. Our linux member servers are winbound, filesystems are ext2+ with acl support and permissions assigned to AD groups via setfacl. At any given time, out of all the users that use the fileshares daily there are about 1-2 that get "access denied" by the client os (win xp, 7 and 8). I can log into the linux host, su into the...

...seem good. It would seem like this kind of board would be exactly what was needed to provide a FXO port, assuming it can do full duplex operations, which it should since data calls are full duplex.... The picture isn't quite high enough quality to read the chip specs... It sorta looks likea Winbound or Connexiant silkscreen.... So is that thing a winmodem with a different PCI identifier? -- Ethan (Tele Monster)

On 02/12/14 20:40, steve wrote: > On 02/12/14 21:00, Rowland Penny wrote: >> On 02/12/14 19:51, steve wrote: >>> On 02/12/14 20:30, jacek burghardt wrote: >>>> I recived this: >>>> logonCount: 0 >>>> sAMAccountName: Guest >>>> sAMAccountType: 805306368 >>>> objectCategory:

...then the same verbage about not being authorized. Any ideas what is wrong and/or what to try? Thanks Here are some facts that might help shed light: - wbinfo -u and -g show me the list of users and groups I expect to know of from the MsAD domain MYDOMAIN. - I can ssh into the samba box as a winbound user successfully (i.e. winbind mapped the username's sid to a unix uid and gid; there is no mention of the username in /etc/passwd or /etc/group). - here's the global section of my smb.conf: [global] unix charset = LOCALE workgroup = MSOE realm = MSOE.EDU...