NET_GetPacket: WSAENETRESET

Ask questions about dedicated servers here and we and other users will do our best to answer them. Please also refer to the self-help section for tutorials and answers to the most commonly asked questions.
Post Reply
Mj93
New to forums
New to forums
Posts: 8
https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
Joined: Fri Jul 04, 2014 8:43 pm

NET_GetPacket: WSAENETRESET

Post by Mj93 »

Hello,

We've been getting an error on our logfiles (Of game servers) lately, which is: NET_GetPacket: WSAENETRESET - i'm not sure what it means exactly, and if it's related to our vps or just a connection issue at the datacenter. it'll flood the server logfile, then nobody is able to connect at that moment, then it's fine again. according to the logs, this happens like twice a day or something. here's a link i found somewhere in the net, of another game, having the same issue and some possible solutions: http://www.esportsheaven.com/threads/182730/ - maybe a router restart at the host can fix this?

I've seen nearly the same problem here: http://www.nfoservers.com/forums/viewto ... =44&t=9559

Fire wall was disabled ever since we started running the game servers (mohaa spearhead).

I've had a look here as well: http://www.nfoservers.com/forums/viewto ... =47&t=8820 - as instructed by a support tech, though i have the same values as in the link above.

hope you can help me out!
Thanks in advance ;-)
User avatar
kraze
Former staff
Former staff
Posts: 4362
Joined: Fri Sep 17, 2010 9:06 am
Location: California

Re: NET_GetPacket: WSAENETRESET

Post by kraze »

Unfortunately, the error itself is pretty generic and doesn't tell us much :/

When did this start occurring and were any changes made to the VDS or server around the time it started?
@Kraze^NFo> Juski has a very valid point
@Juski> Got my new signature, thanks!
@Kraze^NFo> Out of context!
@Juski> Doesn't matter!
@Juski> You said I had a valid point! You can't take it back now! It's out there!
Mj93
New to forums
New to forums
Posts: 8
Joined: Fri Jul 04, 2014 8:43 pm

Re: NET_GetPacket: WSAENETRESET

Post by Mj93 »

First downtime report was on the 1st of July (couple of days ago). It didn't crash or anything, it was only not reachable for a short period of time (I mean the game server which is running on the vps). No changes were made lately. It used to be fine 2 weeks ago. Could it be a DDoS attack?
User avatar
kraze
Former staff
Former staff
Posts: 4362
Joined: Fri Sep 17, 2010 9:06 am
Location: California

Re: NET_GetPacket: WSAENETRESET

Post by kraze »

I'd expect more issues for an attack, but we can sure take a look. Just open a request via the "help" tab and ask us to look for an attack the next time it happens.

If you put up a second instance of your server does it happen on that one as well?
@Kraze^NFo> Juski has a very valid point
@Juski> Got my new signature, thanks!
@Kraze^NFo> Out of context!
@Juski> Doesn't matter!
@Juski> You said I had a valid point! You can't take it back now! It's out there!
Mj93
New to forums
New to forums
Posts: 8
Joined: Fri Jul 04, 2014 8:43 pm

Re: NET_GetPacket: WSAENETRESET

Post by Mj93 »

kraze wrote:If you put up a second instance of your server does it happen on that one as well?
Hello,

I'm not able to test this for some reason.

Could it have to do with the server being run on AFFINITY 02 ? would changing to AFFINITY 01 make any difference?

Would turning on the firewall make any sense aswell?

I requested moving my VDS to a new machine, however that unfortunatly didnt help. our server has been unreachable for over 10 minutes now, which i find weird. i checked the logs and saw this:

Code: Select all

NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPacket: WSAENETRESET
NET_GetPa
I really don't know what this error means, in order to work on fixing it...

Maybe mr.john (or anybody else) can shed some light on on that? i'd appreciate it.

i know NFO is the best out there, so please help me get this fixed soon.
Welshe
New to forums
New to forums
Posts: 2
Joined: Mon Jul 14, 2014 12:58 pm

Re: NET_GetPacket: WSAENETRESET

Post by Welshe »

Maybe its something to do with this?

"Internap appears to have had some sort of problem at its Frankfurt location shortly after 22:00 CEST. This led to packet loss to many clients. We are following up with them to ask what caused this and how they can prevent it from recurring."
Mj93
New to forums
New to forums
Posts: 8
Joined: Fri Jul 04, 2014 8:43 pm

Re: NET_GetPacket: WSAENETRESET

Post by Mj93 »

Welshe wrote:Maybe its something to do with this?

"Internap appears to have had some sort of problem at its Frankfurt location shortly after 22:00 CEST. This led to packet loss to many clients. We are following up with them to ask what caused this and how they can prevent it from recurring."
Yes that might be possible, it happend at around 10 PM CET indeed. my vds is located in Frankfurt. But how come i get this error on a daily basis? well, not as bad as it was today, but i still see it everyday (like 20x the error per 1-day-long log file, which isnt much of an issue, though people complain about it).

The question is; is NET_GetPacket: WSAENETRESET = Lost packet?

If so, is there a way to prevent this network-related-issue from happening again?
Mj93
New to forums
New to forums
Posts: 8
Joined: Fri Jul 04, 2014 8:43 pm

Re: NET_GetPacket: WSAENETRESET

Post by Mj93 »

Internap is having more problems with intermittent packet loss today in Frankfurt. We are attempting to get them to investigate and tell us what is going on.

These are not from attacks against an NFO customer.
Between 03:00 CEST and 04:00 CEST on Thursday, July 17, we will rebooting our router in Frankfurt in order to update its OS, which will in turn improve its performance when dealing with certain types of DDoS attacks. This should result in approximately 3-5 minutes of connectivity loss for your service at this location. The event will be fully scripted, and we have done it successfully at all other locations already.
That explains alright. Hopefully that would fix the issue.
User avatar
Edge100x
Founder
Founder
Posts: 12947
Joined: Thu Apr 18, 2002 11:04 pm
Location: Seattle
Contact:

Re: NET_GetPacket: WSAENETRESET

Post by Edge100x »

It's unlikely that the error that you gave relates to those events.
Mj93
New to forums
New to forums
Posts: 8
Joined: Fri Jul 04, 2014 8:43 pm

Re: NET_GetPacket: WSAENETRESET

Post by Mj93 »

Edge100x wrote:It's unlikely that the error that you gave relates to those events.
Well it seems to have been fixed ;-) so guess it had something to do with the datacenter's router just as i thought indeed!

Ps.: i can PM you the Logfiles if you're interested.
Post Reply