similar to: firefox update

Displaying 20 results from an estimated 7000 matches similar to: "firefox update"

2020 Mar 18
2
vnc kde emacs redraw issue
Does anyone have access to the following that could help me with the issue I am having trying to use kdrc with vnc and emacs. VNC redraw issues with emacs on KDE https://access.redhat.com/solutions/1585893 I can't access the portal since I am using CentOS. -- Stephen Clark Email Confidentiality Notice: The information contained in this transmission may contain privileged and confidential
2020 Mar 18
2
vnc kde emacs redraw issue
On 03/18/2020 09:19 AM, Jyrki Tikka wrote: > On Wed, 2020-03-18 at 07:31 -0400, Steve Clark wrote: >> Does anyone have access to the following that could help me with the >> issue I am having trying to >> use kdrc with vnc and emacs. >> VNC redraw issues with emacs on KDE >> https://access.redhat.com/solutions/1585893 >> > There is a workaround: > >
2020 Jan 16
4
Need info on adobe flash player plugin 32 for CentOS7
On 01/16/2020 03:30 PM, Chris Adams wrote: > Once upon a time, Kay Schenk <kay.schenk at gmail.com> said: >> I kept getting messages that my old Flash Player 31 was obsolete so >> I went in search of an update. > Adobe stopped releasing Flash for Linux a while back. IIRC the only > "supported" Flash on Linux is distributed as a part of Google Chrome > (and
2015 Dec 02
0
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
Great thanks, I'll start digging into that. So your running theory is that one of the DNS resolution attempts is returning .WINDOWS not . WINDOWS.CORP.XXX.com? On Wed, Dec 2, 2015 at 10:07 AM, mathias dufresne <infractory at gmail.com> wrote: > OK, sorry, I haven't re-read the whole thread carefully enough. > From what I understand sometimes your DNS request are truncated,
2015 Dec 02
0
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
All the DNS stuff checks out. The names resolve as they should (They pass all checks Mathias suggested). They all give the exact same answers. hostname -A is showing correctly. I nuked the boxed and reinstalled. Same problem. It simply won't request the ActiveDirectory SRV records from WINDOWS.CORP.XXX.COM, it requests them from WINDOWS and is disappointed when there isn't any DNS setup
2015 Dec 02
0
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
Dnsmasq is not running locally! Disabling it would do nothing but stop DHCP and DNS forwarding for 2000+ soon to be irate people. What I am going to do however is bypass DHCP completely and assign a static address with DNS pointed straight at active directory. If that still doesn't work, I think I can definitely narrow this down to a bug in Active Directory, our AD configuration, or a bug in
2020 Feb 13
2
Monitor email for office365.com with fetchmail
I am trying to use fetchmail to monitor box in office365.com. Its not working. Is there a "better" way to monitor and inbox ? I have verified all the ports are open, using 993, using ssl, using sslproto SSL3 etc.. Anyone done this ? Got it working. I basically have: machine outlook.office365.com login myuser at mydomain password mypassword fetchmail --ssl --sslproto SSL3 --smtpname
2015 Dec 09
1
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
Here's a random question... would it matter if our domain has trust relationships setup? *Jonathan S. Fisher* *VP - Information Technology* *Spring Venture Group* On Wed, Dec 9, 2015 at 9:34 AM, mathias dufresne <infractory at gmail.com> wrote: > Hi Jonathan, > > You wrote: > domain windows.corp.springventuregroup.com > search windows.corp.*pringventuregroupcom* >
2015 Dec 12
2
Nested Group control doesn't work
Hey guys, We can perform this LDAP query against Windows Server 2012 no problem, but against samba it's failing: (&(sAMAccountName={0})(memberOf:1.2.840.113556.1.4.1941:=CN=graylog_users,OU=Applications,OU=Groups,DC=ad,DC=corp,DC=xxx,DC=com)) Is that "nested group" tree control (memberOf:1.2.840.113556.1.4.1941:) supported? If not, is there a better way to design this ldap
2006 Jun 29
0
Mainpine OCTO+ and CentOS v4
I've been having a problem with getting a Mainpine OCTO+ working on CentOS Version 4. I know at some point I'll have to recompile the kernel in order to access all 8 ports but something is still not right. Wvdialconf almost every will id all of the ports. All too often it can fine the modem on at least half the ports on the board. I'm starting to hear that something is not right on V4
2015 Dec 03
0
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
>unless you explicitly set your site name when you provision I guess we didn't. Is that an issue? I still wonder why that says "null" when, even if we used the default, our sitename is not null. > well it obviously isn't working your way To be sure, I took a packet capture. It shows the DNS is going straight to the DCs, so in reality it is working the way you are
2015 Dec 14
1
Nested Group control doesn't work
Thanks, that's extremely helpful. I searched but wasn't able to find that bug report.... Just to clarify, there are no known workarounds, correct? *Jonathan S. Fisher* *VP - Information Technology* *Spring Venture Group* On Sat, Dec 12, 2015 at 10:06 PM, Andrew Bartlett <abartlet at samba.org> wrote: > On Sat, 2015-12-12 at 10:25 -0600, Jonathan S. Fisher wrote: > > Hey
2015 Dec 02
2
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
On 02/12/15 16:27, Jonathan S. Fisher wrote: > Great thanks, I'll start digging into that. So your running theory is that > one of the DNS resolution attempts is returning .WINDOWS not . > WINDOWS.CORP.XXX.com? This is not your problem. Rowland > > On Wed, Dec 2, 2015 at 10:07 AM, mathias dufresne <infractory at gmail.com> > wrote: > >> OK, sorry, I
2015 Dec 03
0
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
Rowland, I hear and understand you loud and clear. If you could point out below what is the problem, because the client seems to be configured correctly as you have asked: root at freeradius:~# nslookup 192.168.127.131 Server: 192.168.127.131 Address: 192.168.127.131#53 Non-authoritative answer: 131.127.168.192.in-addr.arpa name = whiskey.windows.corp.XXX.com. Authoritative answers can be
2015 Dec 01
0
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
>It isn't running, one of the first things I do when setting up a new DC is to remove nscd if it is installed. Ah ok... well this isn't a DC, just a member... is NSCD ok to run as a member? Otherwise I can remove it. > you get a caching dnsmasq server as standard Not on ubuntu server... There is no dnsmasq package installed nor is it in ps -ef > If you have to have that
2015 Dec 03
0
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
It doesn't work, even with the DNS set as such: root at freeradius:~# sudo net rpc info -UWINDOWS\\Administrator Unable to find a suitable server for domain WINDOWS Our registered domain is XXX.com. corp.XXX.com and windows.corp.XXX.com are internal and not resolvable on any public DNS server. I was curious if anyone else had any comments on these two questions I had: * What is this
2006 Jul 11
1
Building a new 2.6 kernel
I needed more serial ports that the basic CentOS Version 4 system is built to use so I'm using the following kernel build instructions to build the new 2.6 kernel: http://www.hylafax.org/content/Handbook:Basic_Server_Configuration:Modem-speci fic_Guidance I believe the procedure is correct but the kernel is not building. I used the "kernel-2.6.9-34.EL.src.rpm file that I found on one
2015 Dec 01
0
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
Checked with the network guy... yes, the main DNS is indeed dnsmasq. He has a delegation though, so any query for WINDOWS.corp.XXX.com winds up going to to the correct place: domain=/windows.corp.XXX.com/192.168.127.141 domain=/windows.corp.XXX.com/192.168.112.4 The DC's (192.168.127.141, 192.168.112.4) are indeed running DNS (I can dig at them). Would it just be easier to make this host
2015 Nov 30
2
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
Hey guys, I've successfully joined the domain with "sudo net ads join -k". However, when I try to run this: "sudo net rpc info" I get this error: "Unable to find a suitable server for domain WINDOWS" I dumped the DNS requests and it looks like the problem is that it's asking for ldap entries under the workgroup name, not the FQDN: >From Wireshark:
2015 Dec 01
0
After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command
So everything with the hostname with now resolving correctly, without the 127.0.1.1 hack anymore. We just had to make sure DHCP was handing out the correct domain, which it is now: $ hostname -d windows.corp.XXX.com $ hostname -f freeradius.windows.corp.XXX.com I deleted all the shared secrets, removed the computer from AD and rejoined... but of course, we're still getting the exact same