BitJunkie223 (OP)
Member
Offline
Activity: 88
Merit: 10
Vertcoin stealthy master race.
|
|
December 06, 2015, 12:14:48 AM |
|
So I replaced my old D-Link 54mbps router with a TP-Link 300mbps model. The interface feels easier, and my internet speeds have actually bumped up about 2mbps, so it's a win-win. Except...
The SP20's I had running, are no longer connecting properly. They were working fine on my old router, and I had everything configured right, apparently. I set up the new router to be on the same IP, and subnet mask, and all that stuff, thinking it would be plug and play, and I'd just have to reconnect my two laptops to the network, and the miners would start right back up.
I guess I was wrong... They look for a connection with the flashing green light. In fact, the downstairs unit actually lit up solid green for a period, and when I logged into it, it actually showed it was hashing. The upstairs unit no longer feels like working, and the downstairs one keeps spinning up, but fails to start hashing...
First I went back to both the ethernet and the wireless adapter picking IP automatically, and yes, I did enable DHCP on the router. I bridged them together as normal, and it didn't work.
Next, I set them both to unused static IP's, and bridged them (as I've done before with success) and it didn't work.
Then finally, I set them both to static IP's, then set the bridge's IP manually, and that still didn't work...
At this point, I'm convinced this has to do with a setting on the router, and not so much the settings on my laptops that I'm using as controllers... I did set LAN DNS to 192.168.1.1, the IP of the router, which was always the way I set the DNS in the IPv4 settings for the adapters. It was set to 0.0.0.0, and I thought maybe that was making them not work, but setting the DNS as I normally would at 192.168.1.1 still didn't work...
|