That's why virtual serving is a more solid option unless he has multiple IP addresses with which to individually define each server / domain. > > > On Mon, 26 Jul 2004, Garrett Krueger wrote: > >> If you have a domain name registered through some service (such as >> domain >> monger), they probably have a separate entry for the port filled in with >> a >> default value of 80. >> >> If you're doing it yourself, you could try: 192.168.1.2:81 >> where you append the port number directly after the webserver's address. >> You would also have to remember to define this port entry in the >> httpd.conf file. > > Unless domain monger is on some fancy new version of the internet, you > can't just choose arbitrary ports for your website and expect the browser > to automatically figure it out. The browser will send the request to port > 80, unless told otherwise in the URL line. So you can LINK to > http://whatever:where-ever just fine. But going to http://whatever won't > work if the server isn't listening on port 80 for that site. > > > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > Help beta test TCLUG's potential new home: http://plone.mn-linux.org > Got pictures for TCLUG? Beta test http://plone.mn-linux.org/gallery > tclug-list at mn-linux.org > https://mailman.real-time.com/mailman/listinfo/tclug-list > _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota Help beta test TCLUG's potential new home: http://plone.mn-linux.org Got pictures for TCLUG? Beta test http://plone.mn-linux.org/gallery tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list