Not Sure if this is the proper place but tech help needed!

[Derex]

New Issue now...what the hell? Not sure what the fuck is going on with these sudden changes when I'm not changing anything. It seems like it's something with my network as this is effecting my wife's machine also. Can't hit up LNET whatsoever. This is the error messaging. Anyone have an idea?


lnet: No connection could be made because the target machine actively refused it. - connect(2) for "lnet.lichproject.org" port 7155]
lnet:114:in `initialize'
lnet:114:in `open'
[lnet: NilClass is not a valid input stream. It must walk
like either a String, an IO, or a Source.]
C:/Ruby22/lib/ruby/2.2.0/rexml/source.rb:22:in `create_from'
C:/Ruby22/lib/ruby/2.2.0/rexml/parsers/baseparser.rb:128:in `stream='
[lnet: connection lost]
[lnet: waiting 293 seconds before trying to reconnect...]

lol

[gemstonefella]

Yeah, I'm that dumb...no idea what it is.

[gemstonefella]

Ah, I see it's just not me. Guess I should read around first.

[Derex]

Ah, I see it's just not me. Guess I should read around first.

happens :P

[Bryce]

For Wireless gemstone disconnects on Windows 10 fix: disable all Power Management settings in Device Manager, expand Network Adapters, right-click the adapter > Properties > Power Management, and then clear the Allow the computer to turn off this device to save power check box

[Ploobar]

Yeah, I'm getting the same [lnet: waiting 299 seconds...] crap too. Haven't been able to do anything on lnet since early this morning.

What's really strange is, I can kill lnet but if I try to start it again, I get the same damned message. Once in a great while though a chat from someone seems to get through and I can see it in the lnet chat window.

Is it a lot of people having trouble or just a few? Does anyone know?

[Ploobar]

It's back up!!

[Methais]

Yeah, I'm getting the same [lnet: waiting 299 seconds...] crap too. Haven't been able to do anything on lnet since early this morning.

What's really strange is, I can kill lnet but if I try to start it again, I get the same damned message. Once in a great while though a chat from someone seems to get through and I can see it in the lnet chat window.

Is it a lot of people having trouble or just a few? Does anyone know?

This just means LNet is down. It happens from time to time. Local stuff still works like ;go2 and all that, but things like ;locate and chat channels don't.