HAHA ...you are PWned....24online is a POS that screws up the networking protocols in Windows....For a detailed explanation on how, go to linc.sourceforge.net
1st uninstall 24online client from all machines...Restart and try the pings...once it works, you can take it beyond from there...We had a long and detailed discussion on 24online client and I had put up a guide for Sunnyboi on how to get a LAN up & running with 24online client....
Let me try find that thread
found:
http://www.techenclave.com/forums/hathway-cablenet-doubts-5748.html?highlight=cyberoam
Seriously, if you can switch to another ISP that doesn't use 24online, nothing like it...else, use this at your own risk....
Used to work for me...
Best and easiest method is to remove the client completely (remove all traces from registry ) from the primary machine (the one connected to the ISP) , set up a crossover/wireless connection betweem this and the other mahcine; install the client on the secondary machine...and login from the second machine...
Network sharing and network gaming will also work fine between the 2 PCs..However, plain vanilla pings may not work but that's OK
However, your internal network won't work when you logout from the ISPs network so if u r using a time based connection , ur bad!
Also, whenever your external network (b/w ur home and the ISP ) goes down, ur internal network also won't work
Reason:
Packet Mangling
Credit goes to Ashish Kulkarni for his work on decoding this aspect of the Cyberoam/24Online protocol.
For certain versions of the clients - specifically 1.3.1 (protocol V5) and perhaps others - outgoing IP datagrams are mangled by a packet-level driver installed by the client installation program. This driver goes by the name of "eno2000.sys" and "enonotify.dll". The driver actually alters the "Type of Service" (TOS) octet of each datagram by setting bit 6 (assuming bits are numbered 0 to 7) to 1. Additionally, while the client is not logged in, the packet-level driver resets this bit to 0 for all outgoing IP datagrams. Correspondingly the server hosted by the ISP actively filters all packets and only allows the altered ("flagged") packets to pass.
For more information about the TOS octet, please refer to the Internet Protocol specification (RFC 791) and the Type of Service in the Internet Protocol Suite specification (RFC 1349).
Visit the Slyberoam Software page to learn how you can configure your PC to set the TOS byte to 0x02, without having the eno2000.sys driver installed.
Source:
http://www.rasteroid.com/software/slyberoam/protocol.asp#PacketMangling
Credit: Rahul Mittal
Since the MAC of the NIC connected to the network stays the same, the ISP server is fooled inot believing the setup constitutes of one machine only ...
The disadvantage is that you need to have both PCs on even when you want to use the net on one