Billion UK Forum

Hi all

I'm new to the forum and new to the Billion products. I very recently purchased a Bipac 7800DX and I'm trying to set it up so that I can remotely access my Windows Storage Server 2008 R2. I've previously had the Server set up on my Cisco router, but this 7800DX isn't very intuitive.

When I run the Remote Server setup from the Server, it checks to see if the router is Upnp enabled - which it is. But when trying to set up the port forwarding automatically, there is an error returned saying that the router doesn't support upnp This was the same on the Cisco router too, so I blame Windows for that one - actually, I blame Windows for everything - unless I'm using the MacBook Pro Retina as that is a pain too

I have an account with DynDns and the updater is working fine - I have confirmed the IP address issued by my ISP is getting updated with DynDns.

Can someone tell me in very simple steps (assuming I know nothing about this router) how to configure port forwarding so that I can access my Windows Storage Server 2008 R2 device remotely please?

It would also be helpful if someone can give me an idea how to set up the same router so I can connect to my CCTV and anything else that I want to access remotely - I assume I have to set up port forwarding for all devices, but how do you determine what ports should be used and forwarded? What are they forwarded to?

Thanks in advance, and I hope I haven't missed any important details

Rodger wrote:Hi all

I'm new to the forum and new to the Billion products. I very recently purchased a Bipac 7800DX and I'm trying to set it up so that I can remotely access my Windows Storage Server 2008 R2. I've previously had the Server set up on my Cisco router, but this 7800DX isn't very intuitive.

When I run the Remote Server setup from the Server, it checks to see if the router is Upnp enabled - which it is. But when trying to set up the port forwarding automatically, there is an error returned saying that the router doesn't support upnp This was the same on the Cisco router too, so I blame Windows for that one - actually, I blame Windows for everything - unless I'm using the MacBook Pro Retina as that is a pain too

I have an account with DynDns and the updater is working fine - I have confirmed the IP address issued by my ISP is getting updated with DynDns.

Can someone tell me in very simple steps (assuming I know nothing about this router) how to configure port forwarding so that I can access my Windows Storage Server 2008 R2 device remotely please?

It would also be helpful if someone can give me an idea how to set up the same router so I can connect to my CCTV and anything else that I want to access remotely - I assume I have to set up port forwarding for all devices, but how do you determine what ports should be used and forwarded? What are they forwarded to?

Thanks in advance, and I hope I haven't missed any important details

Everything you want to do is set with 'NAT >> Virtual Server' section, this section is Billion's port forwarding page. You select the internal IP (win storage server internal IP) the protocol eg TCP or UDP and the ports that need to be opened eg 1723.

The same goes the CCTV camera's, first find out the internal IP address, then find out the ports the device use eg 8080, then setup some virtual server rules for the devices (CCTV)

You should be able to find the ports used by logging into the CCTV equipment, or refer to the manual, regarding the IP address, you can either check the DHCP table, and match the MAC address of the device to the IP address listed here, or login to the CCTV camera and check the network settings

I hope this helps

Thanks a Billion for the prompt response

I have to go out at the moment but I'll check what I've done already because I'm fairly sure I did something along those lines and it didn't work I'm only trying to set up the Server at the moment and I gave it a fixed IP address to make my life easier. I'll report back if I get further issues or require additional information - or if I get it working

Well that didn't seem to want to work So I've fired off an email to the people who make the Server and I'll see what they come back with. Maybe between the information I have here and the information they give I will be able to get this working

It's probably the port numbers which are required to punch holes in the connection or whatever it is they do, but I haven't got a clue what they should be to be honest so I'll leave it to the manufacturer to tell me

Rodger wrote:Well that didn't seem to want to work So I've fired off an email to the people who make the Server and I'll see what they come back with. Maybe between the information I have here and the information they give I will be able to get this working

It's probably the port numbers which are required to punch holes in the connection or whatever it is they do, but I haven't got a clue what they should be to be honest so I'll leave it to the manufacturer to tell me

Your right, once you have the correct ports added to the virtual server section with the internal IP entered, these ports/devices should then be exposed to the internet