Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA12708; Fri, 29 Sep 95 23:46:16 EDT Received: by MIT.EDU id AB19809; Fri, 29 Sep 95 23:43:47 EDT Date: Fri, 29 Sep 95 23:43:47 EDT From: MAILER-DAEMON@MIT.EDU (Mail Delivery Subsystem) Subject: Returned mail: Cannot send message for 3 days Message-Id: <9509300343.AB19809@MIT.EDU> To: To: proven@PO7.LOCAL To: tytso@E40-PO.LOCAL To: probe@E40-PO.LOCAL To: jis@E40-PO.LOCAL To: tlyu@PO8.LOCAL ----- Transcript of session follows ----- 421 atrium.com.tcp... Deferred: Connection timed out during user open with texatrium.zilker.net 451 jaisimha@atrium.com... Cannot send message for 3 days jaisimha@atrium.com... Cannot send message for 3 days ----- Unsent message follows ----- Received: from pad-thai.cam.ov.com by MIT.EDU with SMTP id AA02717; Tue, 26 Sep 95 22:58:45 EDT Received: by pad-thai.cam.ov.com (8.6.12/) id ; Tue, 26 Sep 1995 23:00:56 -0400 Received: from GATEWAY by pad-thai.cam.ov.com with netnews for kerberos-wrapper@cam.ov.com (kerberos@mit.edu) To: kerberos@MIT.EDU Date: 26 Sep 1995 18:03:59 GMT From: reece@eco.twg.com (Reece R. Pollack) Message-Id: <449faf$80v@eco.twg.com> Organization: The Wollongong Group, Inc. Sender: usenet@cam.ov.com References: Reply-To: reece@eco.twg.com Subject: Re: HELP WANTED: kinit problem on Solaris2.4 In article , zhu@ctcgp1.ih.att.com (-Zhu,K.) writes: |>Hello, |> |>I installed MIT Kerberos V5 Beta 5 on a Solaris2.4 (for testing |>purpose, everything is on the same machine). When I ran kinit, |>I got the following error message: |> |> kinit: Can't send request (send_to_kdc) |> |>The system was set up according to Ts'o document (dated May 5, 1995) |>as well as Lenny Miceli's hints (dated on September 13, 1995). |>I checked all the pieces (krb5kdc running, /etc/krb5.conf file, |>/etc/services file, ...) and they appear ok. The man page |>for kinit appears out of date and thus not that helpful. |> |>Any help on getting around this to make the kinit run would |>be truely appreciated. Thanks in advance. This usually happens to me when I forget to add the Kerberos service entries to the /etc/services file. Without these entries, kinit can't figure out which port to use to connect to the kdc. -- Reece R. Pollack Senior Software Engineer The Wollongong Group, Inc.