Search Results

Search found 4 results on 1 pages for 'tommed'.

Page 1/1 | 1 

  • Core i7 with 4GB - go 64 bit or stay 32bit..?

    - by tommed
    I have a Core i7 laptop with 4gb ram. In windows, the disadvantage of using the 32bit OS would be that a single app could not use more than 2gb of ram (+ the 2gb shared kernel-space memory) except when setting a boot switch which reduces the amount of shared kernel memory, then it's 3GB max per app. What disadvantages/limitations would I have in Ubuntu for sticking to the 32bit OS? (If any?) - As I only have 4GB of ram, I can't see why I need to use the 64bit version?

    Read the article

  • Wireless (Broadcom) just stopped working after putting machine to sleep!

    - by tommed
    Had the wireless working on my Dell Studio 15 for months now (Ubuntu 10.04 64bit, now 10.10 64bit). But I shut the lid this morning, which put the machine to sleep; when I openend it again the wireless would no longer connect to anything :'( I rebooted the machine, but that didn't help. I then did ifconfig eth1 {down,up}, but that didn't help, then I did iwconfig eth1 power {down,on}, but that didn't work. So I uninstalled the wireless driver (Broadcom STA) from additional drivers (reboot in the middle), but it still won't work anymore!! This is the trace from daemon.log, looks like it is a driver issue? Nov 28 12:26:39 ulap NetworkManager[1218]: (eth1): supplicant connection state: disconnected - scanning Nov 28 12:26:39 ulap NetworkManager[1218]: (eth1): supplicant connection state: scanning - disconnected Nov 28 12:26:45 ulap NetworkManager[1218]: (eth1): supplicant connection state: disconnected - scanning Nov 28 12:26:50 ulap wpa_supplicant[1295]: Trying to associate with MY_MAC_CODE (SSID='MY_WIRESS_SSID' freq=2417 MHz) Nov 28 12:26:50 ulap wpa_supplicant[1295]: Association request to the driver failed Nov 28 12:26:50 ulap NetworkManager[1218]: (eth1): supplicant connection state: scanning - associating Nov 28 12:26:51 ulap wpa_supplicant[1295]: Associated with MY_MAC_CODE Nov 28 12:26:51 ulap NetworkManager[1218]: (eth1): supplicant connection state: associating - associated Nov 28 12:27:01 ulap wpa_supplicant[1295]: Authentication with MY_MAC_CODE timed out. Nov 28 12:27:01 ulap NetworkManager[1218]: (eth1): supplicant connection state: associated - disconnected Anyone seen this, or know how I can get around this issue? It had been working fine up until now?! Even ran update-manager, but there wasn't any changes to the wireless drivers (or any related networking areas). Running the most up-to-date version of 10.10 x64. My android phone and other devices are still working on the wireless.

    Read the article

  • Authenticating Windows 7 against MIT Kerberos 5

    - by tommed
    Hi There, I've been wracking my brains trying to get Windows 7 authenticating against a MIT Kerberos 5 Realm (which is running on an Arch Linux server). I've done the following on the server (aka dc1): Installed and configured a NTP time server Installed and configured DHCP and DNS (setup for the domain tnet.loc) Installed Kerberos from source Setup the database Configured the keytab Setup the ACL file with: *@TNET.LOC * Added a policy for my user and my machine: addpol users addpol admin addpol hosts ank -policy users [email protected] ank -policy admin tom/[email protected] ank -policy hosts host/wdesk3.tnet.loc -pw MYPASSWORDHERE I then did the following to the windows 7 client (aka wdesk3): Made sure the ip address was supplied by my DHCP server and dc1.tnet.loc pings ok Set the internet time server to my linux server (aka dc1.tnet.loc) Used ksetup to configure the realm: ksetup /SetRealm TNET.LOC ksetup /AddKdc dc1.tnet.loc ksetip /SetComputerPassword MYPASSWORDHERE ksetip /MapUser * * After some googl-ing I found that DES encryption was disabled by Windows 7 by default and I turned the policy on to support DES encryption over Kerberos Then I rebooted the windows client However after doing all that I still cannot login from my Windows client. :( Looking at the logs on the server; the request looks fine and everything works great, I think the issue is that the response from the KDC is not recognized by the Windows Client and a generic login error appears: "Login Failure: User name or password is invalid". The log file for the server looks like this (I tail'ed this so I know it's happening when the Windows machine attempts the login): Screen-shot: http://dl.dropbox.com/u/577250/email/login_attempt.png If I supply an invalid realm in the login window I get a completely different error message, so I don't think it's a connection problem from the client to the server? But I can't find any error logs on the Windows machine? (anyone know where these are?) If I try: runas /netonly /user:[email protected] cmd.exe everything works (although I don't get anything appear in the server logs, so I'm wondering if it's not touching the server for this??), but if I run: runas /user:[email protected] cmd.exe I get the same authentication error. Any Kerberos Gurus out there who can give me some ideas as to what to try next? pretty please?

    Read the article

  • Authenticating Windows 7 against MIT Kerberos 5

    - by tommed
    Hi There, I've been wracking my brains trying to get Windows 7 authenticating against a MIT Kerberos 5 Realm (which is running on an Arch Linux server). I've done the following on the server (aka dc1): Installed and configured a NTP time server Installed and configured DHCP and DNS (setup for the domain tnet.loc) Installed Kerberos from source Setup the database Configured the keytab Setup the ACL file with: *@TNET.LOC * Added a policy for my user and my machine: addpol users addpol admin addpol hosts ank -policy users [email protected] ank -policy admin tom/[email protected] ank -policy hosts host/wdesk3.tnet.loc -pw MYPASSWORDHERE I then did the following to the windows 7 client (aka wdesk3): Made sure the ip address was supplied by my DHCP server and dc1.tnet.loc pings ok Set the internet time server to my linux server (aka dc1.tnet.loc) Used ksetup to configure the realm: ksetup /SetRealm TNET.LOC ksetup /AddKdc dc1.tnet.loc ksetip /SetComputerPassword MYPASSWORDHERE ksetip /MapUser * * After some googl-ing I found that DES encryption was disabled by Windows 7 by default and I turned the policy on to support DES encryption over Kerberos Then I rebooted the windows client However after doing all that I still cannot login from my Windows client. :( Looking at the logs on the server; the request looks fine and everything works great, I think the issue is that the response from the KDC is not recognized by the Windows Client and a generic login error appears: "Login Failure: User name or password is invalid". The log file for the server looks like this (I tail'ed this so I know it's happening when the Windows machine attempts the login): If I supply an invalid realm in the login window I get a completely different error message, so I don't think it's a connection problem from the client to the server? But I can't find any error logs on the Windows machine? (anyone know where these are?) If I try: runas /netonly /user:[email protected] cmd.exe everything works (although I don't get anything appear in the server logs, so I'm wondering if it's not touching the server for this??), but if I run: runas /user:[email protected] cmd.exe I get the same authentication error. Any Kerberos Gurus out there who can give me some ideas as to what to try next? pretty please?

    Read the article

1