I cant open an ip address for an ass...

There are several private address ranges that may be affecting the operations you are attempting to perform see table

IP Address Ranges Reserved for Private Use
Class Networks A 10.0.0.0 through 10.255.255.255 B 172.16.0.0 through 172.31.0.0 C 192.168.0.0 through 192.168.255.0
All addresses in this range in your network are only directly addressable to machines within your network at most by default. The router to your ISP and the internet as a whole maps these addresses onto the IP address assigned statically or dynamically by your ISP to the WAN side of your router using an address translation (NAT) service. So where you are attempting to connect to this device from may be significant. You may need to review your setup guide to see if it references router configuration requirements to support access to the Web_xpander port from devices not attached to your internal network. If you have multiple internal networks (address ranges and not devices) this could also be an issue.

Secondly -- does the Setup software for the device tell you the IP address assuming it is dynamically assigned. Otherwise how would you know what the address is. Static assignment could resolve that issue however you must understand your network to assign your own address. Given a theoretical network where the router gateway is 192.169.0.1 and the network mask is 255.255.255.0 the valid network addresses are 192.168.1.0 - 192.168.1.255. A router or other device supporting DHCP address assignment reserves another range such as 192.168.0.100 for 50 leases (ending at 192.168.0.149) for dynamic assignment to requesting network adapters. Ignoring the 0 and 255 address this leaves open to the network administrator (you in your home) the possibility of assigning static IP address in the ranges of say 192.168.0.2 - 192.168.0.99 and 192.168.0.150 - 192.168.0.254 or so. You as well as the DHCP server are required to assure that there are no duplicate IP addresses assigned on your network. So statically assigning 192.168.0.100 (which is DHCP assignable in our case) could and would most likely result in duplicate addressing and network problems.