search for: xtdnet

Displaying 6 results from an estimated 6 matches for "xtdnet".

Did you mean: tdnet
2001 Apr 04
0
Heh?
...imes I can't. It actually seems to almost alternate, "success,failed,success,failed,success" because at some point I thought it was a hostname problem (using host or FQDN), but it isn't Traces of the two with ssh -v -l root: Failed: [root at bofh /root]# ssh -v -l root undoable.xtdnet.nl OpenSSH_2.5.2p2, SSH protocols 1.5/2.0, OpenSSL 0x0090581f debug1: Seeding random number generator debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: ssh_connect: getuid 0 geteuid 0 anon 1 debug1: Connecting to undoable.xtdnet.nl [213.160.202.1] port 22. debug1...
2002 Oct 15
3
ISC DHCPD Problem and Solution.
...tftp-hpa server is 193.110.157.30. *ware used: Intel eepro/100+ (82557/8/9 rev 9, board assembly 748564-005, romchecksum 0xdb8681d) syslinux 1.76-1.i386.rpm intel boot agent 2.6 build 004 intel undi pxe-2.0 build 071 tftp-hpa-0.30 ISC dhcpd V3.0pl1 tcpdumps are at: http://www.xtdnet.nl/paul/pxe/ Paul
2000 Oct 25
2
Can't use two links on a linux box
Hi, I have a linux box connected to two leased lines as follows: _/\__/\_ / \ +--------+ +------------+ ( Internet )----+ Router | | SMTP server| \_ __ _/ +----+---+ +------+-----+ \/ \/ | 200.200.200.254 | 100.100.100.2\ -+-------+----- ... ---------+-- 100.100.100.1\ | 200.200.200.1 +-+--+--+ | Linux | +---+---+ _/\__/\_ 192.168.1.1 |
2005 Sep 20
4
SUCCESS - 512 Simultaneous Calls with Digital Recording
List users, Over the last few days we have been working with MCI's development lab to test our Asterisk setup. We were using a piece of hardware called an Abacus 5000 that is capable of creating and terminating thousands of SIP calls. Initially, we could not get past 64 simultaneous digitally recorded calls without having call quality issues including dropped calls. We identified an
2000 Mar 08
0
NIS, PAM, OpenSSH. Seems to work perfectly (one minor concern)
I just spent some time trying to figure out how to get OpenSSH to work correctly with NIS and PAM. It seems to work fine, apart from one minor worry I still have (see below). Feedback about grave security risks are welcome :) This is using RedHat 6.1 with updates and the OpenSSH 1.2.2p1-1 RPM's on the NIS server as well as the client. In short, my configuration is: /etc/nssswitch.conf:
2001 Feb 27
5
NAT+portfw failure
I have the following forced up mew by evil telco problem: - One IP - Homebrew LAN - portforwarding for some services. - extra PPTP/ppp layer to an internal 10.* network which mutilates DNS answers. Setup: Machine A has ip a.b.c.d (real IP) and is reachable over ADSL with it from the world. It does NAT for an internal LAN 192.168.0.0/24) and has portforwading turned on for some ports (eg 80)