That's all proper because 192.x.x.x is an non-routeable IP range. See google rather than me duplicate the web.
As to pinging something on the 192. lan from outside that again is not going to work as we all know what ping is and now we know the non-routeable network ranges.
Re-think your plan and why not put it all on the school lan so it's all visible?
I dont have much experience in networking hope some one can help me with this.
I am in a school network with ip address 166.X.X.X. My XP PC is connected to the network i have an ip of 166.X.X.X. ( i will name my PC as 'PC A'). For a specific project we purchased a win NT 4.0 workstation PC ( i will call this PC 'PC B') and wanted to connect to our network 166.X.X.X so we decided to do a ICS ( internet connection sharing) with my PC A which is in XP everything went well and the PC B was assigned a ip of 192.168.X.X we are able to surf network with both PC A & PC B . but when we want to share files to PC B from my friends PC whos is in the network with ip 166.X.X.X the PC B does not shows! also when we ping the ip of PC B '192.X.X.X' from our ip 166.X.X.X there is no responce but i am able to share files from PC A and also able to ping from PC A.
Is this a limitation in ICS that the client PC will not be shown outside the internal network? any solution to solve this is much appreciated I was suggested that i need to use a dual LAN server if i need to see the clients outside the internal networks...
The reason for me to ping is i need to send some packets to this PC B and wants its response to this.
Thanks, sorry for long description!