Alex, Congrats at getting Apache off the ground. Lots of advice here about hardware, but... Are both your WS and Svr Windows boxes? If so, which OpSys? If you want both to share access to the Internet, consider "modem sharing" or "ICS" (Internet Connection Service - IIRC - M$ not v.generous on advice about this, except 50,000 repeat-pages telling you how to get it going). If the problem is simply getting the two machines to 'see' each other, eg for in-house web serving only, then the issue is one of DNS or WINS naming. Which do you use/run a server for? If the answer is basically neither, then we should introduce a static naming system for your two machines (do NOT use this method in conjunction with ICS!): - use WinExplorer to burrow down to C:\WINNT\system32\drivers\etc (YMMV by OpSys) - use Notepad to open "hosts" (NB no filetype/extension or 'dot'). - you should see lines such as: 127.0.0.1 localhost - copy-and-paste that line to a new line below - alter the IP address to the appropriate 192.168.1.n (different on each machine) - alter the "localhost" to a suitable network name for each machine, eg "Fred" and "Barney" - repeat on the other machine (IPaddr and name must be unique/different) - reboot both machines - use DOS box from one to ping the other machine's IPaddr, then networkNm - repeat from other machine - use IE and try both IPaddr and networkNm in Address: field should now work (pre-requisite: holding your tongue correctly) NB have assumed that TCP/IP is up and running on both boxes NBB by repeating the localhost line copy, using the same 192... IPaddr but changing the networkNm, you can add VirtualHosts to your Apache config on that particular machine, ie have more than one named 'web site' under the one server. NBBB the host files are static and easy to maintain in this scenario, but quickly get out of control in a corporate environment - which is why we would then use a WINS and/or DNS server! Hope it helps, =dn ----- Original Message ----- From: "Adam Williams" <awilliam@mdah.state.ms.us> To: "Alex Francis" <afrancis@camerondesign.co.uk> Cc: <php-db@lists.php.net> Sent: Monday, December 09, 2002 8:53 PM Subject: Re: More Apache Installation problems > what you need to do is have 1 nic going directly to your cable modem using > a cross over cable, and then with the 2nd NIC in your WS plug it into the > hub along with the web server box, or ditch the hub and connect the WS to > the web server with a cross over cable. > > Adam > > On Mon, 9 Dec 2002, Alex Francis wrote: > > > Adam, You are correct. > > > > I had two NICs, set up exactly as you describe, but kept getting problems (I > > would lose my internet connection and have to reboot to get it back. I think > > I will try againand if that fails, buy a cable modem router. > > > > "Adam Williams" <awilliam@mdah.state.ms.us> wrote in message > > Pine.LNX.4.33L2.0212091429301.1473-100000@roark.mdah.state.ms.us">news:Pine.LNX.4.33L2.0212091429301.1473-100000@roark.mdah.state.ms.us... > > > No I think he has his WS with a real IP from his ISP and then his web > > > server plugged into the same hub as his WS but with 192.168.1.1. He'll > > > either need to get a 2nd NIC and give it an ip like 192.168.1.2 or get a > > > cable modem router. Or change his WS to linux and add eth0:0 with > > > 192.168.1.2 :) > > > > > > Adam > > > > > > On Mon, 9 Dec 2002, Gene Dymarskiy wrote: > > > > > > > > > > > > > > > > > > > > > > > I am a bit confused. > > > > > > > > Your WS is connected to cable modem and gets public IP assigned by your > > ISP. Your WS is also connected to a hub shared with your web server. > > > > > > > > does it mean you have two network cards, one connected to cable modem, > > and the other to the hub? > > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > From: Alex Francis [mailto:afrancis@camerondesign.co.uk] > > > > Sent: Monday, December 09, 2002 2:20 PM > > > > To: Gene Dymarskiy > > > > Subject: RE: More Apache Installation problems > > > > > > > > > > > > I need to have a server assigned IP address on my workstation for my > > cable > > > > modem. > > > > > > > > -----Original Message----- > > > > From: Gene Dymarskiy [mailto:gdymarskiy@I-DEP.com] > > > > Sent: Monday, December 09, 2002 8:06 PM > > > > To: Alex Francis; php-db@lists.php.net > > > > Subject: RE: More Apache Installation problems > > > > > > > > > > > > I'd check IP address of your workstation. make sure both the WS and the > > > > server are on the same subnet. Your WS should have 192.168.... address, > > too. > > > > > > > > good luck > > > > > > > > -----Original Message----- > > > > From: Alex Francis [mailto:afrancis@camerondesign.co.uk] > > > > Sent: Monday, December 09, 2002 2:00 PM > > > > To: php-db@lists.php.net > > > > Subject: Re: More Apache Installation problems > > > > > > > > > > > > It seems like a network problem. I can access the network through > > windows > > > > network neighborhood but can't ping it, any suggestions? > > > > > > > > "Gene Dymarskiy" <gdymarskiy@I-DEP.com> wrote in message > > > > 3A2D71914B7B4D4986494ED56458B8A7012E55@idep-exch1.i-dep.com">news:3A2D71914B7B4D4986494ED56458B8A7012E55@idep-exch1.i-dep.com... > > > > make sure both your server and workstation can see each other. > > > > > > > > try pinging the server: > > > > > > > > ping 192.168.1.1 > > > > > > > > > > > > > > > > -----Original Message----- > > > > From: Alex Francis [mailto:afrancis@camerondesign.co.uk] > > > > Sent: Monday, December 09, 2002 1:39 PM > > > > To: php-db@lists.php.net > > > > Subject: More Apache Installation problems > > > > > > > > > > > > At last I have Apache and PHP running on my server. > > > > My server IP is 192.168.1.1 and I have set ServerName 192.168.1.1 in my > > > > httpd.conf file. > > > > > > > > I can access my test files from the server using either http://localhost > > or > > > > http://192.168.1.1, however if I try the same on my main workstation I > > can't > > > > find the server. Is there something else I need to do. > > > > > > > > > > > > > > > > -- > > > > PHP Database Mailing List (http://www.php.net/) > > > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > > > > > > > > > > > > > > > -- > > > > PHP Database Mailing List (http://www.php.net/) > > > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > PHP Database Mailing List (http://www.php.net/) > > > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > > > > > > > > > > > > > -- > PHP Database Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
