Well, now we're diagnosing a web browser or operating system problem.
To do that, we're going to need to know more about the computer, the operating system, and the browser. Version numbers and service packs and other information (like "Windows XP SP3" or "Internet explorer 8.01") would be great.
It would help if you could describe in detail the other devices connected to the network, like with a list of IP addresses.
I don't like to rely on PING to tell me that devices are really connected and configured. There's too much chance of there being an IP conflict or an incorrect assumption about which device is which.
There's an excellent piece of freeware called "TCPING" (
www.elifulkerson.com). You can use that utility to verify connectivity to devices using a TCP connection instead of the more basic "PING" command. Using TCPING on TCP Port 502 proves you're talking to a Modbus/TCP device, and on TCP Port 44818 it's EtherNet/IP. TCP Port 80 is the standard HTTP port, so you can be sure the device is responding in some way to your HTTP request.
The ports might not yet be set up for EtherNet/IP or Modbus/TCP, but they should definitely respond to TCPing on Port 80.
When you type the IP address of the gateway into your web browser... exactly what do you see ? Is there any sort of frame or page that suggests that the Anybus-X is responding at all ?
It might help to right-click on the resulting web page and select 'show source', to tell you more about how the Anybus-X is responding to the HTTP request.
Are you familiar with using Alt-PrintScreen and control-V in MS-Paint to capture screenshots ? A screenshot might be very helpful.