Prev: solaris update8 causing SCR issues because of patch 118833-36
Next: patchadd rejects sun studio patches
From: kartikvashishta108 on 17 May 2010 10:54 When I telnet to my system running Solaris 10, I get very slow initial response times, and instead of the "login" prompt, the first prompt I see is "password", this password prompt comes after a lo-ong time.......I have to hit enter at that "password" prompt to get an "incorrect password" message and then revert to the "login" prompt where I supply my login credentials.....in short it is slow and it starts with a "password" prompt not a "login" prompt. cat /etc/release Solaris 10 5/09 s10s_u7wos_08 SPARC Copyright 2009 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 30 March 2009 once the telnet session is "established"(by supplying username/ pasword), the response times are good.
From: Andrew Gabriel on 17 May 2010 12:04 In article <b5c02700-a6cb-4308-8a64-cb10e57899c1(a)f14g2000vbn.googlegroups.com>, kartikvashishta108 <kartik.unix(a)gmail.com> writes: > When I telnet to my system running Solaris 10, I get very slow initial > response times, and instead of the "login" prompt, the first prompt I > see is "password", this password prompt comes after a lo-ong > time.......I have to hit enter at that "password" prompt to get an > "incorrect password" message and then revert to the "login" prompt > where I supply my login credentials.....in short it is slow and it > starts with a "password" prompt not a "login" prompt. > > cat /etc/release > Solaris 10 5/09 s10s_u7wos_08 SPARC > Copyright 2009 Sun Microsystems, Inc. All Rights Reserved. > Use is subject to license terms. > Assembled 30 March 2009 > once the telnet session is "established"(by supplying username/ > pasword), the response times are good. Two thoughts... The IP address you are connecting from takes a long time to either reverse translate, or to timeout trying to doing so. The telnet client you are using is sending across TELNET AUTHENTICATION negotiation, probably passing whatever user name it thinks you are using on the client system. -- Andrew Gabriel [email address is not usable -- followup in the newsgroup]
From: kartikvashishta108 on 17 May 2010 12:13 On May 17, 11:04 am, and...(a)cucumber.demon.co.uk (Andrew Gabriel) wrote: > In article <b5c02700-a6cb-4308-8a64-cb10e5789...(a)f14g2000vbn.googlegroups..com>, > kartikvashishta108 <kartik.u...(a)gmail.com> writes: > > > When I telnet to my system running Solaris 10, I get very slow initial > > response times, and instead of the "login" prompt, the first prompt I > > see is "password", this password prompt comes after a lo-ong > > time.......I have to hit enter at that "password" prompt to get an > > "incorrect password" message and then revert to the "login" prompt > > where I supply my login credentials.....in short it is slow and it > > starts with a "password" prompt not a "login" prompt. > > > cat /etc/release > > Solaris 10 5/09 s10s_u7wos_08 SPARC > > Copyright 2009 Sun Microsystems, Inc. All Rights Reserved. > > Use is subject to license terms. > > Assembled 30 March 2009 > > once the telnet session is "established"(by supplying username/ > > pasword), the response times are good. > > Two thoughts... > > The IP address you are connecting from takes a long time to either > reverse translate, or to timeout trying to doing so. > > The telnet client you are using is sending across TELNET AUTHENTICATION > negotiation, probably passing whatever user name it thinks you are > using on the client system. > > -- > Andrew Gabriel > [email address is not usable -- followup in the newsgroup] Thanks, for the second issue - the telnet client was indeed passing a login name to the telnet session......I did telnet from a cmd prompt and it showed up with the "login" prompt, so you were correct. This leaves me with the slow response time, this setup is on a home LAN, not sure what the issue could be, I'm able to telnet fine to other systems, ping does not show any delays.... C:\Documents and Settings>ping 192.168.0.247 Pinging 192.168.0.247 with 32 bytes of data: Reply from 192.168.0.247: bytes=32 time=3ms TTL=255 Reply from 192.168.0.247: bytes=32 time=1ms TTL=255 Reply from 192.168.0.247: bytes=32 time=1ms TTL=255 Reply from 192.168.0.247: bytes=32 time=2ms TTL=255 Ping statistics for 192.168.0.247: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss) Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 3ms, Average = 1ms C:\Documents and Settings>
From: kartikvashishta108 on 17 May 2010 12:47 On May 17, 11:13 am, kartikvashishta108 <kartik.u...(a)gmail.com> wrote: > On May 17, 11:04 am, and...(a)cucumber.demon.co.uk (Andrew Gabriel) > wrote: > > > > > In article <b5c02700-a6cb-4308-8a64-cb10e5789...(a)f14g2000vbn.googlegroups.com>, > > kartikvashishta108 <kartik.u...(a)gmail.com> writes: > > > > When I telnet to my system running Solaris 10, I get very slow initial > > > response times, and instead of the "login" prompt, the first prompt I > > > see is "password", this password prompt comes after a lo-ong > > > time.......I have to hit enter at that "password" prompt to get an > > > "incorrect password" message and then revert to the "login" prompt > > > where I supply my login credentials.....in short it is slow and it > > > starts with a "password" prompt not a "login" prompt. > > > > cat /etc/release > > > Solaris 10 5/09 s10s_u7wos_08 SPARC > > > Copyright 2009 Sun Microsystems, Inc. All Rights Reserved. > > > Use is subject to license terms. > > > Assembled 30 March 2009 > > > once the telnet session is "established"(by supplying username/ > > > pasword), the response times are good. > > > Two thoughts... > > > The IP address you are connecting from takes a long time to either > > reverse translate, or to timeout trying to doing so. > > > The telnet client you are using is sending across TELNET AUTHENTICATION > > negotiation, probably passing whatever user name it thinks you are > > using on the client system. > > > -- > > Andrew Gabriel > > [email address is not usable -- followup in the newsgroup] > > Thanks, for the second issue - the telnet client was indeed passing a > login name to the telnet session......I did telnet from a cmd prompt > and it showed up with the "login" prompt, so you were correct. > > This leaves me with the slow response time, this setup is on a home > LAN, not sure what the issue could be, I'm able to telnet fine to > other systems, ping does not show any delays.... > > C:\Documents and Settings>ping 192.168.0.247 > > Pinging 192.168.0.247 with 32 bytes of data: > > Reply from 192.168.0.247: bytes=32 time=3ms TTL=255 > Reply from 192.168.0.247: bytes=32 time=1ms TTL=255 > Reply from 192.168.0.247: bytes=32 time=1ms TTL=255 > Reply from 192.168.0.247: bytes=32 time=2ms TTL=255 > > Ping statistics for 192.168.0.247: > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss) > Approximate round trip times in milli-seconds: > Minimum = 1ms, Maximum = 3ms, Average = 1ms > > C:\Documents and Settings> removed dhcp and gave it a static IP, the response time is good now
From: Andrew Gabriel on 17 May 2010 13:11 In article <295c7a1e-65a4-4dc8-9931-4c9a8db3d7d3(a)c11g2000vbe.googlegroups.com>, kartikvashishta108 <kartik.unix(a)gmail.com> writes: > removed dhcp and gave it a static IP, the response time is good now Make sure the IP addresses you dish out for DHCP can be reverse translated on the server. If necessary, create /etc/hosts entries for them all. -- Andrew Gabriel [email address is not usable -- followup in the newsgroup]
|
Next
|
Last
Pages: 1 2 Prev: solaris update8 causing SCR issues because of patch 118833-36 Next: patchadd rejects sun studio patches |