Jump to content

Cragzman

Members
  • Posts

    46
  • Joined

  • Last visited

Everything posted by Cragzman

  1. Ahhh evil. I forgot to mention that I managed to get the NTLM working on a mock domain I have set up at home with no problems. But when I try and set it up on the school domain, with a few tweaks on the .conf files, I get a login box to the squid box I just set up via IE7. Kinda defeats the object of NTLM authentication methinks. I'm probably clutching at staws but maybe it has something to do with the default domain policy in Active Directory? My domain kerberos policy: Account Policies/Kerberos Policy Policy Setting Enforce user logon restrictions Enabled Maximum lifetime for service ticket 600 minutes Maximum lifetime for user ticket 10 hours Maximum lifetime for user ticket renewal 7 days Maximum tolerance for computer clock synchronization 5 minutes NTP is set up correctly so it can't be the clock sync. I haven't got any Dansguardian or similar stuff installed yet. Just want to make sure that no login boxes come up. Thanks again guys
  2. Cool. Squid should run ok without these parameters? Thanks
  3. Hi again. I have made a Squid cache on a Ubuntu 8.04.1 server. Browsed the web on how to build it. Configuration is: Ubuntu 8.04.1 Server Samba 3.0.28 (3.0.28a-1ubuntu4.4) Winbind Kerberos 5 Squid 2.6 (2.6.18-1ubuntu3) Got a slight problem with NTLM scheme parameters. Errors that I get when I restart Squid are: unrecognized ntlm auth scheme parameter 'use_ntlm_negotiate' unrecognized ntlm auth scheme parameter 'max_challenge_reuses' unrecognized ntlm auth scheme parameter 'max_challenge_life' My squid.conf file (may need a bit of a tidy): ================================== auth_param ntlm program /usr/bin/ntlm_auth --helper-protocol=squid-2.5-ntlmssp auth_param ntlm children 30 auth_param ntlm use_ntlm_negotiate on auth_param ntlm max_challenge_reuses 0 auth_param ntlm max_challenge_lifetime 2 minutes auth_param basic program /usr/bin/ntlm_auth --helper-protocol=squid-2.5-basic auth_param basic children 5 auth_param basic realm Squid Proxy Server auth_param basic credentialsttl 2 hours hierarchy_stoplist cgi-bin ? acl QUERY urlpath_regex cgi-bin \? no_cache deny QUERY hosts_file /etc/hosts refresh_pattern ^ftp: 1440 20% 10080 refresh_pattern ^gopher: 1440 0% 1440 refresh_pattern . 0 20% 4320 acl all src 0.0.0.0/0.0.0.0 acl manager proto cache_object acl localhost src 127.0.0.1/255.255.255.255 acl to_localhost dst 127.0.0.0/8 acl purge method PURGE acl CONNECT method CONNECT http_access allow manager localhost http_access deny manager http_access allow purge localhost http_access deny purge acl authenticated_users proxy_auth REQUIRED acl lan src 10.103.0.0-10.103.3.255 http_access allow authenticated_users http_access allow localhost http_access allow lan http_access deny all http_reply_access allow all icp_access allow all visible_hostname ubuntuproxy coredump_dir /var/spool/squid http_port 8000 cache_peer cachepilot sibling 8000 3130 proxy-only login=ubuntu:ubuntu cache_effective_user squid cache_effective_group squid ============================= Kinda copied the stuff above but changed and added the odd one or two things. Any ideas peeps? Cheers
  4. I have managed to set up Squid with NTLM Authentication. WOOO! Just a few more bits and pieces that need sorting. 1. Is there a thing for squid that can log domain usernames in the access.log? 2. Is there a time converter thingy for the log so I can make sense of it? 3. Can I make multiple user groups (for example: staff, students) and have seperate URL blacklists for each? Thanks again peeps
  5. Oh yeah forgot to mention that I stuck the drivers in both Capture and Setup images. kinda went mad and stuck both 32 and 64 bit drivers in for XP and Vista to cover all bases.
  6. I had problems with WDS and Vostros. What I did was format the drive using an XP cd because I had partition problems. Then I injected XP and Vista network card drivers. WDS uses the fluffy bunny look of Vista which I don't like much. YUCK!! Then WDS played ball and got an image woooo!!
  7. My pay is the same. What a load of rubbish. Took them ages to sort it out just to get the same pay. Think I better go out to do some begging on the street to raise some cash.
  8. Thanks for the help guys. I decided to go for Ubuntu 8.04.1 Server as it seemed to be the popular choice. Also our intranet server uses it. Been solid as a rock. Think I have installed Squid, Samba, and Winbind. Just now to configure it. Eeeek!
  9. Hi guys. I'm on a mission to set up a Squid box. Been told that it would be better than our rubbish Equiinet Cachepilot. But I'm not sure which Linux I should use. Any ideas? Also does Squid, when authenticating with Active Directory, create log files with the users username included? Trying to kill the user input of user credentials when using LDAP on the Cachepilot. Plus Cachepilot hates WSUS. Any help would be grand. Ta very much
  10. Quick update. For a test I tweaked the Cachepilot so I don't have to input user proxy credentials in a 2 hour timespan. WSUS synchronizes with no problems. Hope it still askes for credentials outside the 2 hours eek. Bummer that it hates AD authentication.
  11. I'm using the Servers user account for proxy authentication and it belongs to the netinet group. It should work but it doesn't. Tried my own credentials but no joy. Nothing looks amiss in AD either.
  12. Had a go at calling ICT Solutions today but the internal phone system being a pain in the rear. If someone could give me the ICT Solutions WSUS 3 SP1 upstream IP with port number, I would be very grateful.
  13. Hi peeps. I'm having a problem with WSUS SP1 synchronizing with Microsoft Update. I have just recently installed it as a clean install with no previous versions. Here is a few details of the setup we have: 1. WSUS is installed on a domain controller. 2. Our school goes through an E2BN Equiinet Cachepilot proxy (Release 3.2.5 (upgraded)). 3. Proxy is using user login authentication (LDAP thingy) so we can see who has accessed what sites via Tail. In the WSUS proxy settings, I inputted the proxy name, port number, and login credentials with "Allow basic authentication (password is sent in cleartext)" enabled. With these settings, in therory, WSUS should work. But I get this error message: -------------------------------------------------------------------------- WebException: The remote server returned an error: (407) Proxy Authentication Required. at System.Net.HttpWebRequest.GetRequestStream() at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig() at Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper) at Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper webServiceHelper) at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesFromUSS() at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect) -------------------------------------------------------------------------- Is this a known issue? Is there fix/workaround? Any ideas would rock. Cheers all
  14. Hallo all! I work with mickeyh080. Just an update relating to the Dell Poweredge 1900 server. Quite recently we have had BSOD at random occasions. The event viewer shows the same error. (System Error - (102) Event code 1003.) Used the Windows Debug thingy and found that SYMEVENT.SYS (a symantec driver) is causing a problem. Found that it was linked to Symantec Live Update and then I updated SYMEVENT. The server seems to be behaving at the mo. But im not sure if SYMEVENT is to blame for the freezing and not being able to log on via remote desktop. Just have to wait and see methinks.
×
×
  • Create New...