Menu
What's new
By:
Filters

Interesting SA:MP bug

Status
Not open for further replies.
.stephen

.stephen

Retired Admin
Joined
Mar 11, 2017
Messages
7,763
Location
the south
So I've got a pretty interesting SA:MP bug where some of the servers aren't working on the server list, and some are working perfectly and I'm able to connect with no problems. Pretty much, server'll just be stuck on 0/0 as if it was offline, and when trying to remove/re-add it it'll just stay stuck at (Retreiving info...), also like if it was offline.
When trying to connect it'll just try n try to connect with the same message of "The server didn't respond, retrying...".

I've tried multiple things to try and fix it so please don't suggest anything too obvious as there's a chance I've already tried it:
  • Removing and then re-adding the server to the list.
  • Disabling and re-enabling the network adapter
  • Reinstalling SA:MP
  • Restarting my PC (Twice)
  • Restarting the router
  • Disabling the Windows Defender Firewall
  • Refreshing the server list (Like that'd be of any help :LUL: )
  • Deleting samp.cfg and userdata.dat
  • Connecting with the numerical IP
  • Deleting the SAMP folder in GTASA User Files completely.
  • Reinstalling GTA:SA completely
  • ipconfing /flushdns method, ipconfig /release > ipconfig /renew method also.

None helped, soooo, I guess I'm here asking for help, plzfixmygametyvm!

79123
 
Last edited:
.stephen

.stephen

Retired Admin
Joined
Mar 11, 2017
Messages
7,763
Location
the south
RCRP diagnostics tool test results, if that can be of any use with my problem :shrug:

Running RC-RP Diagnostics test...
Retrieving system date and time.
Fri 12/20/2019
12:11 PM

------- Ping/Traceroute to EU.FROSTGAMING.COM -------:

Pinging eu.frostgaming.com [185.198.188.98] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 185.198.188.98:
Packets: Sent = 8, Received = 0, Lost = 8 (100% loss),

Tracing route to eu.frostgaming.com [185.198.188.98]
over a maximum of 30 hops:

1 7 ms 5 ms 5 ms 10.74.64.1
2 7 ms 6 ms 7 ms 172.20.2.5
3 13 ms 18 ms 6 ms 10.160.0.1
4 * * * Request timed out.
5 7 ms 17 ms 31 ms 213.133.1.92
6 13 ms 15 ms 12 ms 212-200-250-221.static.isp.telekom.rs [212.200.250.221]
7 31 ms 60 ms 13 ms 212.200.7.67
8 64 ms 54 ms 59 ms linx-lon1.thn2.peering.clouvider.net [195.66.227.14]
9 47 ms 47 ms 48 ms h185-198-188-93.reverse.clouvider.net [185.198.188.93]
10 * * * Request timed out.
11 58 ms 100 ms 51 ms 185.198.188.3
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

------- Ping/Traceroute to SERVER.REDCOUNTYRP.COM -------:

Pinging server.redcountyrp.com [185.198.188.100] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 185.198.188.100:
Packets: Sent = 8, Received = 0, Lost = 8 (100% loss),

Tracing route to server.redcountyrp.com [185.198.188.100]
over a maximum of 30 hops:

1 5 ms 5 ms 5 ms 10.74.64.1
2 8 ms 6 ms 5 ms 172.20.2.5
3 6 ms 10 ms 6 ms 10.160.0.1
4 * * * Request timed out.
5 7 ms 7 ms 6 ms 213.133.1.92
6 12 ms 14 ms 12 ms 212-200-250-221.static.isp.telekom.rs [212.200.250.221]
7 12 ms 13 ms 12 ms 212.200.7.67
8 94 ms 66 ms 43 ms linx-lon1.thn2.peering.clouvider.net [195.66.227.14]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 50 ms 61 ms 50 ms 185.198.188.3
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

------- Ping/Traceroute to GOOGLE.COM -------:

Pinging google.com [216.58.214.238] with 32 bytes of data:
Reply from 216.58.214.238: bytes=32 time=17ms TTL=54
Reply from 216.58.214.238: bytes=32 time=18ms TTL=54
Reply from 216.58.214.238: bytes=32 time=17ms TTL=54
Reply from 216.58.214.238: bytes=32 time=18ms TTL=54

Ping statistics for 216.58.214.238:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 18ms, Average = 17ms

Tracing route to google.com [216.58.214.238]
over a maximum of 30 hops:

1 6 ms 5 ms 5 ms 10.74.64.1
2 6 ms 6 ms 5 ms 172.20.2.5
3 13 ms 10 ms 6 ms 10.160.0.1
4 * * * Request timed out.
5 7 ms 7 ms 7 ms 213.133.1.92
6 12 ms 15 ms 13 ms 212-200-250-221.static.isp.telekom.rs [212.200.250.221]
7 40 ms 21 ms 21 ms 79.101.106.2
8 17 ms 19 ms 18 ms 74.125.242.225
9 17 ms 17 ms 18 ms 72.14.237.209
10 17 ms 18 ms 18 ms bud02s24-in-f14.1e100.net [216.58.214.238]

Trace complete.

IPconfig information:

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-DP6INLS
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : BC-EE-7B-E0-D1-C5
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::eda7:26ea:a40c:d348%3(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.102(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, December 20, 2019 11:46:29 AM
Lease Expires . . . . . . . . . . : Saturday, December 21, 2019 11:46:29 AM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 113045115
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-24-51-5D-59-BC-EE-7B-E0-D1-C5
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

*****Test Complete*****!
12:21 PM
Fri 12/20/2019
 
Giga

Giga

Donator
Joined
Dec 4, 2010
Messages
18,985
Location
MNL
Looks like the server is unreachable from your network for some reason. Based on the results, your network can ping the origin data center but not ping the server itself.

Probably a @fr0st thing at this rate. inb4firewallban
 
attilathehun

attilathehun

Silver Member
Joined
Dec 10, 2019
Messages
686
Location
MARS
found a temporary solution, on sa-mp; (LINK REMOVED - not allowed without management's permission) and click save button. It worked for me.
 
Last edited by a moderator:
Status
Not open for further replies.
Top