similar to: nmblookup problem

Hi William. Thanks a lot for your help. Im having some trouble recompiling my kernel after a installed the patch. Im running RH 7.3 with kernel 2.4.18-3. The patch I installed is routes-2.4.16-6.diff. I got no errors installing it. I added the multipath support, and recompiled it. The make dep and the make bzImage went fine. I got error during the make modules. These are the errors:

Hi, I am trying to set up a linux box to act as a router for my college. There are two different types of users; students and conference guests, and they have IPs statically assigned by DHCP, from separate ranges (but they are on the same subnet). The students go out onto an academic connection (via eth0), and conference guests go out on an ADSL line (via eth3). eth1 and eth2 are configured for

Hi, here is a client computer and a server computer (Debian Wheezy, armel, samba Version 3.6.6, IP address: 192.168.1.2, Name: xyz). Problem: wins doesn't answer nmblookups by the client on the broadcast address: client$ nmblookup -S xyz querying xyz on 192.168.1.255 name_query failed to find name xyz Why is that so? How to fix this? When I specify the the server IP I do get an answer:

hi. Are you add only 0.0.0.0/1 as route, not 128.0.0.0/1 too? Did you tried to add route to 5.6.7.8 via C with lesser metric then via B? If you have to add static routes only on a few servers, you can add them to the $HOST-up scripts. On Mon, Feb 29, 2016 at 11:12 AM, Zhang Jun <gb2313 at gmail.com> wrote: > my network: > > local pc(192.168.1.2)-->openwrt_adsl_router A(

my network: local pc(192.168.1.2)-->openwrt_adsl_router A( 192.168.1.1/24&11.22.33.44pppoe&10.10.10.1/24 tinc)<---remote B: 10.10.20.1/24 ^ | remote C:10.10.0.1/24 all running tinc 1.0.x, ADSL router

Hi I have a strange problem. I have a firewall with 3 nics. 1 - lan 2 - leased line or diginet 3 - connected to adsl modem I have 2 tables in defined in /etc/iproute2/rt_tables: 200 diginet 201 adsl The ADSL modem has an IP of 192.168.0.1 and is configured to initiate the PPPOE connection. I can mark packets within the network destined for port 80 successfully: ip ro add default via x.x.x.x

I'm running Samba 1.9.18p8. If I use nmblookup to query the name of an NT server, as in nmblookup -A <ip address> then a packet trace shows an RPC reply coming back and nmblookup displays a list of names belonging to the NT server. If I try the same query on a Windows 95 machine, nmblookup only says Looking up status of <ip address> No status response (this is not unusual)

I'm trying to use nmblookup to find the IP address of a Windows machine called "MARKETKA" (only with an accent over the 'E'). If I do a reverse lookup on the IP address, with debugging enabled, I can see that the hex code for the accented 'E' character is 0x90: $ nmblookup -d 4 -A 192.168.1.15 | grep MARK answers 0 char .MARK.TKA hex

Hi. Im now decribeing my problem very clearly to see if anyone could help me. I have 3 (three) nics in my system. 1 is for my internet network - (eth1) 2 are for my 2 adsl lines that i use to connect to the internet (eth2 is my "master" adsl line) and (eth0 is my "slave" adsl line). I know that to make redundance work ill have to setup the ip route and ip rule in my

Hi folks, I find that nmblookup seems to be receiving responses to name queries, but ignoring them. Here's what's happening: # nmblookup somehost querying somehost on x.y.255.255 name_query failed to find name somehost But watching the transaction with ethereal on the local host, I see that: 1. nmblookup on local udp port nnnn (some random number above 1024) sends an nbns

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

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.

Hello, i have had a terribe day today, why? because i have been so 4 or 5 hours trying to do work this and i have not finished it. I feel very pleased if anything can help me. I have two isp connections: eth0: dhcp ip1: 82.198.*.* gw1: 82.198.*.* and a router adsl in ip 192.168.0.253: eth1: static ip2: 192.168.0.254 gw1: 192.168.0.253 the same machine has 3 more networks cards but i am

Hello! I''ve got the following setup: ippp0 (isdn), ppp0 (adsl), eth1 (internal lan), eth0 (nic dedicated to the adsl modem) Firewall rules: Default 2.4. iptables (everything set to accept) except: iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE iptables -t nat -A POSTROUTING -o ippp0 -j MASQUERADE Routing Table: Default gw is set to the ptp partner of ippp0 Problem: Packets

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 Everyone, >From windows 2K, machine I could see Samba server but I can't get its share. I tried to follow the instruction given at http://samba.planetmirror.com/samba/ftp/docs/Samba24Hc13.pdf to resolve the problem. nmblookup -U 127.0.0.1 _SAMBA_ and nmblookup -B 10.10.255.255 real-samba-server-name fails for me but nmblookup -U 127.0.0.1 real-samba-server-name

I have an XP Pro box on my LAN, and I'm trying to figure out why nmblookup '*' can't see it. I'm writing a script that finds all the shares on the LAN and mounts them, and it works great except for this one box. On another windows box, when I run "net view", the XP box is listed as I expect. On my linux box, when I run "nmblookup -A 192.168.0.111" it

Hi All: When I usign nmblookup to query my domain controller, I got different = results: root@Latrell:# nmblookup -A ADDomain.com Looking up status of 169.254.211.91 No reply from 169.254.211.91 root@Latrell:# nmblookup -A ADDomain.com Looking up status of 172.23.26.204 WIN-2003 <00> - M <ACTIVE> WIN <00> -

When I have my iptables based firewall running, I cannot get nmblookup to locate any computers (Windows 98, Samba, Windows NT 4, or Windows XP) I require tight firewall settings, because college students can cause havoc on a network when its servers are not secure. I need a way to get nmblookup to work without disabling the firewall. The standard conntrack module does not work, because

I have Ubuntu 14.04.LTS and some Windows 7 client, with for example IP 192.168.0.201. I run nmblookup from Samba4 4.1.14 built in my own (without changes at nmblookup) with the following parameter: *nmblookup -A 192.168.0.201* As there is defined at nmblookup, it query *<00> of specified IP. So, I see non constant answers: Sometimes for the first nmblookup run it shows answers where there