search for: nirl

Hello, SIP invites are accepted from imitator , but 'SIP 180' is not responded back to imitator. By inspecting the issue , we can *see* the response is generated and sent from asterisk (via asterisk logger ("sip debug" )) , but while sniffing the interface with tcpdump, we can't see 180 response on the interface. We don't have errors on the interface, firewall

I'm using samba version 2.2.1a on a linux RH7.2 kernel 2.4.7-10. I'm having a lot of oplock problems, specially when using office applications like word. I would like to know: 1. what is the recommended configuration in version 2.2.1a (oplocks = yes/no , level2 oplocks = yes/no , kernel oplocks = yes/no) 2. what is considered to be a stable version for oplocks usage Thanks, Nir

I understand that the difference between "server" and "domain" mode is that in "domain" mode"Samba fully uses the domain capabilities. He behaves like another NT Server or Windows 9x do by participating in domain trust relationships." Could someone please explain me 1. What is it exaclty that "domain" mode does, that "server" mode

What is the recommended linux version (RH 7.x) for samba 2.2.7 ? Are there any known issues with RH7.2 / RH7.3 ? -------------- next part -------------- HTML attachment scrubbed and removed

Hi guys, I hope this is not an off-topic here. I'm trying to configure my samba on a RedHat AS 2.1, to run in an active-active configuration. The "Red Hat Cluster Manager Installation and Administration Guide" says on chapter 6.2 : "Allows the setup of an active-active configuration to maximize equipment utilization. More details on active-active configurations appear

Hi all, Please excuse me if this question is not appropriate for this forum: Lets assume that samba server crashed or was shut down abnormally, while users where holding open files in the server. In this case, I've noticed that locking.tdb is not being cleaned when samba is restarting. I was wondering why shouldn't it be cleaned. Thanks, Nir

I am using samba 2.2.1a , in an NT-4 domain. security = DOMAIN on the first logon to the samba server, I can see a message: Attempting host lookup for name MYPDCNAME<0x20> the next message appears after 10 seconds (that is the delay). samba tries to resolve MYPDCNAME with the wins server, and succeeds. Higher debug level (debug level = 10) does not produce more debug messages. Any ideas