Hi,
I have the next problem on OpenSuse 11.2:
I needed to connect remote to my computer at work. I've installed AT&T client (agnclient-1.0-2.0.1.3003.i386.rpm + prerequisites). All is working fine, I can connect to my computer from work using KRDC. But I have the next problem:
From that point on I can browse the internet only after I start AT&T client.
I have a project where I'll have a number of remote Linux systems in the field. From time to time they'll need to connect to a central server via SSH. These remote systems are automated and have no user present. The number and IP of the remote systems is likely to change often, so keeping a central list of them may be difficult.
I’m looking for an infrastructure which ideally should be maintained as following:
Several (virtual) operating-systems (linux and windows as well) should run on a server simultaneously and be accessible over the local network from heterogeneous clients (such as linux, os x and windows operating systems running on a desktop computer).
The aim is that it doesn’t matter which client device in the l
I have an OpenVPN server and many clients connecting.
I have an OpenVPN server and many clients connecting.
I have a NFS server running Linux and exporting a couple of shares.
tried in two different networks and multiple clients both Windows and Mac. It seems like when I reboot the VPN server it allows any client to connect once and second client connection gets error from any client.
I setup pptpd on CentOS6.3, I m testing it, I can connect to the server the first time after reboot.
I'm trying to setup a small LAN, using an Ethernet switch, an Arch Linux server, and around 10 Windows XP machines. This network has no outside connections.
The Arch machine has a self configured ip address (configured with ip addr add 192.168.0.1 dev eth0), and acts as a DHCP server(using dhcpd).
Given n (e.g. 200) clients in a /24 subnet and the following network structure:
client 1 \
. \
. switch -- firewall
. /
client n /
(in words: all clients connected to one switch and the switch connected to the firewall)
Now by default, e.g. client 1 and client n can communicate directly using the switch, without any packets ever arriving the firewall.