Good point - I forgot about the hosts file on each machine - duh.
That should take care of any IP name resolution issues.
From a networking standpoint, I have Samba configured to be domain master, local master, preferred master, and os level 255, and all PCs WINS set to the server IP.
The server is always on.
I think I need to concentrate on getting Samba networking consistently with Winblows before moving forward with the website issue.
Thanks to all for your time and support.
Last edited by molinus; January 13th, 2011 at 09:19 PM.
when you say you pinged the hostname, you need to clarify this.
avahi hostnames are only useful in my example if you use the hostname they create :
so if your ubuntu machine is called "heimdal", then the avahi hostname for it will be heimdal.local
here is a valid virtual-host definition file for such an address :
a. assuming your network device is eth0, and
b. that you have disabled the defaul virtual-host :
c. make sure that /etc/apache2/sites-enabled no longer contains files named "default"Code:sudo a2dissite default sudo a2dissite default-ssl
1. For development purposes add yourself to the apache usergroup.
2.Create the virtual host file system for the virtual hostCode:sudo adduser $USER www-data
3. Modify the permission giving ownership to the apache user group. and making it readable by any user account on the machine.Code:sudo mkdir /var/www/heimdal.local/logs -p sudo touch /var/www/heimdal.local/logs/errors.log sudo touch /var/www/heimdal.local/logs/access.log sudo touch /var/www/heimdal.local/logs/authentication.log sudo mkdir /var/www/heimdal.local/cgi-bin -p sudo mkdir /var/www/heimdal.local/db -p sudo mkdir /var/www/heimdal.local/public_html -p sudo mkdir /var/www/heimdal.local/public_html/css -p sudo mkdir /var/www/heimdal.local/public_html/js -p sudo mkdir /var/www/heimdal.local/public_html/img -p sudo touch /var/www/heimdal.local/public_html/index.html sudo touch /var/www/heimdal.local/public_html/favicon.png sudo touch /var/www/heimdal.local/public_html/favicon.ico
4. Create the virtual host definition file for the new virtualhostCode:sudo chown www-data:www-data /var/www/heimdal.local/ -R sudo chmod 775 /var/www/heimdal.local/ -R
Paste the followingCode:sudo nano /etc/apache2/sites-available/heimdal.local
save it :Code:<VirtualHost *:80> ServerAdmin root@localhost ServerName heimdal ServerAlias heimdal.local DocumentRoot /var/www/heimdal.local/public_html <Directory /var/www/heimdal.local/public_html/> Options Indexes FollowSymLinks MultiViews AllowOverride All Order allow,deny allow from all </Directory> Alias /robots.txt /var/www/heimdal.local/public_html/robots.txt Alias /favicon.ico /var/www/heimdal.local/public_html/favicon.ico LogFormat "'time'='%t', 'user'='%u', 'client-ip'='%a', 'server-ip'='%A', 'server-name'='%v', 'url'='%U', 'status'='%>s'" authentications ErrorLog /var/www/heimdal.local/logs/errors.log CustomLog /var/www/heimdal.local/logs/access.log combined CustomLog /var/www/heimdal.local/logs/authentications.log authentications </VirtualHost>
5. Enable it :Code:ctrl + o ctrl + x
6. Allow access to the apache and avahi ports :Code:sudo a2ensite heimdal.local sudo service apache2 restart sudo service avahi-daemon restart
7. access it via avahi/bonjour enabled operating systems withCode:sudo ufw allow in on eth0 to any port 80 sudo ufw allow in on eth0 to any port 5353
Last edited by airtonix; January 14th, 2011 at 11:26 AM.
Fear is the mindkiller....
The little death that obliterates...
So if I have correct.
Your MACs can all connect to the website using the serverip or hostname. They can access the Samba shares with no issues?
Your PCs can do none of the above?
Are your MACs and PCs recieving the same IP address etc. from the same DHCP server or are they static?
If it is working for the MACs and not the PCs then I don't think it is a Ubuntu issue, it is an issue on the PCs. I don't understand how you get no replies from a PING but you are then able to browse to the Samba Share on the Server.
On a PC do start->run->//serverip and OK. This will connect to the Samba Share on the Server. If that works then I fail to understand why you cannot access the websote on the same server
Do you have some group policies being pushed on the PCs?
Anything different with the network configuration between the MACs and PCs?
Have you tried bringing in another PC (like a laptop running Win) just to see if there is something funky with the PCs in your network?
It definitely seems client-related if the other machines on your network don't have an issue getting to the server.
Oh, I didn't ask - you said all IPs are static, did you put in default gateway and DNS information on the network interfaces? Stupid question, I just am grabbing at straws here!
Re posts #16 & 17:
I am grasping at straws too - all machines have Internet access, and Gateway / Mask / DNS / WINS IPs are configured correctly (see the numbers 1-4 mentioned in post #15).
Here are the spooky results of my test running 200 pings of 32 bytes to the server:
The first 188 pings timed out.
The last 12 responded!
time to reply - 3263ms for the first one, two at 1ms, one at 250ms, and the other 8 at 1ms.
I am now on a quest.
On three different Windows machines (laptop running XP Home - desktop running XP Professional - desktop running Windows 7) I got the same results: after awhile it would connect and I had access to mywebsite and all server shares. 5 minutes later it would not connect.
The 3 Macs have been connected to the server all day with no interruptions...
Last edited by molinus; January 14th, 2011 at 06:58 PM. Reason: Update