Debian Configuration :: Refuses Port Connections - VNC
Sep 29, 2010
I'm trying to setup VNC on our debian server so the boss can remotely do admin stuff from anywhere in the world. the first step is getting it working from anywhere in the room, though. And I can't even seem to get that far.
So far I have a VNC server setup, although not without problems. I downloaded and installed vnc from the vnc site, that wouldn't work because trying to start a vnc server gave this error: "error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory"
There are lots of results on google for this error, and the solution everywhere seems to be the same. to install the package: libstdc++2.10-glibc2.2
However, trying to install this package in debian fails. both using apt-get and trying to manually download it from packages.debian.org it just doesn't seem to exist.
I've tried tightvnc from the official repositories and it gives the same error, too.
The way I got around that eventually, thanks to another tutorial, was to install the package vnc4server. then run vnc4passwd to create a password. and after that vncserver works fine, or seems to. Creates display 1.
Now, when I'm trying to connect to hostname:1 from another computer in the LAN. It gives error 10061, connection refused. I installed the debian and I don't recall setting it up to refuse connections on port 1. Is there anything I should check or change to allow the connection, or any log file in debian to check and see what's going wrong?
I'm also trying connecting internally via client on the debian machine, but I can't runvncviewer. I get the same missing shared library error as before. I guess I just worked around, not solved it.
I also can't access it with the java viewer. Trying to connect on port 5801 either from the server itself, or from another one on the lan, tells me it's refusing the connection.
To be clear, I'm certain that the vnc server is started. We have working DNS, and trying to connect directly to the internal IP:1 doesn't work either.
I installed a fresh Debian Desktop without the LAN cable connected. After that I got message when I put the cable in:
Code: Select allNetwork Interface Connection New Wired Connection failed
I have tried to re-install everything once again with the cable in, but during the Debian installation there was no network detected.
However, I proceeded and re-installed Debian. But the problem persists. It continues to re-connect and than disconnect. There is a symbol showing re-connection. The network eth0 is visible to the machine.
I booted Mint Live disc and the same happens there.
Is it fair to say that connLimit and hashlimit are very similiar on Linux i.e. while hashlimit caters to limits for groups of ports, they both set the connection rate limit per host? How in IPTables, do I configure a policy that limits connections on a port that encapsulates the total sum of all connections from all hosts? i.e. I do not want to allow more than 6000conn/minute for port range that is the sum of all connecting hosts?
I have slapd-server running but it seems to refuse connections in a very odd way. Wireshark shows that everytime JavaEE-client tries to connect, only 2 packages are sent. As I understand, in tcp/ip protocol, the first is just "hello, who's there". The last is just a message consisting of ACK and RST. I think RST means "we're done". At this point I don't think any credentials are checked so I don't know what could be wrong
I have ssh installed and running on my laptop(Debian Sequeeze). I can run "ssh localhost" without any problem. But for some reason I cannot connect to it from other computers. They all give "connection timed out". I can connect to these computers`s ssh servers but for some reason my laptop with Debian is not accepting any connections.
A little background: CCNA and A+ I have preformed this task on Cisco routers Linux for 5+ years, mostly with Debian (mostly casual, a few production situations) I need to setup a linux box with Load Balancing over a cable line 8mb down, 1mb up connection and a T1 line. If this isn't possible, at the very least I need Failover (which I have admittedly not researched as fully.) I know Failover is possible, but I would really love to double my upload bandwidth as we host a small website here. Is load balancing over uneven connections possible on Debian?
Side question: If I host a website, when users connect and get responses over 2 Public IP's, what would be the reaction on the users side? Would it get filtered and or blocked by a firewall?
My Debian server is used by people to set up ssh-tunnels for use as a local proxy ( on their remote machines).Since only the tunnel is setup, and no shell is used, I can't use "who" to see which users have an active ssh-tunnel on my server, but I would like to have an idea about who is active etc. I think I should be able to determine this from the auth.log file, but then I would have to use some script to determine what connection is still active. Is there an easy way to see what users have active ssh-tunnels on my Debian server at any given moment?
I'm trying to bridge connections between a wired and a wireless connection in one of my computers. I was told it was impossible due to low-level limitations in the wireless subsystem, but apparently theres a way if you somehow forward packets from one port to the other. Is there a way I can achieve this?
I have exim setup on squeeze to run as an "internet site". Outgoing mail works fine but it seems to just ignore incoming smtp requests on port 25. I can see the incoming connection via tcpdump but exim doesn't seem to talk. If I connect via telnet it rather quickly says connection refused. Is there something additional I need in the Exim conf?
I just installed Debian and am getting a problem where I can't open the list of network connections. I can use the network manager applet to connect to wireless networks, but I cannot access the network connections list from there either (right click "edit connections)
I'm not incredibly knowledgeable with Linux, but I tried a few simple things I could think of like reinstalling the packages, or restarting the interfaces. (ifdown/up wlan0)
It's strange, because when I click "network connections," I see it show up for a second on the bottom panel, I get some rotating mouse icon while I wait a few seconds and then if goes away. Is there some kind of logfile that could help me identify the problem?
Using Debian 6 on eeePC1000HEB with Ath9k (i think) wireless card. Net Interface: wlan0
I am still a noob with linux and debian in particular. I do some android development so through that I have learned a little bit about linux but only the basic command prompt commands and the basics of how linux works and such.Anyways, I was looking around on the forum and on other forums and I couldn't find any helpful information about how to set up wireless connections (such as wifi) on debian. When I installed debian on my computer it asked me for the ipw2200 files and I didn't have them at the time but now I have the latest framework files for that, I don't really know how to install them and after I install them I don't know how to turn on my wireless connections from there.
I am really sorry if someone already made a post on this subject and I am just too clutzy to find it, if that's the case please just post the link to that thread for me cause I'm dumb as crap.So basically the main problem I am trying to fix right now is that I cannot get my internet to work on my old dell inspiron 6000 laptop which I am trying to get to run debian.
I have a set up with a computer that has two network cards and is connected to two networks. Both networks connect to the internet via separate routers that have DHCP enabled. I can set one of the routers up to do port forwarding to the computer without any complications but if I want to do the same on the other router the port forwarding from it doesn't work and I can't reach the system.
I know for a fact that the services are accessible from both networks and both routers can forward ports to other computers in their network. The networks are 10.10.0.1/24 and 172.22.0.1/24. I've tried turning off iptables but that didn't change anything.
Is there any kind of setting that could prevent the interface on the computer to reject traffic using NAT or something?
If I disable the interface on the working network (ifdown eth1) then suddenly eth0 on the other networks starts accepting requests sent to it via the router that does the port forwarding. I do however want to emphasize that services work just fine as long as the requests originate from either of the networks they are on.
I need to connect to a serial port server via /dev/tty.. . The serial port IP addresses are the server's IP address with a particular port # (10001, 10002 etc). The way this seems to work is to create a pseudo-tty and somehow link or configure it to point to the serial server's IP/port #'s.
On this moment i build an webenvironment with wordpress, apache2, debian 8. On this moment i try to impelement Varnish.
By default this application use the port 6081. I try to put apache on port 8080. This already works but i get varnish not running on port 80.
You can see below that varnish still listen to the default port 6081. How can i fix this?
Code: Select allroot@webI:/home/beheerder# netstat -lpt Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address      Foreign Address     State    PID/Program name tcp    0   0 *:ssh          *:*           LISTEN   2917/sshd tcp    0   0 *:6081         *:*           LISTEN   3717/varnishd tcp    0   0 localhost:6082     *:*           LISTEN   3699/varnishd
[Code] ....
To test another port i have also try to start Varnish on port 85.
Code: Select allvim /etc/default/varnish DAEMON_OPTS="-a :85        -T localhost:6082        -f /etc/varnish/default.vcl        -S /etc/varnish/secret        -s malloc,256m"
I have restart the apache and varnish services. I have also rebooted the server but varnish will not listen on port 80 (or other non default ports). On port 6081 the application works fine. But how can i fix this ?
Source Varnish port 80
I can use the application with the following command
Code: Select allvarnishd -f /etc/varnish/default.vcl -a 0.0.0.0:80.
But why is this not working with the normal config file. Varnish are than listen to port 80. With every server reboot i need than to run this command. So i would like to use the config file.
Is is possible, via iptables or something similar, to bind a service running on a specific port to a specific interface? My case: I use a VPN service for privacy. I would like to have all traffic except ftp and ssh to run over tun0. Ports 21 and 22 will need to be accessible to the outside world (eth0) while the VPN is running.
I just noticed after installing a new server with samba that a portscan will show the samba used ports. This server has two interfaces, a world address eth0 and an intranet eth1. The samba ports show in scanning either interface, even after I changed samba to listen only to the intranet (192.168.x) address.
I am concerned especially about the 139 and 445 ports, which could attract a lot of garbage traffic.This is Debian 5.05 default samba installation.Otherwise similarly installed Ubuntu box with two interfaces does not show samba at all, even though smbd is running and working just fine.
Everything default.Everything works nicely with one exception. I can't connect to MySQL from the network.nmapping localhost tells me 3306 is open but nmap from the outside shows only ports 22 and 111 open. To my knowledge I have no firewall, iptables -L gives an empty set.I have several similar installations on the same network without any problems of this nature.
I've setup my own repository which I want to use SSH as the protocol. I managed to get everything working with an SSH key using port 22. Now, I would like to change the SSH port. I've already changed it on the SSH/repo server. Now I can't figure out how to change apt to use a custom port on the client computer.
My sources.list file line which worked over port 22: deb ssh://user@1.1.1.1/home/user/repo lenny main contrib non-free I've tried: deb ssh://user@1.1.1.1:12345/home/user/repo lenny main contrib non-free and it fails and actually says "failed connecting to port 22"
Can this be done? I've searched google for hours and I getting nothing but unrelated data. I've read the man pages. The man page for apt.conf specified that you can set the port this way for HTTP, but doesn't mention anything about ssh ports.
I have a java application that I wrote recently. It runs off port 9955. The application runs great on my mac server. When I installed it on my linux box i cant get to it from outside the box. A port scan shows the port as closed. I flushed my iptables, did not help. I can telnet into the app locally, from the server and it works great. I cannot telnet from outside the server. I have a reference to the application in /etc/services as a tcp port (which it is).
I have got a laptop running Debian squeeze. I wish to share the wireless connection of the laptop (wlan0) to the ethernet port of the laptop, so that I can share the wireless connection to my desktop PC which is connected to the ethernet port.
I have read the article on Ubuntu community: [url]
I followed the steps, and the /etc/network/interfaces file on my laptop is:
Now the situation is: My laptop can connect to Internet (i.e. ping debian.org from laptop is fine), my desktop PC can connect to my laptop (i.e. ping 192.168.1.1 from desktop PC is fine). However, the desktop PC cannot reach the Internet.
I also read the information on Debian Wiki: [url]
It seems I must install and configure ebtables before sharing my wireless connection to ethernet port. Is it true? (But why the article on Ubuntu community doesn't mention it?) Or I just made some mistakes?
I have a trayless SATA hotswap bay that is really terrific for quickly attaching and removing SATA hard drives. I'm trying to write a udev rule to create a symbolic link to the device node for the drive that is attached through the hotswap bay (/dev/bay -> /dev/sdX). This eliminates any ambiguity when performing destructive tasks (fdisk, etc). I'm running squeeze amd64. I've read through several tutorials and have it working somewhat. Here's the output of udevadm info for a drive attached via the hotswap bay.
Here is my udev rule DEVPATH=="/devices/pci0000:00/0000:00:11.0/host7/*", SUBSYSTEM=="block", SYMLINK+="bay%n"
This produces the desired behavior and gives me an fdisk-able device node. The problem I am having is that the "host" component of the DEVPATH varies from bootup to bootup. I'm just using on onboard SATA, host2-7, specifically host7. There is also onboard PATA, host0-1. It seems to just be random which "host"s are assigned to which controller. For example, the next time I boot the system, the onboard SATA will be host0-5 and the onboard PATA will be host6-7. In this simple case, I could just write 2 rules, one for each possibility and it would still be correct because of the different PCI addresses of the two controllers. But on systems with more SCSI (uh... libata, actually) controllers, a "host" file can point to different physical ports between bootstraps. This would be bad. Does anyone know of a way to write a rule to tie a device node to a specific physical SATA port on the motherboard/hba?
I'm not sure if this is a Linux standard, but I've always understood that Linux restricts usage of ports below 1025 to root-user only. My question is why was this method developed?My theory is that it's to reduce the possibilty users who may not be as knowledgable with Linux from getting hacked. This is probably wrong though as ports 1025-66535 are available to any program as any user.
A deamon say ssh will be listening on port 22. when a new connection is requested by the client, it will be authenticated and a new connection gets establihed with some port say 1025. And ssh will continue to listen on 22 for new connections.If I am correct then in my machine I observed following connections are establised to ssh port 22, As per my understanding connection should be established on a different port other than 22.
I'm trying to follow the instructions here: [URL] but I'm struggling with point 2 & 3:
Quote:
2. If you have previously reconfigured the firewall on your PC, make sure the firewall allows incoming connections on port 22 from anywhere, and on port 5900 from localhost (also known as 127.0.0.1)
3. If your PC is behind a home router, or any other device that uses NAT, configure your router to send connection attempts on port 22 (but not port 5900) to your PC
So my questions are:
1. I installed a fresh version of Ubuntu 11.4, should I be concerned about step 2? If so, how can I allow incoming connections on port 22 from anywhere, and on port 5900 from localhost?
2. Regarding step 3, I'm using NETGEAR model DGN1000 router. Is that something that I should do from the router's setting page or it's some commands that I should pass through SSH?
