|
FreeBSD General Other questions regarding FreeBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|||
Strange issues with 7.2
Hi,
Let's start first with this - a couple of days ago we had to change our ISP and now everything is configured and working, but however there are some small issue that I just cannot understand. At home I have a FreeBSD 6.1 gateway which is doing NAT for the internal network, firewall-ing, etc.. Behind the gateway I've another 7.2 system which I use for file server, and one 7.2 Desktop system, and a couple of Windows machines. Everything is working fine, except for BSDs. First - pinging a remote host from BSD systems takes way too much, than pinging the same host from a Windows machine. Don't know why but resolving hostnames under the FreeBSD systems is taking too much time. On the same 7.2 desktop system I also have Windows XP and Debian installed. Under Debian resolving a remote host also takes a lot of time, while under Windows XP - everything is working just fine! Just to mention - nothing was changed or installed on these systems recently. The second thing is that startx on the 7.2 desktop is taking also a lot of time to start up (usually it was taking ~1 second to load, and now it's taking ~5-10 seconds!). top shows nothing, expect that for a very short period of time hald was doing something - so I disabled it. Rebooted the system and tried to startx and then X couldn't start and I get this errors: Code:
Invalid MIT-MAGIC-COOKIE-1 key Do you know what might be causing this? All BSDs have issues while resolving hostnames, while Windows machines do not..? And X is just waaay too slow now.. That's definitely something that I haven't come across.. until now. Thanks for any feedback and sorry for the long post
__________________
"I never think of the future. It comes soon enough." - A.E Useful links: FreeBSD Handbook | FreeBSD Developer's Handbook | The Porter's Handbook | PF User's Guide | unix-heaven.org |
|
||||
Quote:
Quote:
__________________
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. |
|
|||
Hi,
This morning I re-checked every configuration file and found out that I was having some wrong entries in /etc/hosts - after we changed the ISP seems like that I forgot to update /etc/hosts file as well. I guess I was just too tired last night and didn't notice this Fixing /etc/hosts fixes the startx issue. In the internal network the gateway is also a DHCP server - so it sends the clients the right DNS servers. But however I also re-checked the resolv.conf file on the gateway and yes - it was containing the old DNS servers (another thing that I just didn't notice last night ) So I fixed the resolv.conf entries and did a reboot - just for sure. Results are as follows:
Doing an nslookup from Windows clients sometimes returns this, sometimes resolves normally: Code:
> nslookup youtube.com DNS request timed out. timeout was 2 seconds. *** Can't find server name for address <dns-server1>: Timed out *** Can't find server name for address <dns-server2>: Non-existent domain *** Default servers are not available Server: UnKnown Address: <dns-server1> DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to UnKnown timed-out Code:
nslookup youtube.com Server: <dns-server1> Address: <dns-server1>#53 Non-authoritative answer: Name: youtube.com Address: 74.125.127.100 Name: youtube.com Address: 74.125.67.100 Name: youtube.com Address: 74.125.45.100 After these tests I assume that now BSD systems make a faster DNS lookup and Windows clients sometimes fail to resolve - so I can exclude the possibility that DNS lookups are slower in BSD. I'm outta of other ideas for now. I'll play later with tcpdump and check what goes inside and outside of the gateway. Thanks again for the feedback, I'm open to accept other ideas as well to resolve this issue
__________________
"I never think of the future. It comes soon enough." - A.E Useful links: FreeBSD Handbook | FreeBSD Developer's Handbook | The Porter's Handbook | PF User's Guide | unix-heaven.org |
|
|||
Issue resolved.
The root cause that the primary DNS server was answering very slow. Changed the DNS server and now everything is working fine again
__________________
"I never think of the future. It comes soon enough." - A.E Useful links: FreeBSD Handbook | FreeBSD Developer's Handbook | The Porter's Handbook | PF User's Guide | unix-heaven.org |
|
|||
Quote:
I know nslookup is deprecated, but as you mentioned I don't have any other choice under Windows. But what I still wonder is how those Windows machines automatically switched to the second (working) DNS server. The primary DNS server was not so responsive, and browsing was very slow. Anyway, I've removed the primary DNS server and switched to another one
__________________
"I never think of the future. It comes soon enough." - A.E Useful links: FreeBSD Handbook | FreeBSD Developer's Handbook | The Porter's Handbook | PF User's Guide | unix-heaven.org |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Strange FreeBSD Issues (USB/Nvidia Drivers) | bjstick | FreeBSD Installation and Upgrading | 9 | 10th April 2017 10:57 AM |
Strange lib problem | mururoa | FreeBSD General | 3 | 1st August 2009 07:34 AM |
strange dmesg output | gosha | OpenBSD General | 4 | 11th March 2009 01:10 PM |
PF: strange port 21 | iwi | OpenBSD Security | 3 | 25th November 2008 02:21 PM |
strange with dvd+rw-format | cyberboy | FreeBSD General | 0 | 26th May 2008 05:43 PM |