win machine A is connected to internet (naked) by @home cable modem with static ip address in city A with a subnetmask of 255.255.252.0
e-smith machine B (4.0b5 server only - dedicated) is connected to internet on an institutional network in city B.
A's ip address is designated as a local network on e-smith machine B. BUT, if A's correct subnetmask (255.255.252.0) is entered into B's local network setup, A cannot ftp or telnet to B, but A can access B's e-smith manager. By entering 255.255.255.0 for A's subnetmask on B's local network setup (although it's really 255.255.252.0) A has ftp, telnet, and e-smith manager access to B.
Is this a bug with 4.0b5, or is there some other reason for this?
Glenn Kennedy
0 Replies
818 Views