In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED] writes >You didn't tell us the full IP's. It is fine to post IP's starting with >192.168.xxx.xxx as these addresses are reserved for LAN use and are not >internet accessible.
It wasn't a security issue, it was a memory issue! <G> I just can't remember... >If one IP is 192.168.0.xxx and the other is 192.168.1.xxx or they are >different in the third xxx then you may have an issue with your subnet >mask. >If the third (as above) is different then your subnet needs to be >255.255.0.0 If only the fourth (last) xxx is different then your subnet >mask >can be either 255.255.0.0 or 255.255.255.0 All the computers on the network are 192.168.1.x, with subnet mask 255.255.255.0 >Go to the machine that is not network accessible It is network accessible - I can ping it, and I can access files in the shared area, as I can with all computers on the network. > and type localhost into >a >browser - this should work. It does. > Then type its IP follower by the port (:80) >into >a browser. example - >192.168.xxx.xxx:80 >Then type 192.168.xxx.xxx:80 (with the non working servers IP) from >another >PC. If this doesn't work from another PC then go back to the non-working >server and disable the firewall and test again from the other PC. > >Post your results and we can tell you how to configure your firewall. >Please >not that other security software can interfere to so mention what >security >software you have on the non-working PC - like - Norton Security etc I think that it just has Windows Firewall, but I can't really be sure. But I will follow your instructions on Monday, and see what happens. -- Pete Clark Sunny Andalucia http://www.hotcosta.com/comm_1.htm
