Blade miner trouble. | Bitcointalksearch.org

EfterlysT

full member

Activity: 425

Merit: 109

Quote from: BigJon901 on September 12, 2013, 07:32:44 PM

It's cause your blade is on a different subnet.

You can either do 2 things.
1. Change your routers subnet to match that of the blade. (Easiest if all other network computers are DHCP (non static ip))
2. Temporary change your subnet to match the blade, go to configuration and change it's IP to the old subnet. Then change the router back to the old subnet. (Safest/More Complicated).

The problem is your network is most likely 192.168.0.XXX the blade is on 192.168.1.254. You see how it's 0.XXX instead of 1.XXX?

Log into your router (I take it you know how to do this)

If i remember correctly for D-Link routers you need to click "setup" on the top tabs and then on the left side click "network settings" tab on the left.

In the new window you will see Router IP Address

It will look something like this 192.168.0.1
Change this number to 192.168.1.1

Next go down to IP range and make sure the maxium (right box) ends with .254 example 192.168.1.254

Now reboot the router and you should be able to access the blade's configuration page. Now from there you can change the IP to the old subnet and then reverse the steps you just did or leave it as be if everything on the network just gets a new IP from DHCP.

Hope this helps you!

Tips: 18ZU96h1ErviqwLKhgh4L8rGcEzRdZuwMm

This made everything easier. My router had 192.168.0.1 and i just switched it to 192.168.1.1 and everything started to work.

Thank you !

wpgdeez

hero member

Activity: 728

Merit: 500

The correct url is http://192.168.1.254:8000/main

RicRock

sr. member

Activity: 290

Merit: 250

You could also change the subnet on your PC temporarily until you configure the blade.

a subnet of 255.255.255.0 will put you on a network of 192.168.0.x

a subnet of 255.255.0.0 will make your "local" network 192.168.x.x

Random8

newbie

Activity: 31

Merit: 0

If you don't want to change any router settings, you could find a small hub or switch (one that's not built into a router), plug the blade into it, and plug a PC's ethernet port into it. On the PC, change its IP address to a static address of 192.168.1.1,
netmask 255.255.255.0. The DNS setting won't matter.

Then, fire up your PC web browser, and point it to http://192.168.1.254:8000. You can then use the web interface to change your blade's IP address to match your router's LAN addresses.

If you have a crossover ethernet cable, you might be able to connect a PC's ethernet port directly to the blade, without using a hub or switch.

-R8

BigJon901

full member

Activity: 199

Merit: 100

It's cause your blade is on a different subnet.

You can either do 2 things.
1. Change your routers subnet to match that of the blade. (Easiest if all other network computers are DHCP (non static ip))
2. Temporary change your subnet to match the blade, go to configuration and change it's IP to the old subnet. Then change the router back to the old subnet. (Safest/More Complicated).

The problem is your network is most likely 192.168.0.XXX the blade is on 192.168.1.254. You see how it's 0.XXX instead of 1.XXX?

Log into your router (I take it you know how to do this)

If i remember correctly for D-Link routers you need to click "setup" on the top tabs and then on the left side click "network settings" tab on the left.

In the new window you will see Router IP Address

It will look something like this 192.168.0.1
Change this number to 192.168.1.1

Next go down to IP range and make sure the maxium (right box) ends with .254 example 192.168.1.254

Now reboot the router and you should be able to access the blade's configuration page. Now from there you can change the IP to the old subnet and then reverse the steps you just did or leave it as be if everything on the network just gets a new IP from DHCP.

Hope this helps you!

Tips: 18ZU96h1ErviqwLKhgh4L8rGcEzRdZuwMm

eastpk

member

Activity: 120

Merit: 10

WINSTARS - We are changing the face of gambling

pm sent.

Nixsy

full member

Activity: 151

Merit: 100

Quote from: EfterlysT on September 12, 2013, 06:13:15 PM

Quote from: Nixsy on September 12, 2013, 06:02:08 PM

Can you verify that the ip the router has assigned the blade is correct? You should be able to view connected devices in the router menu.

If that looks ok, can you open a cmd prompt and type ping [blade internal ip address] and check to see if packets are being rejected.

As a final solution your router may have a "DMZ" demilitarized zone, This is a final option as it completely removes any protection (firewall ect) from this internal up.

I hope this helps a little dude.

Also if you use an android phone download an app called "fing" it can show you a list of all devices connected to the same network as you are on, Great debugging tool for networks.

I cant find the blade if i look in the LAN section. When i update the list i only find my other two stationary computers connected to the router.
I have tried two different blades now with same problem.

I cant find any dmz option in my router. But i have a firewall section and i have shut it down completely. It should accept any connections right now.

I am not sure how else to help dude. Sorry.

EfterlysT

full member

Activity: 425

Merit: 109

Quote from: Nixsy on September 12, 2013, 06:02:08 PM

Can you verify that the ip the router has assigned the blade is correct? You should be able to view connected devices in the router menu.

If that looks ok, can you open a cmd prompt and type ping [blade internal ip address] and check to see if packets are being rejected.

As a final solution your router may have a "DMZ" demilitarized zone, This is a final option as it completely removes any protection (firewall ect) from this internal up.

I hope this helps a little dude.

Also if you use an android phone download an app called "fing" it can show you a list of all devices connected to the same network as you are on, Great debugging tool for networks.

I cant find the blade if i look in the LAN section. When i update the list i only find my other two stationary computers connected to the router.
I have tried two different blades now with same problem.

I cant find any dmz option in my router. But i have a firewall section and i have shut it down completely. It should accept any connections right now.

Nixsy

full member

Activity: 151

Merit: 100

Can you verify that the ip the router has assigned the blade is correct? You should be able to view connected devices in the router menu.

If that looks ok, can you open a cmd prompt and type ping [blade internal ip address] and check to see if packets are being rejected.

As a final solution your router may have a "DMZ" demilitarized zone, This is a final option as it completely removes any protection (firewall ect) from this internal up.

I hope this helps a little dude.

Also if you use an android phone download an app called "fing" it can show you a list of all devices connected to the same network as you are on, Great debugging tool for networks.

EfterlysT

full member

Activity: 425

Merit: 109

Yesterday i got a delivery of old version blade miners.

My internet connection is wireless mobile 3G/4G connection recieved on a D-Link DWR-923.
The Router has four LAN connections and i have tried them all with no luck.
I have turned off the built in firewall and also tried to add portforwarding for 192.168.1.254 and port 8000.

I cant reach the blades interface (192.168.1.254:8000) at all !
I just get a white screeen telling me that the browswe could not connect to the adress.

I cant find any other that having troble with setting theese miners up. Atleast everyone seems to be able to connect to it.
Is my wireless connection the problem ?

When connecting a blade unit to the router it light up orange on the connectors leds, all other connectors is green.
If i connect the network cable from the blade to any other computer it instantly connects to internet. If i put it back into the blade zero luck.

I am stuck at the moment and i suck at network stuff :/

Anyone got some tips ?

Topic: Blade miner trouble. (Read 1321 times)