long time connecting to server

Question

Level 1

0 points

long time connecting to server

Hello, recently installing snow leo & have some network problem.
MacPro 4.1 / 10.6.2
I setup network & everything is work good, internet speed is ok - but when i try to connect to server near me (in my local subnet) it takes really long time before login window comes up. Already tried change network interface order - did not work for me. BTW - when i try reach my local server i use comm + K, then IP address (no DNS) - so I think it cant be DNS problem. Also I disable IP6. It seams problem in my system or just miss-configuration something
ping to this server works fast, traceroute -n - fast too, but without "-n" - takes long time (about 10 sec)

Any suggestion ?

Mac Pro, Mac OS X (10.6.2)

Posted on Jan 5, 2010 1:49 PM

Reply

Answer 1

bphendri

Level 1

119 points

Jan 5, 2010 2:13 PM in response to abalamut

What kind of server are you trying to connect to? Another MAC OS X server? Windows server?

Do you have any other services running on the server? Mail? Web? How do their response times seem?

Reply

Answer 2

abalamut Author

Level 1

0 points

Jan 7, 2010 1:12 PM in response to bphendri

Hello, first - thanks you for answer.
I have several mac's & pc's at home. Everyone works good, insted of new installed Snow Leo.
Mac at home, I have small local network behind cisco pix, so I use ISP dns. To communicate each other i use ip address. My mackintosh has 192.168.19.2

Some test here:
when i traceroute my self it takes about 25 sec before it done but I see

macpro:~ alexpronin$ traceroute 192.168.19.2
traceroute to 192.168.19.2 (192.168.19.2), 64 hops max, 52 byte packets
1 192.168.19.2 (192.168.19.2) 0.126 ms 0.040 ms 0.020 ms
macpro:~ alexpronin$

so traceroute takes less then 1 sec! but why it is takes so much time?

second test

macpro:~ alexpronin$ traceroute -n 192.168.19.2
traceroute to 192.168.19.2 (192.168.19.2), 64 hops max, 52 byte packets
1 192.168.19.2 0.128 ms 0.014 ms 0.012 ms
macpro:~ alexpronin$

answer comes immediately !

yes -it is look like dns, netbios, dejavue issue ... dont understand what I shel do!

can you point me??

Reply

Answer 3

abalamut Author

Level 1

0 points

Jan 7, 2010 1:47 PM in response to abalamut

some additions

I have edited fite /etc/hosts, it is temporary solved problem - but it is not good solution.

Waiting for advice ...

Reply

Answer 4

bphendri

Level 1

119 points

Jan 7, 2010 8:05 PM in response to abalamut

Hmmm..

What was the entry you put in /etc/hosts?

If that worked around the problem, it sounds like it might be a DNS issue of some sort.

Reply

Answer 5

bphendri

Level 1

119 points

Jan 7, 2010 8:09 PM in response to bphendri

But yet it is interesting that you are using the IP address to connect,

But the only thing the /etc/hosts file is used for is to provide name resolution to a machine without doing a DNS lookup..

Reply

Answer 6

bphendri

Level 1

119 points

Jan 7, 2010 8:15 PM in response to bphendri

I also don't understand your traceroute numbers.. Your saying it's taking 10 seconds for the tracert to be configured, but it looks to me like from the hop time that it isn't taking no 10 seconds.

Compare these with a traceroute taken from my network. Mine should be substantially slower, however the command functions instantly, and I am returned to the prompt instantly.

traceroute hobie.catracing.org
traceroute to hobie.catracing.org (192.168.1.2), 64 hops max, 52 byte packets
1 hobie.catracing.org (192.168.1.2) 0.566 ms 0.241 ms 0.227 ms

So my next question is.. When is it taking 10 seconds? From the time you hit enter after entering the traceroute command, or from the time it takes to begin the traceroute, or the time it takes to return back to the shell prompt?

If that makes any sense?

Reply

Answer 7

abalamut Author

Level 1

0 points

Jan 8, 2010 4:50 PM in response to bphendri

Hello, thanks for answering
there is my simple cfg
macpro has 192.168.19.2/28
stockserver 192.168.19.3/28

I added to /etc/hosts the following
192.168.19.2 lacalhost
192.168.19.3 stockserver

when I did it - everything works fine & fast, but I can not add every computer to hosts, course some times I bring some new & it takes IP from DHCP, I think it is clear.

And about your last question -
It takes about 25 sec from i hit enter until it takes back to the shell prompt.
but when it done it display that traceroute done for less 1 sec!

Because traceroute is diagnostic tool, usually people don't use it to really work, the same delay happen when I try to connect to file share. It does not matter afp / smb / nfs / even ftp.

When first time I looked this I was try trace route for diagnostic porpoise - it delayed too.

So - now it is clear that it is dns/netbios/dejavue problem - but how I can fix it?!
I have not any Idea.

Some Addition - I thougt when I try reach anything by IP it makes reverse lookup
Because I use ISP DNS there are not records to my local subnet

lacalhost:~ alexpronin$ nslookup 192.168.19.3
Server: 77.50.0.3
Address: 77.50.0.3#53

** server can't find 3.19.168.192.in-addr.arpa: REFUSED

lacalhost:~ alexpronin$

but answer become imidetely !

it seems system try get answer some other way

PS
sorry my poor english, it is not my native language

Reply

Answer 8

bphendri

Level 1

119 points

Jan 8, 2010 6:45 PM in response to abalamut

Interesting. Though the thing is, especially since you are using IP Addresses, your local router should know that those are internal addresses, it should not even have to do a reverse lookup on the ISPs DNS server. And the ONLY time it should have to do a reverse lookup, is if you where doing an inquirely as to the hostname of a specific IP address. Otherwise, all's the computer should need to know is the IP address, which it has already.

I would say something funky is going on with your router, and that it is sending what should be local traffic, out to your ISP, and your ISP is routing it back in.

I good test would be to assign just your server a static address, as well as your Mac Pro workstation, hook it up to a switch or a hub and do a connection by IP address. It should be instantaneous.

Router config, is the only thing I can think of at this point, because as I said, if your connecting by IP, to the SAME upnet. The router shouldn't be passing it to your ISP at all!

Reply

Answer 9

abalamut Author

Level 1

0 points

Jan 9, 2010 1:39 PM in response to bphendri

Hello bphendri, problem is SOLVED!
After hard fighting & testing every possible cfg it seems it is 10.6.2 & ISP DNS conflict.
I even bring other router from my friend for testing.
I don't know how to solve problem but in my case I just change DNS server to public.google.dns
it is 8.8.4.4.
It is even faster then my ISP DNS.

Reply