similar to: Multi-IP question

On Sun, 23 Feb 2003 09:47:05 -0800, "Sam Leffler" <sam@errno.com> said: > >> Add a new config option IPSEC_FILTERGIF to control whether or not >> packets coming out of a GIF tunnel are re-processed by ipfw, >> et. al. By default they are not reprocessed. With the option they >> are. > > This may affect your ipfw/ipf rules. If you are happy with

Hi, After lots of struggle and rtfm I finally got most things running, except for 'nmblookup' and 'net getlocalsid' on the BDC. I'm not new to Samba, but plenty more to learn. Here's the setup in summary: system pdc is the PDC on subnet 192.168.0.0, running SuSE10.1, LDAP master, wins server, domain master browser, no iptables; system bdc is the BDC on subnet 192.168.2.0,

Hi, I'm having trouble explicitly forcing a codec between sip devices. Am I missing something or is this not really possible? I have a grandstream registering to asterisk, named sip0. Sip0 registers, via sip, to another asterisk box, sip1. When I place a call from the grandstream, it will travel through sip0 to sip1, where it is then placed to the PSTN. Nothing can reinvite, this path is

I'm reposting this to the list.. My spam filters didn't like the list host. :( If anyone was able to respond to the mail below, can you send it again please? Thanks. ------------------------------------------------------------------------- Hi, I'm having trouble explicitly forcing a codec between sip devices. Am I missing something or is this not really possible? I have a

Hi list. I'm new to this list, so please bear with me. I've got samba 2.2.8a on Solaris 9 (SPARC). I've run all the tests. testparm runs fine. Other tests: # nmblookup -B stage __SAMBA__ querying __SAMBA__ on 192.168.18.25 192.168.18.25 __SAMBA__<00> # # nmblookup -B 192.168.1.9 '*' querying * on 192.168.1.9 192.168.1.9 *<00> # # nmblookup -d 2 '*'

Hi, I can't get "net view \\<servername>" to work from my Windows test client. It fails with "The network path was not found". I followed some of the online debugging guides and have found that a couple of the test nmblookups on the server are failing. The server is named 'fileserver1' and its IP address is 155.2.196.251 for the purpose of this email.

I'm trying to troubleshoot a new samba setup on a tiny network, and I'm clearly missing something. I'm running Samba 3.0.22 on Ubuntu Linux. When I first set it up, it seemed to go so smoothly. I changed all the workstations to the same workgroup (RABNETWORK) and they could see each other and the server, but they couldn't open anything on the server. I don't really understand

Believe me, I have tried everytbing I can think of to solve this problem. I will work my tail off to resolve this but I am fresh out of ideas. Any suggestions would be GREATLY appreciated. Here are the details... problem: server can see machines/shares on clients but clients cannot see machines/shares on server workgroup/domain: golgerth no router server: rpms: kernel 2.4.18.19.8.0

This is getting real tough to debug. titan : Solaris 8 running samba 3.0.31 aequitas : OpenSolaris running samba 3.2.0 I can do basics test just fine : # /usr/xpg4/bin/date -u;/opt/csw/bin/findsmb Sat Jul 12 22:50:51 GMT 2008 *=DMB +=LMB IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION

Samba not responding to broadcast calls from networked PCs. Short: My Redhat Linux 8.0 box is not replying to udp broadcasts, and I can't figure out why. Network: The offending Redhat 8.0 Linux Box (//DS) attempting to run Samba 2.2.7 Firewall Redhat 7.3 (//IW) successfully running Samba 2.2.4 Win98 (//MS) Win2k (//SL) <Not running at the time of these tests> Very long: I've

I used to be able to browse the windows shares on the network through Nautilus. I can see them as computers, but when I click on them, it fails. (I'm on Ubuntu 6 LTS, AMD64) About 3 months ago, this failed. But, the windows boxes can all still access my shares on my Linux box. I was going through the trouble shooting, and found this out, but I'm not sure what to do next. I am

I'd like my Samba server to be a Domain Master Browser for a workgroup (let's call it 'ENGINEER'). I set it up according to BROWSING.txt, but yet Windows NT/95 PCs on other subnets are unable to browse and see computers on this subnet (even if those PCs are also in the same workgroup). It appears that the Samba is not acting as the Domain Master Browser ... at least as far as

I'm debugging my Samba setup using the "Troubleshooting Techniques" from Sam's Teach Yourself Samba in 24 Hours. Everything works fine up until the nmbd section. I am able to do the following correctly: nmblookup -U 127.0.0.1 __SAMBA__ nmblookup -U 127.0.0.1 POGO (the server) nmblookup -B 192.168.1.255 WIN-CLIENT (the client) but when I do nmblookup -B 192.168.1.255

> Maybe there isn't a glibc version (although > it shouldn't be hard to port the Solaris version to >glibc). I will try to port nss_wins to glibc. I made some changes to smb.conf and follow the tests described in Samba diagnosis (www.samba.org/samba/docs/diagnosis.html) smb.conf [global] workgroup = NETMANAGER server string = Deltacom Samba Server printcap name =

Hi All, Due to a hard-disc crash, I have just upgraded from a working Samba setup running in FC2 to a non-functional Samba setup running in FC3. The Windows XP machine has not changed, but won't connect. Samba is fully up2date from the FC3 repositories. smb.conf [global] workgroup = MYGROUP server string = Samba Server hosts deny = ALL hosts allow = 192.168.1.0/24 127.

Troubleshooting steps fail. Trying to replace a standalone Netware server with a Samba4 server with AD. To isolate this test setup, changed server's static IP address and separated the wiring. Then went through the Troubleshooting portion of The Samba Checklist. Some tests pass. Some tests fail. I'm weak on Samba, DNS and AD. I appreciate your instructions on how to overcome the

It's really weird how many times thing break in threes. This time is was my wife's laptop, my router and a phone. Anyway... My network has a router and 2 computers; my F11 box with the samba server on it called steve and my wife's laptop now running Windows 7 called Kellie-PC. My old router was a Linksys WRT54G that I had flashed with DD-WRT. I was using DHCP and DNS masquerading in

Hello all. I've decided to try using samba on our Solaris systems to give users who are stuck with PCs on their desks access to our gis data. I obtained a compiled binary package of version 2.0.7 from one of the samba.org sites, and have installed SAMBAroot, SAMBAusr, SAMBAman, and SAMBAdoc. All apparently worked just fine. I've made a couple of changes to the smb.conf file, changing

I make all steps in the guide: http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/install.html#id2546028 but command (exetuded in the same computer where is samba): smbclient //fc9/tester -Utester%test gives error: Domain=[DZTI] OS=[Unix] Server=[Samba 3.2.0-17.fc9] tree connect failed: NT_STATUS_BAD_NETWORK_NAME The user tester have been created by commands: useradd tester smbpasswd -a

I'm having a perplexing problem with a multiple configuration setup. My setup was working fine until I changed the IP address of my server. Since then, Samba has been misbehaving. All other networking processes are working fine so I don't believe it to be a o/s issue on the system. The system is running Solaris 2.6 using Samba 2.0. My client and the server are on the same TCP/IP class, a