I have these two ports open for some reason. netstat says they're attached to 'smbd', but when I look at packages installed and search for smbd the only thing that comes up is samba4 which is NOT installed.
I'm guessing some other package installed this as a dependency. Is there anyway to find out what it was and remove it?
I'm having some trouble addressing computers by name. I've just upgraded most my my box's to Lucid, and it was all working fine, but suddenly stopped - not quite sure why, or what I did, but I need it to come back! At first I thought it was my old router dying (which it was) but a new router hasn't helped.
I've now moved DHCP from the router to my server, and that's working fine, giving out static IPs from MAC addresses, and so forth, but I still can't address anything by name. My server is on 192.168.100.1 and called myth-server, if I
At the CLI, I want to know how to get a netbios name from an IP address. It seems that every solution that I have found is windows based, or requires me to install something beyond samba. is a simple "prog-x -somearg 192.168.1.100" or similar to get the netbios name - and that it doesn't require a reconfiguration of my server?
For instance, I would like this to be usable on a desktop system in an ad hoc without having to be run from root.
I have been beating my brains out the last few days trying to get my linux box to ping my Pc's via the netbios name. (ping pc_name) I have read post after post with no luck at all. What i do know is that my pc's can ping the linux box via netbios name with no problem. Samba works from the pc's but not the other way around. I have added wins to my host in the nsswitch.conf fileMy smb.conf file:Quote:
global] workgroup = OFFICE server string = Samba Server Version %v
If you're running samba server on your Slackware box on a windows network / domain, and you don't want it showing up on the windows computers network neighborhood browser, there's a couple of things you have to do. First, add the line:
disable netbios = yes to the global section of smb.conf. This didn't work for me so I also figured out the next step:
Second, edit the rc.samba script and remove the references to starting or restarting nmbd.
In this line: if [ -x /usr/sbin/smbd -a -x /usr/sbin/nmbd -a -r /etc/samba/smb.conf ]; then
Remove the reference to nmbd (underlined above) so it looks like this:
if [ -x /usr/sbin/smbd -a -r /etc/samba/smb.conf ]; then
Then comment out with a # this part: #echo " /usr/sbin/nmbd -D" # /usr/sbin/nmbd -D
and add a comment # mark here (right before nmbd)
samba_stop() { killall smbd # nmbd
underlined above, then restart samba or reboot. The first step may not be necessary if you make the changes to rc.samba but I did both and that took care of it.
In recent days, (today is September 18, 2010) I've been surfing the web trying to learn how to access nodes in my soho lan by netbios names instead of having to connect through the ip number, because ip's change every time according to DHCP assignments. I do not know what has happened to the "new" command mount.cifs, but things seem to have become a bit more complicated with the new version. Security problems, they say, and surely that's the reason.
I show here an automated way of loging into servers by netbios name instead of having to resort to the use of IP numbers, hosts files, wins servers and all that jazz. This is especially useful if your soho lan have five or more network nodes, and you do not want to go finding out the ip numbers assigned to the machines you want to connect to (temporarily or permanently).
This output is piped to gawk to isolate the line containing <00>, and gawk outputs the first element (print $1) of that line, which happens to be the ip of the server ServerName. I tested the script in my soho network, which now has Linux, Windows XP and Windows 7 nodes, and it worked perfectly for both tipes of servers.I'm using GNU's gawk, but I'm pretty sure that awk would do the job just as well.
LAN CentOS 5.5 Windows 7 machine (hostname/NETBIOS name: AwesomePC, LAN IP: 192.168.1.20) Workgroup: Cake No WINS server No Domain No AD
Goal
From CentOS 5.5, have
# ping AwesomePC
resolve to a ping on 192.168.1.20
Problem
# ping AwesomePC
resolves to some random public IP that seems to be coming from my WAN DNS (openDNS) servers
ATTEMPTS
Have edited /etc/nsswitch.conf, edited line: hosts: files wins dns Have edited /etc/resolv.conf, added line: search CAKE Have installed samba (# yum install samba) and run (# service smb start), with /etc/samba/smb.conf, workgroup = CAKE, name resolve order = wins host lmhosts bcast
Does # ping even care about samba? How can I get this to work?
I have a fileserver that I want to share out samba shares. However, i configured samba to have another netbios (SAN) and my windows box still sees whoopn-SAN which is the name I gave to my server when i installed it. Now I am using 9.10 and I know that i can create a share from the gnome gui in nautilus and that appears to be a windows like share. How can I turn OFF the windows like shares that ubuntu does out of the box and use ONLY samba? I ask because there appears to be a conflict of permissions b/w samba and this stuff.
I've had my FC11 x86_64 installation up and running for 6 months. Until a week ago, I was able to mount windows shares through Nautilis using their netbios names. About a week ago, this all broke with no tinkering on my part. Now, I can mount the shares using the IP address, but not using the netbios name.
When I make he attempt either from scratch or by using a previously working bookmark, I get "cannot display location "smb:\..." When I browse the network using Nautilis I can see the workgroup, but when I try to open it, I get "unable to mount location. Failed to retrieve share list from server." When I use nmblookup with the netbios name, the correct ip adress is returned.
The problem seemed to correspond to a software update that occurred on 2009-11-21 that included updates to selinux-policy and selinux-policy-targeted. SE Linux has the System Default Enforcing Mode set to disabled. The system default policy type is set to targeted with no other options available.nsswitch.conf file appears to have been changed on the same date, but reverting back to the backup version of the file failed to solve the problem. Samba is up and running. My linux shares are accessible from my windows boxes. The firewall is open to smb and smbclient.
I am on a 172.16.x.x network with about 60 Windows XP home and Vista home clients in a peer-to-peer workgroup that uses DHCP to assign addresses. About half the traffic on my LAN is netbios broadcast. I do not want to do a WINS server because I do not want to have to manually change the registry on every machine. This is only for local name resolution and I do not have any web servers or e-mail servers. I do not have access to a Windows server to use as a DNS server. I am on Debian and using BIND but am open to other suggestions.
I want to do a simple port redirect, i.e. whatever comes trough whatever interface on port AAAA will get redirected to port BBBBI thought that iptables -t nat -I PREROUTING --source 0/0 --destination 0/0 -p tcp --dport AAAA -j REDIRECT --to-ports BBBBhowever it doesn't work, e.g. nc -v -w2 -z localhost AAAA gives:
nc: connect to localhost port AAAA (tcp) failed: Connection refused while nc -v -w2 -z localhost BBBB
I have a mail server i need it to send message via port 587 not port 25, i make some changes to my postfix server which i use and it is already successed making a telnet to 587 port like it :
This applies to my 2 opensuse PC's, my Windows PC is fine.I can ping a hostname, say "PC1" but I can not ping PC1.domain.local (even the host PC can not ping it's own FQDN). When I ping just the hostname the ping stats even list the FQDN.Onto the next issue, since all my PC's, have the domain prefix domain.local, my Synology can not. I can ping it's IP and that is it. I can resolve it's name with nmblookup just fine tho and that is what is killing me. How is this not resolving.Even weirder, I can browse to "Synology" in Network Servers under places on the slab.
sudo ssh -L 750:192.168.123.103:873 username@192.168.123.103It does exactly what it's supposed to do, but how do i edit / remove this rule?Is there some config file where i can alter the forwarding? How does it get stored?Im using Ubuntu 10.10Server Edition (allthough i recon it would be pretty much the same across all versions
I'm not that great with mailservers, and just been thrown a curveball with a MS Exchange environment for which there is apparently no solution... yeah, right. But is there a workaround?
The problem is that the site mail (SMTP) needs to be sent via port 26 instead of the commonly used 25. Port 25 is mapped to a mailfilter, which apparently causes havoc with some of the mail, and the techs that have been on site trying to coax the Exchange server to co-operate have said that the only way would be to get rid of the filter.
The problem is that there are number of apps that are unable to have the outgoing port changed and so keep sending mail out on port 25.
I look after the Unix/Linux side of things at work, and I was wondering if there was an easy way to set up a Ubuntu box to receive mail on port 25 and just forward it to the MS box on port 26? So, in other words (and I hope this makes sense): monitor port 25, and forward whatever comes in on port 25 to the server on port 26. Simple portforwarding, or is it? What steps do I need to take?
everything works fine. I can log in, and local port forwarding is done. Otherwise when I use the command:
ssh user@ssh_server -R 5500:localhost:5500 -p 22
I get an error "remote port forwarding failed for listen port 5500". However when I try remote port forwarding in WinXP by use of putty there is no problem...
VERY new to linux, erm but I have an issue that needs solving!I recently moved to university, where their network blocks sftp port 22, this means that I cannot connect to my FTP server which is running a version of linux.Now I've got this ftp server connected to a seedbox and it was created using the following walk through..Code:I have written this guide for a friend, but I though it would be useful for others as well.
There are several guides floating around, but I found that most always cock up in some way. This one is tried and tested to work on Debian Etch (on an OVH rps, but should apply to most servers).If there is a new stable release of rtorrent/libtorrent then I will update this guide to show you how to update it (without reinstalling the whole server).
At the bottom there are also instructions to install ftp access & some network monitoring software.Basically, I would really like someone to be able to construct the commands on how to change the listen port for sftp connection on linux or add another port to the list that Linux would use so that I could put in through putty.
Is there any way to verify if packets being trafficked over a certain port are valid for the service you want to use this port for?
One obvious example that probably clarifies my question: When I open port 443 (outgoing or incoming) for https/ssl traffic, I don't want this port to be used for say openvpn traffic. Thus: when someone wants to surf to a website with https, it should be ok but if someone wants to connect to his home openvpn server over that same port, it should be blocked.
I'm trying to set rxtxSerial to work so a Java app has access to a serial port (via SiLabs CP210x driver, port /dev/ttyUSB0). When I use update-alternatives --config java, there are 3 alternatives which provide `java'. I have tried openJDK and Sun. Both fail but with completely different messages.
In SuSE firewall0. I do have a openSuse 11.4 and multiple IP addresses on eth0 interface
I run (trying to/have to) multiple TOMCAT servers.
I am trying to have each tomcat instance listen to on separate IP address for example:
What i am trying to do is to redirect
a) tomcat 1 -
a) tomcat 2 -
And so on.
I know that it has to be possible.
I do have just eth0/
Is is it possible. Do I have to create "vittual interfaces"? eth0:1, .......... and do redirection ?
"Server" has got just single interface - just 1 ethernet calbe goes to that server. I am planning to have 10-15 tomcat's on that server (I have to unfortunatley) and each has to run on port 80
Is it possible to "grant" permissions to normal users to run app on port 80 - that would solve me lots of problems if impossible to redirect.
I tried to setcap 'cap_net_bind_service=+ep' /path/to/tomcat ...... but no luck
i am running ncat (netcat's new version from nmap) on centos . I am listening on different ports. My question is , is it possible that when a connection is received on a port say 123, i redirect this connection to a different port and use the 123 port again for listening connections. ncat has an option -k which u can add with -l , it will force fully listen on the port. It can accept multiple connections on a single port but i want that once a client connects on to 123 port, he is forwarded to some other port and no longer on 123.
I'm using a Debian servers, as router/firwall.. I've two ethernet interfaces into the server, one for wan and one for lan. The i use SNAT so my LAN clients can access the internet throgh the debian router. That is working... Now i want to be able to access servers on the LAN site from the WAN site, and i wanna use port address translation (PAT). I have a FTP server running on a lan server, so i'm trying to portward port 21.
When people try to access my FTP from the WAN site, they are redirected to the local FTP server, and they are promted for crendentials, but when the credentials are typed, and the local ftp server should answer the wan request, the connections dies.
The wan clients are being promted for credentials, so they are redirected to the local lan server, but after that the connections dies, so i think there is some kind of nat problem, when the local lan server is trying to respond to the wan request..
I make an application on GNU/Linux which listening on a MULTICAST stream, so I open my unconnected socket, bind it on a MULTICAST address and a port, join the multicast group with the "setsockopt (IP_ADD_MEMBERSHIP)", then I receive datagram on my socket.
Now I've two different instances of the same application that run with their own MULTICAST address and port. And what I found strange is that, after a misconfiguration, I switch the ports, for example:
Emitting on 225.0.0.1/23451 and 225.0.0.2/23452 Receiving on 225.0.0.1/23452 and 225.0.0.2/23451
And my receiving part doesn't care about the MULTICAST address, it looks like the socket is listening on the port number only! I mean that the receiver [225.0.0.1/23452] take its datagrams from emitter [225.0.0.2/23452] and vice-versa!