search for: proxy4

I have just completed the installation of a new firewall running Shorewall 1.4 on Mandrake 9.2 for our campus network. It appears to be running fairly well so far, but is generating significantly more log entries than our previous linux 2.0.x firewall... Our previous firewall enjoyed more than 6 years of 24/7 operation with no downtime before we finally decided it needed more horsepower, and

In the panic of replacing our firewall(s) earlier in the week, we ended up moving our original shorewall 1.4 config onto a machine with 2.0.10 already installed, overwriting all the 2.0.10 config files. Most things seem to work fine, except for our masq entries. I''ve examined the default 2.0.10 files compared with our 1.4 files, and can''t spot the problem. What am I missing?

I *think* we are finally making some progress in tracking our elusive performance problems. After employing a second 10Mb link from our ISP, along with another firewall box and proxy, we were able to determine the problem *is* our firewall. We don''t know exactly why yet, but our sporadic slow web access seems to have gone away since swapping a new firewall in this morning. The

First, here's what I want to do / what I have: X100P and a Quicknet PhoneJack. I want to be able to pick up the analog phone (connected to the phonejack) and dial another computer (with the same hardware) or just make a regular phone call which will be decided by asterisk depending on the phone number dialed. I know that this won't be taking full advantage of asterisk, but I'm

...ier (to which nobody responded, making me wonder if anyone else actually uses ACLs for domain accounts on samba...). Here's the conf file: [global] hosts allow = 10. 139.142.66. 127. winbind uid = 10000-20000 max xmit = 65535 allow hosts = 139.142.66. 10. dns proxy = no netbios name = PROXY4 oplocks = yes inherit permissions = yes workgroup = SHAWNIGAN debug level = 3 security = domain getwd cache = yes winbind separator = + log level = 10 read raw = yes write raw = yes socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=16384 SO_SNDBUF=16384 wins server = 139.142.66.1...

...Join is OK Note that client ntlmv2 is on now. The problem comes in when trying to use squid to do the authentication. We get the following error in the squid log file if we set the authenticators debugging to level 9: [2005/11/07 13:36:35, 3] libsmb/ntlmssp.c:ntlmssp_server_auth(606) Got user=[Proxy4] domain=[DOMAIN] workstation=[ianb] len1=24 len2=24 [2005/11/07 13:36:35, 3] utils/ntlm_auth.c:winbind_pw_check(427) Login for user [DOMAIN]\[Proxy4]@[ianb] failed due to [Wrong Password] If we type in a username that doesn't exist, it complains that the username is invalid, so we know that...

...Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:285) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:989) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:790) at org.jboss.deployment.MainDeployer.deploy(...