Hey there,
So I’m trying to access a site from other computers on the network. I can now access sites created with DS just fine. When using the sharing option, it does come up with an IP address, which is the IP of the PC running DS. When plugging in either the hostname or the IP, the user is redirected to hostname or IP/xampp and presented with the ‘New Security Concept’ Message.
I’m running on Win7 in a corp network environment. My PC’s hostname can be resolved, I just get the error message above. Ideally, I’d like to point users to the hostname slash folder name of sites being worked on. Not sure how to accomplish that. But I’m close, I feel.
I’m assuming that this part of the config in xampp-config needs to be changed, but I’m not sure.
#
# New XAMPP security concept
#
Order deny,allow
Deny from all
Allow from 127.0.0.0/8
#Allow from ::1 127.0.0.0/8 \
# fc00::/7 10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 \
# fe80::/10 169.254.0.0/16
ErrorDocument 403 /error/HTTP_XAMPP_FORBIDDEN.html.var
Please advise
Hi Digisavvy,
Unfortunately DesktopServer does not include a DNS server. There are also security implications of modifying all the computers on your network to leverage a third party DNS, but this is beyond the capabilities of DesktopServer’s included abilities. You can, however, modify each of your other computers in the network manually by manipulating their hosts file.
However, let’s first get the sharing feature to work correctly on your current LAN by IP address (also needed if you intend to hack the networking of your other computers to circumvent their DNS settings). When you share a site using DesktopServer’s “Share” feature, what is the IP address that it chooses? You should be able to visit your site on the DesktopServer computer by the given IP address (this is the first check before attempting to access it by another machine/device). Can you visit the site on the same computer with the given IP address?
Regards,
Stephen
Hey Stephen,
I did get the sharing to work.
On line 122 of httpd-xampp.conf I just commented it out and that did the trick. I understand that your product has limits for what it supports and that’s cool. I don’t expect support for things outside what DS Supports.
That said, theoretically speaking, if I had a DNS entry created to resolve hostname.domain.com to point at my PC’s IP, where DS is running, I’d just need to modify vhost entry and the user would be sent to the proper site. More or less correct? In any case, I just want to know if that sounds right. I won’t ask for help troubleshooting it.
You better be at WCLA this weekend, sucka!
=)
You could put your IP in your DNS and it has worked in the past, but I’m not sure how ICANN and a few others feel about private (localhost) IP addresses appearing on Internet DNS. There are several arguments for/against this. Your Windows system admin may have the knowledge to add an entry for you in their LAN “Windows Domain Controller” to do just that, if they are using Windows Server for LAN DNS (most likely if they are using proxy services as well). You’ll need to modify your httpd-vhosts.conf to also include an entry to resolve the domain name to a local folder.
When viewing or editing the httpd-vhosts.conf, be sure that DesktopServer (the app) is not running. You may also want to make modifications outside the ##Begin DesktopServer and ##End DesktopServer comments to prevent your changes from being overwritten.
Hope to be at WCLA, I’m scheduled to and hope to be there but schedules are colliding. I’ll definitely have to show up for one of your meetups; that is a given 
Actually, it would be awesome if you could Skype in to a meetup to talk about your product man. =)
And with regard to resolving hostnames in DNS, it would definitely be on the LAN, accessible only internally.
