CANT CONNECT TO THE SERVARRRRR

Discussion in 'Server Questions / Problems' started by madfire, Jan 22, 2006.

  1. madfire

    madfire Guest

    hi guys, its pretty weird since some weeks (at least 5-6weeks) i cant connect to the server (Awaiting Connection Indefinatly), XFIRE cant get info from the server.. and i cant even PING it. I know that IM the problem (probably). You have an idea why ? Is there other player from SYMPATICO that have problems ?????
  2. Xp1der

    Xp1der M.I.A. Status CallMeMaybe?

    Messages:
    572
    Can you ping the server from your PC?
    All I need to see is the ping statistics.
    If you get 0 received try a tracert on the server
    see where it's bottlenecking

    X
  3. madfire

    madfire Guest

    The ping dont work, Request timed out. And the TRACERT result :

    Code:
    
    Tracing route to 190.56.21.72.reverse.layeredtech.com [72.21.56.190]
    
    over a maximum of 30 hops:
  4. Ralph_Grenader

    Ralph_Grenader M.I.A. Status

    Messages:
    501
    check your lmhost file. i am willing to bet if you use a packet sniffer you will see either your machines firewall/anti spyware program, popup blocker, spyware or router(unlikely) is blocking that address or range of. something on your machine is blocking you from tallking to that router.

    what have you installed in that time frame of six weeks.


    c:WINDOWSsystem32etclmhost

    what antispyware/popup blockers do you use?

    if it's not that IM me i'll get it working, or xp!der will
  5. madfire

    madfire Guest

    i tried to pping and tracert on my laptop(XP) and another computer(win98 no-firewall) and i get error.. BUT on the tracert on my LAPTOP i get this error

    C:Documents and SettingsMick>tracert 72.21.56.190

    Tracing route to 72.21.56.190 over a maximum of 30 hops

    1 1 ms <1 ms 1 ms 192.168.2.1
    2 73 ms 12 ms 12 ms 64.230.197.140
    3 10 ms 10 ms 121 ms 64.230.253.41
    4 80 ms 15 ms 11 ms 64.230.243.121
    5 123 ms 28 ms 52 ms 64.230.173.205
    6 60 ms 21 ms 23 ms 64.230.240.78
    7 21 ms 21 ms 22 ms 206.108.103.194
    8 22 ms 22 ms 22 ms 204.70.150.197
    9 25 ms 22 ms 22 ms 204.70.193.102
    10 24 ms 21 ms 22 ms 204.70.192.194
    11 86 ms 96 ms 48 ms 204.70.192.9
    12 * * * Request timed out.
    13 * * Hardware error.

    Trace complete.


    HARDWARE !! uh
  6. Ralph_Grenader

    Ralph_Grenader M.I.A. Status

    Messages:
    501
    what router are you using. did you buy it or was it provided by your isp. can you get the router out of the equation?

    i'd be lying if i said i knew what the problem was off hand. use some social engineering and ask your isp why you can't connect to that address. tell them that server has military intelligence that is mission critical and they are on a need-to-know basis (they don't need to know). if they don't buy that, refer them to www.askterd.com.

    tell them adogg sent you. i will do it for you if needed, but then i'll have to kill you.
  7. Xp1der

    Xp1der M.I.A. Status CallMeMaybe?

    Messages:
    572
    Normally a "Hardware Error"
    in a tracert doesn't mean the issue is on your end,
    alot of servers don't allow pptp passthrough,
    which Stupid XP uses for tracing, and others don't
    allow "Unframed tcp Packets", a way around that
    is to make sure you have no other internet-enabled
    programs running, Torrents, fileshare, IM Clients,
    AntiVirus, Firewalls (Hardware ans Software).

    Do me a favor, tracert to me specialforcesteam.net,
    and post the log.

    X
  8. madfire

    madfire Guest

    Tracing route to specialforcesteam.net [142.177.195.42]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.2.1
    2 1066 ms 1180 ms 1343 ms 64.230.197.140
    3 1548 ms 1520 ms 1701 ms 64.230.253.41
    4 1525 ms 1391 ms 1608 ms 64.230.243.113
    5 1133 ms 975 ms 933 ms 64.230.173.201
    6 746 ms 852 ms 945 ms 64.230.240.122
    7 1387 ms 1585 ms 1226 ms 64.230.166.82
    8 432 ms 393 ms 277 ms 64.230.166.66
    9 919 ms 983 ms 1190 ms 64.230.203.38
    10 * * * Request timed out.
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 * * * Request timed out.
    14
  9. Xp1der

    Xp1der M.I.A. Status CallMeMaybe?

    Messages:
    572
  10. madfire

    madfire Guest

    ok thank you for your help guys !!

    But all the other hops are pretty high too .. ?!
    Ive put my computer in DMZ, but i still cant connect/ping. And i cant connect to internet without my rooter because its a 'combo' modem/rooter. Its pretty weird because i can play on all my other regulars servers.
  11. elmo

    elmo M.I.A. Status CallMeMaybe?

    Messages:
    1,240
    Restart the router? Sometimes, some routers can get bogged down with 'crap' internally.

    Can you connect to other servers, and if so, where?

    If he were using an anti-virus program (specifically Norton), could this also be a reason? but that brings me back to can you connect to other servers?
  12. elmo

    elmo M.I.A. Status CallMeMaybe?

    Messages:
    1,240
    Actually, you say you haven't tried to connect in 5-6 weeks? What's differenet on your end? New software, new isp, new router, new settings etc.

    Did anyone mention port-forwarding? ALthough, that would seem weird to me...but the router doing something funky with that port wouldn't surprise me...Which I guess can be quickly eliminated if you can connect to other servers.
  13. madfire

    madfire Guest

    yeah i can play on other servers.. i tried too to change the DNS SERVER, but i still have the problem, i pretty sure its not AV related because i tried it on my 4 computer (XP-P,XP-H,98se,LINUX) and i get the same fucking results.. anyway, i think its time to call isp..
  14. madfire

    madfire Guest

    ok, everything seems OK now. During this little 2-months without UAN, i played mostly in Rifles Only server .. and shit, i come back on UAN, ULTRA-FAST gameplay, modded as hell, with mgs..hehe i suck.. ill need some practice
  15. Xp1der

    Xp1der M.I.A. Status CallMeMaybe?

    Messages:
    572
    Nice1 MadFire.
    Glad you got your issues resolved,
    and welcome back.

    X