SSH from inside network takes forever!

[Dale Stanbrough]

I have a server that acts as a firewall/router running Mac OS X.
Recently it started playing up (not sure why...), and now ssh'ing
into it takes around 30 seconds for it to respond (produce a password
prompt) from inside my local network.

However if I ssh to an external computer (which responds in a timely
manner) and then ssh back to the server from outside, it responds
immediately.

Any thoughts on why my server is turning it's back on me? :-)

Dale

--
[email]dstanbro@spam.o.matic.bigpond.net.au[/email]

[Dale Stanbrough]

In article <bg6n12$dcu$1@pcls4.std.com>, [email]tony@aplawrence.com[/email] wrote:

> Reverse DNS. The server is trying to resolve your host name. No doubt
> it is querying internet servers and quite naturally coming up blank.
>
> You can either run a local DNS server or just add yourself to /etc/hosts.

When i ssh to my server, i just use 192.168.0.1, so the DNS lookup
shouldn't be happening...

Dale

--
[email]dstanbro@spam.o.matic.bigpond.net.au[/email]

[Peter KERR]

Dale Stanbrough <MrNoSpam@bigpond.net.au> wrote:

> I have a server that acts as a firewall/router running Mac OS X.
> Recently it started playing up (not sure why...), and now ssh'ing
> into it takes around 30 seconds for it to respond (produce a password
> prompt) from inside my local network.
>
> However if I ssh to an external computer (which responds in a timely
> manner) and then ssh back to the server from outside, it responds
> immediately.
>
> Any thoughts on why my server is turning it's back on me? :-)

network hardware/firmware upgrades?
We had some switches upspeeded recently, and several old Macs
with 10Mhz ether ports that couldn't negotiate a 10Mhz semiduplex
link got turned into tarpits :-(

[tony@aplawrence.com]

Dale Stanbrough <MrNoSpam@bigpond.net.au> wrote:

>In article <bg6n12$dcu$1@pcls4.std.com>, [email]tony@aplawrence.com[/email] wrote:

>> Reverse DNS. The server is trying to resolve your host name. No doubt
>> it is querying internet servers and quite naturally coming up blank.
>>
>> You can either run a local DNS server or just add yourself to /etc/hosts.

>When i ssh to my server, i just use 192.168.0.1, so the DNS lookup
>shouldn't be happening...

Yes, it should. It's a reverse DNS lookup: the server wants to know what
YOUR host name is.

Happens all the time. Probably in most networking FAQS; certainly
is in mine:
[url]http://aplawrence.com/SCOFAQ/scotec4.html#telnetslow[/url]


--
[email]tony@aplawrence.com[/email] Unix/Linux/Mac OS X resources: [url]http://aplawrence.com[/url]
Get paid for writing about tech: [url]http://aplawrence.com/publish.html[/url]

[Anno Siegel]

<tony@aplawrence.com> wrote in comp.sys.mac.comm:

> Dale Stanbrough <MrNoSpam@bigpond.net.au> wrote:

> >I have a server that acts as a firewall/router running Mac OS X.
> >Recently it started playing up (not sure why...), and now ssh'ing
> >into it takes around 30 seconds for it to respond (produce a password
> >prompt) from inside my local network.

>

> >However if I ssh to an external computer (which responds in a timely
> >manner) and then ssh back to the server from outside, it responds
> >immediately.

>

> >Any thoughts on why my server is turning it's back on me? :-)

>
> Reverse DNS. The server is trying to resolve your host name. No doubt
> it is querying internet servers and quite naturally coming up blank.
>
> You can either run a local DNS server or just add yourself to /etc/hosts.

OS X uses the machines directory of the local domain instead of /etc/hosts.

You use NetInfo Manager to make the entry; by default it works on the
local domain.

Anno

[Jerry Kindall]

In article <bgo9mf$mop$5@mamenchi.zrz.TU-Berlin.DE>, Anno Siegel
<anno4000@lublin.zrz.tu-berlin.de> wrote:

> <tony@aplawrence.com> wrote in comp.sys.mac.comm:

> > Dale Stanbrough <MrNoSpam@bigpond.net.au> wrote:

> > >I have a server that acts as a firewall/router running Mac OS X.
> > >Recently it started playing up (not sure why...), and now ssh'ing
> > >into it takes around 30 seconds for it to respond (produce a password
> > >prompt) from inside my local network.

> >

> > >However if I ssh to an external computer (which responds in a timely
> > >manner) and then ssh back to the server from outside, it responds
> > >immediately.

> >

> > >Any thoughts on why my server is turning it's back on me? :-)

> >
> > Reverse DNS. The server is trying to resolve your host name. No doubt
> > it is querying internet servers and quite naturally coming up blank.
> >
> > You can either run a local DNS server or just add yourself to /etc/hosts.

>
> OS X uses the machines directory of the local domain instead of /etc/hosts.

However, it checks /etc/hosts before checking NetInfo, as of Jaguar.

--
Jerry Kindall, Seattle, WA <http://www.jerrykindall.com/>

When replying by e-mail, use plain text ONLY to make sure I read it.
Due to spam and viruses, I filter all mail with HTML or attachments.

[Anno Siegel]

Jerry Kindall <usenet2@jerrykindall.com> wrote in comp.sys.mac.comm:

> In article <bgo9mf$mop$5@mamenchi.zrz.TU-Berlin.DE>, Anno Siegel
> <anno4000@lublin.zrz.tu-berlin.de> wrote:
>

> > <tony@aplawrence.com> wrote in comp.sys.mac.comm:

> > > Dale Stanbrough <MrNoSpam@bigpond.net.au> wrote:
> > > >I have a server that acts as a firewall/router running Mac OS X.
> > > >Recently it started playing up (not sure why...), and now ssh'ing
> > > >into it takes around 30 seconds for it to respond (produce a password
> > > >prompt) from inside my local network.
> > >
> > > >However if I ssh to an external computer (which responds in a timely
> > > >manner) and then ssh back to the server from outside, it responds
> > > >immediately.
> > >
> > > >Any thoughts on why my server is turning it's back on me? :-)
> > >
> > > Reverse DNS. The server is trying to resolve your host name. No doubt
> > > it is querying internet servers and quite naturally coming up blank.
> > >
> > > You can either run a local DNS server or just add yourself to /etc/hosts.

> >
> > OS X uses the machines directory of the local domain instead of /etc/hosts.

>
> However, it checks /etc/hosts before checking NetInfo, as of Jaguar.

Aha. That is interesting. Would that go for passwd and group too?
You don't have to answer that if you say where to read up on it instead :)

Anno