PokerStars homepage
  • If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Announcement

Collapse
No announcement yet.

PLEASE TAKE PART IN THIS POLL

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • PLEASE TAKE PART IN THIS POLL

    Hi everyone, I am now happy that we have gotten over the initial problems of moving our servers last week. I would now like to focus on improving the experience of you all while playing on our software. I am going to have an ongoing interaction here in this "General" forum and this will be the first poll.

    I am interested to know as much about the experiences as possible from as many of you as possible. I am particularly interested in timing out issues.

    Please answer the following poll and reply in this thread if you experience timing out during your play. I am only talking about timeouts that you have no control over. This feedback is essential for me to try to determine whether or not we have a software issue or it is simply internet (router) problems.

    Any of you that are capable of running a tracert and copying it and emailing it to me or better still, posting it in this thread would also help a lot.

    One last thing, any of you that experience time outs, could you please turn your sounds off and then let us know if this solves the problem for you.

    I really appreciate everyones help on this. Please, if you are NOT having problems could you also answer this poll.

    Mark

  • #2
    My experience...

    Mark, I almost never timed out before this latest move. I have a fairly stable cable connection and a relatively new machine running Windows 2k.

    Also, this forum seems to have become very unpredictable. When moving from one message to the next, it just locks up. I can go back and forth a few times using the browser and eventually things seem to work normally.

    I am not experiencing any problems using other sites or any problems on the various cash play sites I visit.

    Thanks for your efforts. I know, as do we all, that it must be very frustrating...especially when you are several thousand miles and an ocean away from the site of the problem.

    By the way, I know that some have mentioned how nice a refund would be for the down time and trouble all of your customers have experienced during this period. Here’s another thought, how about accelerating one or two of Andy’s or Rolf’s lesson plans. I don’t think most of us would have a problem absorbing more than one a week. :lol:.

    Another concept might be, and here I know I begin to tread on dangerous ground 8O , but how about a different level of access for the annual members.

    In other words, if you are an annual member, you could access a three-month series of lessons from day one as opposed to the one per week. This might also be an incentive for some to move from monthly to annual membership.

    Just an idea and something for you to think about. By the way, I hope you and your family, especially the poor puppy, are settling into their new environs successfully.

    Later…

    Steve

    Comment


    • #3
      tracert

      :roll:
      I'll be glad to run a tracert or attempt this action if you can discribe the action. I could not find this action in my help desk file. I have a cable internet connection

      Is this similar to doing a "ping" using a hexi-decimal url code (if yes, what is the hexi-decimal code for the site I need to ping).

      I ping'd:
      Pokerpages.com (216.166.66.128) with 32 bit data
      request timed out
      :

      pokerschoolonline.com(216.166.66.128) with 32 bit data
      request timed out
      :

      Comment


      • #4
        It seems to me that the problem could easily be with our new ISP and in particular the firewall at that ISP. I will be talking to them and Gavin later today (Wednesday)

        In the meantime any of you that can run a tracert immediately after you time out and post it here would help.

        For those that do not know how to run one this is how to:

        click "start"
        click "run"
        type: command
        you will be at a DOS prompt

        type : tracert me2.pokerpages.com

        Once the result is in the window and the tracert is finished please copy it and post it here in this thread.

        Mark

        Comment


        • #5
          Lost connection to server (pokerpages) And had to restart my client!
          Happens often today and yesterday



          Traceroute:
          __________
          Sp†rar v„g till me2.pokerpages.com [216.166.66.128]

          ”ver ett maximalt antal av 30 hopp:



          1 <10 ms <10 ms <10 ms 148.160.248.9
          2 <10 ms <10 ms <10 ms bkman-bm01.adm.boras.net [148.160.201.73]
          3 <10 ms <10 ms <10 ms 148.160.250.1
          4 <10 ms <10 ms <10 ms vrr-a2-atm9-0-0.telia.net [194.236.189.205]
          5 <10 ms 10 ms <10 ms vrr-d1-feth2-0-dist.goteborg.telia.net [195.198.162.1]
          6 <10 ms <10 ms 10 ms 213.64.49.101
          7 10 ms 10 ms 10 ms fre-b1-pos2-2.se.telia.net [213.64.62.121]
          8 10 ms 10 ms 10 ms s-b3-pos2-0.telia.net [213.248.67.61]
          9 10 ms 10 ms 10 ms s-bb1-pos1-0-0.telia.net [213.248.64.141]
          10 20 ms 20 ms 30 ms kbn-bb1-pos3-1-0.telia.net [213.248.64.129]
          11 100 ms 101 ms 110 ms nyk-bb1-pos0-2.telia.net [213.248.64.10]
          12 120 ms 120 ms 131 ms chi-bb1-pos0-1-0.telia.net [213.248.80.6]
          13 120 ms 120 ms 130 ms at-t.telia.net [213.248.84.70]
          14 120 ms 140 ms 130 ms tbr2-p012702.cgcil.ip.att.net [12.122.11.209]
          15 * * * Beg„ran gjorde time-out.
          16 140 ms 150 ms 141 ms 12.122.10.89
          17 141 ms 150 ms 140 ms gbr1-p70.dlstx.ip.att.net [12.122.12.78]
          18 141 ms 150 ms 150 ms gbr4-p00.dlstx.ip.att.net [12.122.5.226]
          19 140 ms 151 ms 150 ms gbr1-p80.auttx.ip.att.net [12.122.2.110]
          20 150 ms 141 ms 150 ms gar1-p360.auttx.ip.att.net [12.123.133.21]
          21 150 ms 150 ms 151 ms 12.124.219.46
          22 151 ms 150 ms 150 ms lc1.gw3.aus1.texas.net [216.166.60.4]
          23 * * * Beg„ran gjorde time-out.
          24 * * * Beg„ran gjorde time-out.
          25 * * * Beg„ran gjorde time-out.
          26 * * * Beg„ran gjorde time-out.
          27 * * * Beg„ran gjorde time-out.

          Comment


          • #6
            I tried running tracert, but the ms-dos window closes automatically once it's finished, and it won't allow cut & paste while it's running....so I couldn't get anything.

            I don't believe, however, this has anything to do with our side. From observation, it truly appears that it's with your ISP. My experience is much like Steve's, in that I never had a problem before the switch, now it happens a lot. It looks like the ISP does not have sufficient bandwidth to support whatever traffic is going through their pipe (this may not just be you). It is USUALLY volume related on PSO, and the more players we have on, the more likely it is to time out, but this is not always the case. I have had trouble with the website timing out this morning (pre-6:00 AM), and I'm sure you're not generating traffic now.

            Whenever the problems start, they are likely to intensify until traffic slows down. I'm blaming the pipe because the forum and the game server usually have trouble at the same time, and if they're on different servers, it's unlikely this would be a configuration problem in the server itself. On the other hand, since most of us use both at the same time, both could be increasing volume at the same time, and it could be a config issue.

            I would recommend getting monitors put on that watch the traffic levels, CPU utilization, interrupts, etc. Have someone personally bring up an IM session that you publish (obviously a temporary account, because this will get ugly). In fact, since AOL, MSN, and Yahoo messengers all seem to be widely used, you may want 3. When performance goes downhill, have the players IM you to tell you that NOW it's bad...since trying to figure it out after things are ok again will never work. I don't know if you really see exactly HOW bad it gets, but this will let you. If people IM you after every timeout, I think you'll see hundreds an hour when things are bad, even though only a portion of the members will bother to respond. Use this as a guide to monitor to tell you when you're in trouble, to have the numbers you're monitoring make sense, and to let you see why everyone is as frustrated as they are.

            As someone else mentioned, if you don't feel you have the best internet minds in Austin on this, I'd bring them in. There is truly a danger of seeing lots of people bail out because of this problem.

            Comment


            • #7
              tracert

              Here is one:
              Tracing route to me2.pokerpages.com [216.166.66.128]
              over a maximum of 30 hops:

              1 17 ms 14 ms 14 ms cdm-208-198-1-gnvl.cox-internet.com [208.180.198
              .1]
              2 27 ms 27 ms 24 ms 172.16.66.73
              3 46 ms 48 ms 43 ms 12.125.64.17
              4 50 ms 46 ms 72 ms gbr6-p50.sl9mo.ip.att.net [12.123.24.126]
              5 42 ms 45 ms 47 ms tbr2-p013501.sl9mo.ip.att.net [12.122.11.121]
              6 75 ms 83 ms 75 ms 12.122.10.89
              7 57 ms 57 ms 54 ms gbr1-p70.dlstx.ip.att.net [12.122.12.78]
              8 82 ms 58 ms 62 ms gbr4-p00.dlstx.ip.att.net [12.122.5.226]
              9 61 ms 58 ms 65 ms gbr1-p80.auttx.ip.att.net [12.122.2.110]
              10 64 ms 93 ms 76 ms gar1-p360.auttx.ip.att.net [12.123.133.21]
              11 85 ms 63 ms 69 ms 12.124.219.46
              12 65 ms 65 ms 66 ms lc1.gw3.aus1.texas.net [216.166.60.4]
              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.
              It ran a total of 30 hops and 21 thru 30 were also 'request timed out'

              I hope this helps

              Comment


              • #8
                Last night was the first time I've played with the new server and I timed out 11 times. In the previous ~100 tournaments I'd timed out no more than half a dozen times total.

                Comment


                • #9
                  Can any of you confirm that what you are experiencing is a disconnect as opposed to timing out. These are two very different things and I want to be able to investigate the correct problem.

                  A time out simply times you out of the current hand whereas a disconnect means you have to restart the program.

                  Mark

                  Comment


                  • #10
                    acing route to me2.pokerpages.com [216.166.66.128]
                    er a maximum of 30 hops:

                    1 10 ms 10 ms 31 ms 10.105.208.1
                    2 * * * Request timed out.
                    3 * * * Request timed out.
                    4 10 ms 10 ms 10 ms 68.39.224.162
                    5 10 ms 20 ms 10 ms 12.125.176.121
                    6 40 ms 20 ms 20 ms gbr2-p70.phlpa.ip.att.net [12.123.137.26]
                    7 10 ms 20 ms 21 ms gbr4-p40.wswdc.ip.att.net [12.122.2.85]
                    8 30 ms 30 ms 30 ms gbr4-p30.attga.ip.att.net [12.122.2.225]
                    9 41 ms 40 ms 50 ms gbr3-p20.dlstx.ip.att.net [12.122.2.89]
                    0 40 ms 40 ms 40 ms gbr4-p60.dlstx.ip.att.net [12.122.1.138]
                    1 40 ms 50 ms 50 ms gbr1-p80.auttx.ip.att.net [12.122.2.110]
                    2 50 ms 50 ms 40 ms gar1-p360.auttx.ip.att.net [12.123.133.21]
                    3 50 ms 50 ms 50 ms 12.124.219.46
                    4 50 ms 50 ms 50 ms lc1.gw3.aus1.texas.net [216.166.60.4]
                    5 * * * Request timed out.
                    6 * * * Request timed out.
                    7 * * * Request timed out.
                    8 * * * Request timed out.
                    9 * * * Request timed out.
                    0 * * * Request timed out.
                    1 * * * Request timed out.
                    2 * * * Request timed out.
                    3 * * * Request timed out.
                    4 * * * Request timed out.
                    5 * * * Request timed out.
                    6 * * * Request timed out.
                    7 * * * Request timed out.
                    8 * * * Request timed out.
                    9 * * * Request timed out.
                    0 * * * Request timed out.

                    ace complete.

                    \> 1 10



                    i see now there is a definite problem, but not my fault..

                    Hope you can fix it soon

                    sZ

                    Comment


                    • #11
                      tracert PLH 700am


                      I timed out three time in the 30 minutes I as in this tourny. I played just to check this problem for us.
                      First tracert/time-out did not get a response

                      Second time out on hand 7178436 and came back on hand 7178470 and received the tracert below. I had another time-out while you visited the table. I had trouble getting to PSO forum so I could not copy the second attempt for tracert. Hope this helps.

                      Tracing route to me2.pokerpages.com [216.166.66.128]
                      over a maximum of 30 hops:

                      1 17 ms 17 ms 13 ms cdm-208-198-1-gnvl.cox-internet.com [208.180.198
                      .1]
                      2 29 ms 36 ms 35 ms 172.16.66.73
                      3 45 ms 53 ms 49 ms 12.125.64.17
                      4 98 ms 72 ms 98 ms gbr6-p50.sl9mo.ip.att.net [12.123.24.126]
                      5 61 ms 46 ms 46 ms tbr2-p013501.sl9mo.ip.att.net [12.122.11.121]
                      6 88 ms 94 ms 86 ms 12.122.10.89
                      7 55 ms 58 ms 61 ms gbr1-p70.dlstx.ip.att.net [12.122.12.78]
                      8 61 ms 61 ms 56 ms gbr4-p00.dlstx.ip.att.net [12.122.5.226]
                      9 61 ms 58 ms 61 ms gbr1-p80.auttx.ip.att.net [12.122.2.110]
                      10 86 ms 68 ms 62 ms gar1-p360.auttx.ip.att.net [12.123.133.21]
                      11 65 ms 83 ms 76 ms 12.124.219.46
                      12 64 ms 61 ms 63 ms lc1.gw3.aus1.texas.net [216.166.60.4]
                      13 * * * Request timed out.
                      14 * * * Request timed out.
                      15 * * * Request timed out.

                      Comment


                      • #12
                        i will not attempt tp play today because it is too frustrating!! however, i will check in the forum occasionally. to see any updates on fixing this..

                        sZ

                        Comment


                        • #13
                          Originally posted by MARK
                          Can any of you confirm that what you are experiencing is a disconnect as opposed to timing out. These are two very different things and I want to be able to investigate the correct problem.

                          A time out simply times you out of the current hand whereas a disconnect means you have to restart the program.

                          Mark
                          Mark,

                          I timed out and disconnected last night. Half the time it was a java error socket lost message and other times I would just freeze from timing out. It happened about 10 times in 2 hours. Bottom line is both disconnects and time outs are happening big time since the move.

                          Jerry

                          Comment


                          • #14
                            Today disconnecting problem!
                            Yesterday both disconnection AND time-out!

                            /AD

                            Comment


                            • #15
                              i had major disconnects and freeze also.

                              i just tried to send this message and got cannot find server!!!!






                              aaaaaaaaaaaaaaaaaarrrrrrrrrrrrrrrrrrgggggggggghhhh h!!!!!!!!!!!

                              Comment

                              Working...
                              X