Sponsored Content
Contact Us Post Here to Contact Site Administrators and Moderators Image/JS hoster down or unreachable Post 302430239 by Neo on Thursday 17th of June 2010 02:42:38 AM
Old 06-17-2010
Index of Support Trouble Tickets with SimpleCDN

I think I know why SimpleCDN blocked my IP address. They read my blog post and did not want me to have access to our trouble ticket log.

Kind of anticipating something like this from them, I saved all the relevant discussions in PDF, including the index of all the trouble tickets, which you might find interesting.

(attached)
 

10 More Discussions You Might Find Interesting

1. IP Networking

Connect: Network is unreachable

I am running RH7.3 on a compaq presario box. The network card is a Linksys one. I am only able to communicate with the local network (only the local IPs are accessible). When I try to ping another box I get a "Connect: Network is unreachable" message. What could be the problem. Thanks in... (2 Replies)
Discussion started by: skotapal
2 Replies

2. Cybersecurity

Host unreachable

I have inherited a Sun Ultra-1, running sunOS 5.8 While on this machine, I cannot ping www.yahoo.com I cannot ping this machine from withing our lan. I do not have an static IP for this machine and used Iconfig hme0 auto-dhcp start. All is well, It seems to me that the previous owner,... (1 Reply)
Discussion started by: defense
1 Replies

3. UNIX for Advanced & Expert Users

Create an Ignite image on tape from Online IgniteUX image

Hi, (HP-UX 11.11) I need to create a tape image of an igniteUX image created on our igniteUX server. That is to say. I have a "Online" image of the igniteUX of the targeted system but I now need to copy it to a useable TAPE (igniteUX) image so i can build an other server from it that is not... (3 Replies)
Discussion started by: Andrek
3 Replies

4. UNIX for Dummies Questions & Answers

Notification if server unreachable?

Is it possible for a group of servers to monitor each other and then send an alert if one of them is no longer 'alive'? Or if its easier have one server that monitors the other five and then sends an alert. If so how would this be done? Thanks (3 Replies)
Discussion started by: Sepia
3 Replies

5. Linux

Linux Port Unreachable

All, I have to servers (NT and REL4). We can access the application on NT from Linux but we cannot access the applications on Linux when accessed from NT. The applicaiton is running on Linux with some IP:Port. When we try to access that application from NT, it says that the port is... (1 Reply)
Discussion started by: The One
1 Replies

6. Solaris

How to get explorer from unreachable machine

Hi Guy. I have a Dummy question. I cant connect a T2000 machine to the network, We have netword card problems. But in this moment is mandatory to get the explorer from the machine. My question is What can I do?. Could I try write the explorer to the CD? (This is a option), or any... (6 Replies)
Discussion started by: aggadtech08
6 Replies

7. Solaris

ICMP Net Unreachable from gateway

Hi all, I cannot reach my SERVER from my NetBackup server connect through SERVER_prv ("cannot connect to client") My SERVER was Sun OS 5.8, below is the message i get when i ping my SERVER: # ping 192.168.X.X or # ping SERVER_prv ICMP Net Unreachable from gateway 172.16.102.XXX for... (3 Replies)
Discussion started by: beginningDBA
3 Replies

8. UNIX for Dummies Questions & Answers

[Ubuntu] some contents unreachable

Hello, I'm using Ubuntu, and when I check "/"(root directory)'s properties. The window says "some contents unreachable". What is the "some contents"? http://i.imgur.com/UWn8Q.png (2 Replies)
Discussion started by: hz_i3
2 Replies

9. UNIX for Advanced & Expert Users

Wether does it successful or unreachable?

Hi, all: How can I check what happen with my own NIC driver which response "successful" when local PC "ping" a remote linux PC but "unreachable" when it "ping" a remote windows XP PC? My writed driver runs in linux 3.0.4 kernel. thanks! li, kunlun (1 Reply)
Discussion started by: liklstar
1 Replies

10. Solaris

Installadm - network in unreachable

Seems to wanboot ok but then fails to connect to server. What do I need to check? {0} ok boot net - install Boot device: /pci@300/pci@1/pci@0/pci@1/network@0 File and args: - install 1G link up <time unavailable> wanboot info: WAN boot messages->console <time unavailable>... (2 Replies)
Discussion started by: psychocandy
2 Replies
KINIT(1)						      General Commands Manual							  KINIT(1)

