>> I ran the following test: >> >> Test 1; Connecting to Apache's default html page from laptop to server via >> WiFi >> >> URL: http://192.168.1.10 >> >> Results: I get Apache's "It works!" page in less than a second >> >> >> Test 2; Connecting to Ledgersmb's setup.pl from laptop to server via WiFi >> >> URL: http://192.168.1.10/ledgersmb/setup.pl >> >> Results: It takes on average about 13 seconds for this page to open. >> >> >> Test 3; Connecting to Ledgersmb's setup.pl directly from server. >> >> URL: http://localhost/ledgersmb/setup.pl >> >> Results: It takes on average about 4 seconds for this page to open. Same >> thing if I substitute 192.168.1.10 for localhost in the server's browser. > > This is starting to sound suspiciously like a DNS problem, not a > LedgerSMB problem. > > First check /etc/resolv.conf, then use dig (dig google.com). Near the > bottom of the output, you should see the server used. That server > should be the first in the /etc/resolv.conf list. > > Run a tcpdump and watch port 53 -- see what you get (or don't get).
Unless I am missing something, isn't the fact that I am using an IP address (http://192.168.1.10/ledgersmb/setup.pl) instead of a hostname bypass DNS ruling it out? All my tests are run from my private local network (192.168.1.x). ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Ledger-smb-users mailing list Ledger-smb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ledger-smb-users