Actually, the problem is more insidious than that.
When I'm on .3.x and the player is on .4.x, even if I spec the player's IP address directly in the Emplode connection screen, it does not connect.
In which case tman's right, there's something borken about your network. That's a direct TCP connect to a specific address, and if it doesn't work then the two hosts are not actually (in some sense) on the same subnet,
and routing between the subnets is broken. (Or is via a zealous firewall that blocks Emplode's TCP port.)
What happens, in the .3-and-.4 case, if you then try and ping the Empeg? Or connect to another service (i.e. not Emplode -- say, Hijack's HTTP or FTP if you have that installed)? If you can ping it, traceroute it. What is the PC's routing table ("route" command on Linux, can't remember what it's called on Windows)?
When we're both on the same subnet (.3 or .4), the network broadcast still doesn't work. But at least if I spec the IP address directly they work.
This is actually all a bit academic, as I'm sure if I asked our network guy if he could give me a couple of static reservations, he would. He's just in the office next to my cube. Doing this would solve my immediate problem, but I'm also interested in the general case, what causes it, and how one would work around it.
Sure, it's about the journey not the destination. There's a clear brownie-points difference between saying to the network guy "What's up with this .3.x and .4.x thing?" and saying "The way you've set this up to do
well-wonky-thing-X is well wonky"
Peter
Previous Topic
Index