NAME
kinit - obtain and cache Kerberos ticket-granting ticket SYNOPSIS
kinit [-5] [-4] [-V] [-l lifetime] [-s start_time] [-r renewable_life] [-p | -P] [-f | -F] [-A] [-v] [-R] [-k [-t keytab_file]] [-c cache_name] [-S service_name] [principal] DESCRIPTION
kinit obtains and caches an initial ticket-granting ticket for principal.Thetypicaldefaultbehavioristoacquireonly Kerberos 5 tickets. How- ever, if kinit was built with both Kerberos 4 support and with the default behavior of acquiring both types of tickets, it will try to acquire both Kerberos 5 and Kerberos 4 by default. Any documentation particular to Kerberos 4 does not apply if Kerberos 4 support was not built into kinit. OPTIONS
-5 get Kerberos 5 tickets. This overrides whatever the default built-in behavior may be. This option may be used with -4 -4 get Kerberos 4 tickets. This overrides whatever the default built-in behavior may be. This option is only available if kinit was built with Kerberos 4 compatibility. This option may be used with -5 -V display verbose output. -l lifetime requests a ticket with the lifetime lifetime. The value for lifetime must be followed immediately by one of the following delim- iters: s seconds m minutes h hours d days as in "kinit -l 90m". You cannot mix units; a value of `3h30m' will result in an error. If the -l option is not specified, the default ticket lifetime (configured by each site) is used. Specifying a ticket lifetime longer than the maximum ticket lifetime (configured by each site) results in a ticket with the maximum lifetime. -s start_time requests a postdated ticket, valid starting at start_time. Postdated tickets are issued with the invalid flag set, and need to be fed back to the kdc before use. (Not applicable to Kerberos 4.) -r renewable_life requests renewable tickets, with a total lifetime of renewable_life. The duration is in the same format as the -l option, with the same delimiters. (Not applicable to Kerberos 4.) -f request forwardable tickets. (Not applicable to Kerberos 4.) -F do not request forwardable tickets. (Not applicable to Kerberos 4.) -p request proxiable tickets. (Not applicable to Kerberos 4.) -P do not request proxiable tickets. (Not applicable to Kerberos 4.) -A request address-less tickets. (Not applicable to Kerberos 4.) -v requests that the ticket granting ticket in the cache (with the invalid flag set) be passed to the kdc for validation. If the ticket is within its requested time range, the cache is replaced with the validated ticket. (Not applicable to Kerberos 4.) -R requests renewal of the ticket-granting ticket. Note that an expired ticket cannot be renewed, even if the ticket is still within its renewable life. When using this option with Kerberos 4, the kdc must support Kerberos 5 to Kerberos 4 ticket conversion. -k [-t keytab_file] requests a host ticket, obtained from a key in the local host's keytab file. The name and location of the keytab file may be speci- fied with the -t keytab_file option; otherwise the default name and location will be used. When using this option with Kerberos 4, the kdc must support Kerberos 5 to Kerberos 4 ticket conversion. -c cache_name use cache_name as the Kerberos 5 credentials (ticket) cache name and location; if this option is not used, the default cache name and location are used. The default credentials cache may vary between systems. If the KRB5CCNAME environment variable is set, its value is used to name the default ticket cache. Any existing contents of the cache are destroyed by kinit. (Note: The default name for Kerberos 4 comes from the KRBTKFILE environment variable. This option does not apply to Kerberos 4.) -S service_name specify an alternate service name to use when getting initial tickets. (Applicable to Kerberos 5 or if using both Kerberos 5 and Kerberos 4 with a kdc that supports Kerberos 5 to Kerberos 4 ticket conversion.) ENVIRONMENT
Kinit uses the following environment variables: KRB5CCNAME Location of the Kerberos 5 credentials (ticket) cache. KRBTKFILE Filename of the Kerberos 4 credentials (ticket) cache. FILES
/tmp/krb5cc_[uid] default location of Kerberos 5 credentials cache ([uid] is the decimal UID of the user). /tmp/tkt[uid] default location of Kerberos 4 credentials cache ([uid] is the decimal UID of the user). /etc/krb5.keytab default location for the local host's keytab file. SEE ALSO
klist(1), kdestroy(1), krb5(3) KINIT(1)
All times are GMT -4. The time now is 01:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy