11 Replies Latest reply: Jan 15, 2013 5:44 PM by Himanshu Singh RSS

    Network failure, work is impossible

    Andrey_ZR Community Member

      Last 3 days we're experiencing many errors on folio uploading and sign in to Folio Builder (Network Failure).

       

      http://data1.floomby.com/files/share/20_12_2012/2gqiWfo730yrFPV4ZI98lA.jpg

       

      DPS Status page snows that everything is ok.

      Don’t you know why?

        • 1. Re: Network failure, work is impossible
          Himanshu Singh Employee Hosts

          Are you working on a corporate network? The issue seems to be localised to your system.

          • 2. Re: Network failure, work is impossible
            Andrey_ZR Community Member

            My administrator told me, that he doesn't changed anything on the network.

            What can i verify by my side?

            • 3. Re: Network failure, work is impossible
              Himanshu Singh Employee Hosts

              I'll send you a list of servers that you can have your IT whitelist. Maybe that will help. Check if there is any other network issue on your end/Try using another system if possible. If it does not help, try creating a new folio.

              • 4. Re: Network failure, work is impossible
                Andrey_ZR Community Member

                Thank you, Himanshu Singh, i forwarded it to the administrator.

                We experiencing this issue with many different folios inside our team, and it's really annoying..

                • 5. Re: Network failure, work is impossible
                  Andrey_ZR Community Member

                  The problem still exists. Here are log files from my ISP. People from there told me that here can be a connection problem between ISP and Adobe servers. Comment it please.

                   

                  17:00:17.755719 IP 194.186.162.1.63992 > 209.34.68.253.443: S 3805199333:3805199333(0) win 65535 <mss 1460,nop,wscale 4,nop,nop,timestamp 172337163 0,sackOK,eol>
                  17:00:17.757347 IP 194.186.162.1.63993 > 209.34.68.253.443: S 2422433095:2422433095(0) win 65535 <mss 1460,nop,wscale 4,nop,nop,timestamp 172337164 0,sackOK,eol>
                  17:00:17.759208 IP 194.186.162.1.63994 > 209.34.68.253.443: S 341433293:341433293(0) win 65535 <mss 1460,nop,wscale 4,nop,nop,timestamp 172337165 0,sackOK,eol>

                   

                  17:00:17.885051 IP 209.34.68.253.443 > 194.186.162.1.63992: S 320483747:320483747(0) ack 3805199334 win 4380 <mss 1460,nop,wscale 0,nop,nop,timestamp 3442919666 172337163,sackOK,eol>

                   

                  17:00:17.886924 IP 209.34.68.253.443 > 194.186.162.1.63993: S 1930018900:1930018900(0) ack 2422433096 win 4380 <mss 1460,nop,wscale 0,nop,nop,timestamp 3442919668 172337164,sackOK,eol>

                   

                  17:00:17.896795 IP 209.34.68.253.443 > 194.186.162.1.63994: S 3702277497:3702277497(0) ack 341433294 win 4380 <mss 1460,nop,wscale 0,nop,nop,timestamp 3442919672 172337165,sackOK,eol>

                   

                  17:00:23.902998 IP 194.186.162.1.63996 > 209.34.68.253.443: S 1694952186:1694952186(0) win 65535 <mss 1460,nop,wscale 4,nop,nop,timestamp 172343284 0,sackOK,eol>
                  17:00:24.561602 IP 194.186.162.1.63996 > 209.34.68.253.443: S 1694952186:1694952186(0) win 65535 <mss 1460,nop,wscale 4,nop,nop,timestamp 172343938 0,sackOK,eol>

                   

                  17:00:24.763746 IP 194.186.162.1.63996 > 209.34.68.253.443: S 1694952186:1694952186(0) win 65535 <mss 1460,nop,wscale 4,nop,nop,timestamp 172344138 0,sackOK,eol>
                  17:00:24.963249 IP 194.186.162.1.63996 > 209.34.68.253.443: S 1694952186:1694952186(0) win 65535 <mss 1460,nop,wscale 4,nop,nop,timestamp 172344338 0,sackOK,eol>
                  17:00:25.165896 IP 194.186.162.1.63996 > 209.34.68.253.443: S 1694952186:1694952186(0) win 65535 <mss 1460,nop,wscale 4,nop,nop,timestamp 172344538 0,sackOK,eol>
                  17:00:25.365834 IP 194.186.162.1.63996 > 209.34.68.253.443: S 1694952186:1694952186(0) win 65535 <mss 1460,nop,wscale 4,nop,nop,timestamp 172344739 0,sackOK,eol>
                  17:00:25.568421 IP 194.186.162.1.63996 > 209.34.68.253.443: S 1694952186:1694952186(0) win 65535 <mss 1460,nop,wscale 4,nop,nop,timestamp 172344938 0,sackOK,eol>

                  17:00:25.869120 IP 194.186.162.1.63996 > 209.34.68.253.443: S 1694952186:1694952186(0) win 65535 <mss 1460,sackOK,eol>

                   


                  • 6. Re: Network failure, work is impossible
                    TK_ITA Community Member

                    Good Morning,

                    we're an Italian company based in Milan, we're working with CS6 InDesign and we have many "Network failure" messages. We're trying to solve the problem with our IT manager, regarding that is possible to know which servers or links we have to put in the "white list" of our firewall?

                    Basically we want to know the web address the DPS is connecting when we press "sign in" in Folio Builder.

                     

                    Thank you so much!

                     

                    Regards,

                    Ronnie

                    • 7. Re: Network failure, work is impossible
                      Himanshu Singh Employee Hosts

                      I'll email you the servers that your IT has to whitelist.

                      • 8. Re: Network failure, work is impossible
                        TK_ITA-2

                        Hi, thank you! I didn't receveid any mail... can you please send me at this e-mail: ghezzi@sorridieditore.it?

                         

                         

                        The nickname is different, because I'm not able to use the old one.. Sorry! :)

                        • 10. Re: Network failure, work is impossible
                          J_99

                          Hi Himanshu,

                           

                          Could you send me that list of servers too please?

                           

                          I don't get the Network failure message when using Windows machines at work, it is only with the Mac's that this problem occurs.

                           

                          Thanks