First thought, do you have a firewall that might be blocking incoming network traffic on that port?
Can you connect from a non-web browser (e.g., telnet or nc)? Maybe chrome is doing something odd. -J Thorpe Mayes wrote: > Hi, > > My guess is that this is simple, but it eludes me. > > I have AOLserver 4.5.1 running. Here is the log: > [19/Jul/2012:13:55:06][2047.3049257840][-nssock:driver-] Notice: starting > [19/Jul/2012:13:55:06][2047.3049257840][-nssock:driver-] Notice: nssock: > listening on 64.58.34.215:80 > > > Sure enough, it is listening on 64.58.34.215: > > netstat -tulpn > Active Internet connections (only servers) > Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name > tcp 0 0 64.58.34.215:80 0.0.0.0:* LISTEN 2047/nsd > > > I can ping it: > > --- 64.58.34.215 ping statistics --- > 18 packets transmitted, 18 packets received, 0.0% packet loss > round-trip min/avg/max/stddev = 41.027/42.837/45.061/1.362 ms > > > There is a file to serve in the pages directory. > > > > Yet, when I try to load that file (http://64.58.34.215) in a browser I get: > > Oops! Google Chrome could not connect to 64.58.34.215 > > > What am I missing here? > > Thanks, > > Thorpe > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ aolserver-talk mailing list aolserver-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/aolserver-talk
