|
Post by Jeffery McClintock on Mar 23, 2015 15:34:19 GMT -5
Sometimes when I'm racing "10022: Error detected on network device" will come up on the top of my screen and I'll fall out of the server, which is a major inconvenience. This is what I get when I look it up but I don't know how to fix it:
WSAEINVAL
(10022)
Invalid argument.
Some invalid argument was supplied (for example, specifying an invalid level to the setsockopt function). In some instances, it also refers to the current state of the socket—for instance, calling accept on a socket that is not listening.
|
|
|
Post by Deleted on Mar 23, 2015 16:00:38 GMT -5
Time to get a new router
|
|
|
Post by Deleted on Mar 25, 2015 8:12:07 GMT -5
I got an old school Linksys with DD-WRT on it and it works like a charm.
|
|
|
Post by Jeffery McClintock on Mar 25, 2015 21:32:32 GMT -5
Got a replacement router from Bright House and still have the same issues. I'm not sure what the deal is with it.
|
|
|
Post by Jeffery McClintock on May 22, 2015 14:26:12 GMT -5
Anybody know anything about this?
If not, I've probably run my last race.
|
|
|
Post by Gary Piccolo on May 22, 2015 15:12:08 GMT -5
Maybe try replacing the modem next. Other then that try replacing the network cable. How many network ports does your PC have? A lot come with two now and if you have a second one, try that port. Also make sure you have the most recent driver for your network connection.
|
|
|
Post by Jeffery McClintock on May 22, 2015 20:00:03 GMT -5
I'm gonna have to tase it and say it got struck by lightning.
|
|
|
Post by Tom Barber on May 22, 2015 20:44:26 GMT -5
Jeffery, you joke about that but I actually did that to a laptop that the store I bought it from told me they would not replace the motherboard (would not charge the battery) under warranty because it was out by 1 month. They did tell me that it is covered during the second year if it was wiped out buy something like a lightening surge so... Attachment Deleted
|
|
|
Post by Rick Moon on Sept 9, 2016 10:30:27 GMT -5
make sure your Communications settings are right in your core.ini here is the way mine are
[Communications] alternate_ip_addr_lookup=1 ; Find IP addresses another way bcast_listserv= ; IP address of race list server bcast_listserv_port=0 ; list server port (0 = default) bcast_listserv_req_freq=0.000000 ; Request race list frequency bcast_ping_disable=0 ; Disable response to pings bcast_send_disable=0 ; Disable sending broadcasts bcast_send_freq=4.000000 ; Broadcast frequency (seconds) disable_direct_connect=1 ; Disable Direct Connect disable_icmp_checking=1 ; Don't open/check ICMP sockets disable_ipx=0 ; Disable IPX support disable_modem=0 ; Don't look for/use modems disable_network=0 ; Disable network support disable_rasapi32_load=0 ; Disable loading rasapi32.dll disable_tcp_ip=0 ; Disable TCP/IP support ignore_net_read_errors=1 ; Don't disco if error reading pkt ignore_net_send_errors=1 ; Don't disco if error sending pkt ip_addr_lookup_timeout=8 ; Timeout to find own IP address log_server_comm_errors=0 ; Log errors for client channels? log_server_connect_status=0 ; Issue messages as clients connect mem_client_send_every=1 ; Client packet freq via memory mem_client_send_size=532 ; Client packet size via memory mem_server_send_every=1 ; Server packet freq via memory mem_server_send_size=1028 ; Server packet size via memory net_lan_client_send_every=1 ; Client packet freq on LAN net_lan_client_send_size=260 ; Client packet size on LAN net_lan_server_send_every=1 ; Server packet freq on LAN net_lan_server_send_size=772 ; Server packet size on LAN net_mdm_client_send_every=1 ; Client packet freq on dialup net_mdm_client_send_size=116 ; Client packet size on dialup net_mdm_server_send_every=1 ; Server packet freq on dialup net_mdm_server_send_size=116 ; Server packet size on dialup net_server_port=0 ; Server port number (0 = default) net_use_mdm_bandwidth_for_tcp_ip=0 ; Use modem bandwidthfor TCP/IP
|
|