API tools faq
paste
runelynx

Untitled

runelynx
Jul 4th, 2017
342
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 93.50 KB | None | 0 0
raw download clone embed print report
  1. Ticket: 239-20EA6EFE-030E
  2. General Support Reply to Ticket
  3.  
  4. Patrick F. - NYC Metro Data Center Tech
  5. Today at 11:08 AM Employee Post
  6. Cannot connect to network
  7. Hello,
  8.  
  9. There is no news at this time and we have requested an update.
  10.  
  11. We will contact you as soon as our Network Team reports back.
  12.  
  13. Thank you,
  14. Patrick F. - NYC Metro Data Center Tech
  15. ReliableSite Hosting
  16.  
  17. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  18.  
  19.  
  20. Today at 10:46 AM
  21. RE: Cannot connect to network
  22. Have they responded?
  23.  
  24. Sent from Mail for Windows 10
  25. From: Support - ReliableSite.Net LLC
  26. Sent: Monday, July 3, 2017 8:37 PM
  27. To: [email protected]
  28. Subject: [239-20EA6EFE-030E] Cannot connect to network
  29. Hello,
  30.    I am checking with network on this, I hope to have an explanation. fix as soon as possible 
  31.  
  32. Thank you,
  33. Sean C. - NYC Metro Data Center Tech
  34. ReliableSite Hosting
  35.  
  36. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  37.  
  38. From: Andrew Boeger <[email protected]>
  39. Sent: Mon, 03 Jul 2017 23:31:51 -0400
  40. To: Support - ReliableSite.Net LLC <[email protected]>
  41. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  42.  
  43. All users just force disconnected from the server. I need help urgently!!
  44.  
  45. Sent from Mail for Windows 10
  46. From: Andrew Boeger
  47. Sent: Monday, July 3, 2017 8:13 PM
  48. To: Support - ReliableSite.Net LLC
  49. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  50. Here is another MTR from server to client.
  51.  
  52. Sent from Mail for Windows 10
  53. From: Andrew Boeger
  54. Sent: Monday, July 3, 2017 8:10 PM
  55. To: Support - ReliableSite.Net LLC
  56. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  57. Here is an MTR from server to my client.
  58.  
  59. Sent from Mail for Windows 10
  60. From: Support - ReliableSite.Net LLC
  61. Sent: Monday, July 3, 2017 8:02 PM
  62. To: [email protected]
  63. Subject: [239-20EA6EFE-030E] Cannot connect to network
  64. Hello,
  65.       I have transferred the updated info to the networking department for further review 
  66.  
  67. Thank you,
  68. Sean C. - NYC Metro Data Center Tech
  69. ReliableSite Hosting
  70.  
  71. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  72.  
  73. From: Andrew Boeger <[email protected]>
  74. Sent: Mon, 03 Jul 2017 22:56:35 -0400
  75. To: Support - ReliableSite.Net LLC <[email protected]>
  76. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  77.  
  78. Another sample
  79.  
  80. Sent from Mail for Windows 10
  81. From: Andrew Boeger
  82. Sent: Monday, July 3, 2017 7:48 PM
  83. To: Support - ReliableSite.Net LLC
  84. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  85. No it is still bad, see this MTR. Packets are still not getting to my server successfully.
  86.  
  87. Sent from Mail for Windows 10
  88. From: Support - ReliableSite.Net LLC
  89. Sent: Monday, July 3, 2017 6:17 PM
  90. To: [email protected]
  91. Subject: [239-20EA6EFE-030E] Cannot connect to network
  92. Hello,<p>Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.<p><br />Thank you,<br /> Alex S. - NYC Metro Data Center Manager<br />ReliableSite Hosting<br />  <br /> Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  93.  
  94. From: Andrew Boeger <[email protected]>
  95. Sent: Mon, 03 Jul 2017 22:51:33 -0400
  96. To: Support - ReliableSite.Net LLC <[email protected]>
  97. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  98.  
  99. No it is still bad, see this MTR. Packets are still not getting to my server successfully.
  100.  
  101. Sent from Mail for Windows 10
  102. From: Support - ReliableSite.Net LLC
  103. Sent: Monday, July 3, 2017 6:17 PM
  104. To: [email protected]
  105. Subject: [239-20EA6EFE-030E] Cannot connect to network
  106. Hello,<p>Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.<p><br />Thank you,<br /> Alex S. - NYC Metro Data Center Manager<br />ReliableSite Hosting<br /> <br /> Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  107.  
  108. From: [email protected]
  109. Sent: Mon, 03 Jul 2017 21:16:38 -0400
  110. To: [email protected]
  111. Subject: Cannot connect to network
  112.  
  113. Hello,
  114. Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.
  115. Thank you,
  116. Alex S. - NYC Metro Data Center Manager
  117. ReliableSite Hosting
  118. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  119.  
  120. From: Andrew Boeger <[email protected]>
  121. Sent: Mon, 03 Jul 2017 23:16:44 -0400
  122. To: Support - ReliableSite.Net LLC <[email protected]>
  123. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  124.  
  125. Here is another MTR from server to client.
  126.  
  127. Sent from Mail for Windows 10
  128. From: Andrew Boeger
  129. Sent: Monday, July 3, 2017 8:10 PM
  130. To: Support - ReliableSite.Net LLC
  131. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  132. Here is an MTR from server to my client.
  133.  
  134. Sent from Mail for Windows 10
  135. From: Support - ReliableSite.Net LLC
  136. Sent: Monday, July 3, 2017 8:02 PM
  137. To: [email protected]
  138. Subject: [239-20EA6EFE-030E] Cannot connect to network
  139. Hello,
  140.       I have transferred the updated info to the networking department for further review 
  141.  
  142. Thank you,
  143. Sean C. - NYC Metro Data Center Tech
  144. ReliableSite Hosting
  145.  
  146. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  147.  
  148. From: Andrew Boeger <[email protected]>
  149. Sent: Mon, 03 Jul 2017 22:56:35 -0400
  150. To: Support - ReliableSite.Net LLC <[email protected]>
  151. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  152.  
  153. Another sample
  154.  
  155. Sent from Mail for Windows 10
  156. From: Andrew Boeger
  157. Sent: Monday, July 3, 2017 7:48 PM
  158. To: Support - ReliableSite.Net LLC
  159. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  160. No it is still bad, see this MTR. Packets are still not getting to my server successfully.
  161.  
  162. Sent from Mail for Windows 10
  163. From: Support - ReliableSite.Net LLC
  164. Sent: Monday, July 3, 2017 6:17 PM
  165. To: [email protected]
  166. Subject: [239-20EA6EFE-030E] Cannot connect to network
  167. Hello,<p>Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.<p><br />Thank you,<br /> Alex S. - NYC Metro Data Center Manager<br />ReliableSite Hosting<br />  <br /> Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  168.  
  169. From: Andrew Boeger <[email protected]>
  170. Sent: Mon, 03 Jul 2017 22:51:33 -0400
  171. To: Support - ReliableSite.Net LLC <[email protected]>
  172. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  173.  
  174. No it is still bad, see this MTR. Packets are still not getting to my server successfully.
  175.  
  176. Sent from Mail for Windows 10
  177. From: Support - ReliableSite.Net LLC
  178. Sent: Monday, July 3, 2017 6:17 PM
  179. To: [email protected]
  180. Subject: [239-20EA6EFE-030E] Cannot connect to network
  181. Hello,<p>Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.<p><br />Thank you,<br /> Alex S. - NYC Metro Data Center Manager<br />ReliableSite Hosting<br /> <br /> Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  182.  
  183. From: [email protected]
  184. Sent: Mon, 03 Jul 2017 21:16:38 -0400
  185. To: [email protected]
  186. Subject: Cannot connect to network
  187.  
  188. Hello,
  189. Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.
  190. Thank you,
  191. Alex S. - NYC Metro Data Center Manager
  192. ReliableSite Hosting
  193. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  194.  
  195. From: Andrew Boeger <[email protected]>
  196. Sent: Mon, 03 Jul 2017 23:11:42 -0400
  197. To: Support - ReliableSite.Net LLC <[email protected]>
  198. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  199.  
  200. Here is an MTR from server to my client.
  201.  
  202. Sent from Mail for Windows 10
  203. From: Support - ReliableSite.Net LLC
  204. Sent: Monday, July 3, 2017 8:02 PM
  205. To: [email protected]
  206. Subject: [239-20EA6EFE-030E] Cannot connect to network
  207. Hello,
  208.       I have transferred the updated info to the networking department for further review 
  209.  
  210. Thank you,
  211. Sean C. - NYC Metro Data Center Tech
  212. ReliableSite Hosting
  213.  
  214. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  215.  
  216. From: Andrew Boeger <[email protected]>
  217. Sent: Mon, 03 Jul 2017 22:56:35 -0400
  218. To: Support - ReliableSite.Net LLC <[email protected]>
  219. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  220.  
  221. Another sample
  222.  
  223. Sent from Mail for Windows 10
  224. From: Andrew Boeger
  225. Sent: Monday, July 3, 2017 7:48 PM
  226. To: Support - ReliableSite.Net LLC
  227. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  228. No it is still bad, see this MTR. Packets are still not getting to my server successfully.
  229.  
  230. Sent from Mail for Windows 10
  231. From: Support - ReliableSite.Net LLC
  232. Sent: Monday, July 3, 2017 6:17 PM
  233. To: [email protected]
  234. Subject: [239-20EA6EFE-030E] Cannot connect to network
  235. Hello,<p>Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.<p><br />Thank you,<br /> Alex S. - NYC Metro Data Center Manager<br />ReliableSite Hosting<br />  <br /> Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  236.  
  237. From: Andrew Boeger <[email protected]>
  238. Sent: Mon, 03 Jul 2017 22:51:33 -0400
  239. To: Support - ReliableSite.Net LLC <[email protected]>
  240. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  241.  
  242. No it is still bad, see this MTR. Packets are still not getting to my server successfully.
  243.  
  244. Sent from Mail for Windows 10
  245. From: Support - ReliableSite.Net LLC
  246. Sent: Monday, July 3, 2017 6:17 PM
  247. To: [email protected]
  248. Subject: [239-20EA6EFE-030E] Cannot connect to network
  249. Hello,<p>Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.<p><br />Thank you,<br /> Alex S. - NYC Metro Data Center Manager<br />ReliableSite Hosting<br /> <br /> Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  250.  
  251. From: [email protected]
  252. Sent: Mon, 03 Jul 2017 21:16:38 -0400
  253. To: [email protected]
  254. Subject: Cannot connect to network
  255.  
  256. Hello,
  257. Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.
  258. Thank you,
  259. Alex S. - NYC Metro Data Center Manager
  260. ReliableSite Hosting
  261. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  262. Attachments: B4FCCBB4FB2A4D6A8B68D5C92956F2D9.png (1 KB)
  263.  
  264. Sean C. - NYC Metro Data Center Tech
  265. Yesterday at 11:36 PM Employee Post
  266. Cannot connect to network
  267. Hello,
  268.    I am checking with network on this, I hope to have an explanation. fix as soon as possible 
  269.  
  270. Thank you,
  271. Sean C. - NYC Metro Data Center Tech
  272. ReliableSite Hosting
  273.  
  274. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  275.  
  276.  
  277. Yesterday at 11:31 PM
  278. RE: Cannot connect to network
  279. All users just force disconnected from the server. I need help urgently!!
  280.  
  281. Sent from Mail for Windows 10
  282. From: Andrew Boeger
  283. Sent: Monday, July 3, 2017 8:13 PM
  284. To: Support - ReliableSite.Net LLC
  285. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  286. Here is another MTR from server to client.
  287.  
  288. Sent from Mail for Windows 10
  289. From: Andrew Boeger
  290. Sent: Monday, July 3, 2017 8:10 PM
  291. To: Support - ReliableSite.Net LLC
  292. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  293. Here is an MTR from server to my client.
  294.  
  295. Sent from Mail for Windows 10
  296. From: Support - ReliableSite.Net LLC
  297. Sent: Monday, July 3, 2017 8:02 PM
  298. To: [email protected]
  299. Subject: [239-20EA6EFE-030E] Cannot connect to network
  300. Hello,
  301.       I have transferred the updated info to the networking department for further review 
  302.  
  303. Thank you,
  304. Sean C. - NYC Metro Data Center Tech
  305. ReliableSite Hosting
  306.  
  307. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  308.  
  309. From: Andrew Boeger <[email protected]>
  310. Sent: Mon, 03 Jul 2017 22:56:35 -0400
  311. To: Support - ReliableSite.Net LLC <[email protected]>
  312. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  313.  
  314. Another sample
  315.  
  316. Sent from Mail for Windows 10
  317. From: Andrew Boeger
  318. Sent: Monday, July 3, 2017 7:48 PM
  319. To: Support - ReliableSite.Net LLC
  320. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  321. No it is still bad, see this MTR. Packets are still not getting to my server successfully.
  322.  
  323. Sent from Mail for Windows 10
  324. From: Support - ReliableSite.Net LLC
  325. Sent: Monday, July 3, 2017 6:17 PM
  326. To: [email protected]
  327. Subject: [239-20EA6EFE-030E] Cannot connect to network
  328. Hello,<p>Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.<p><br />Thank you,<br /> Alex S. - NYC Metro Data Center Manager<br />ReliableSite Hosting<br />  <br /> Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  329.  
  330. From: Andrew Boeger <[email protected]>
  331. Sent: Mon, 03 Jul 2017 22:51:33 -0400
  332. To: Support - ReliableSite.Net LLC <[email protected]>
  333. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  334.  
  335. No it is still bad, see this MTR. Packets are still not getting to my server successfully.
  336.  
  337. Sent from Mail for Windows 10
  338. From: Support - ReliableSite.Net LLC
  339. Sent: Monday, July 3, 2017 6:17 PM
  340. To: [email protected]
  341. Subject: [239-20EA6EFE-030E] Cannot connect to network
  342. Hello,<p>Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.<p><br />Thank you,<br /> Alex S. - NYC Metro Data Center Manager<br />ReliableSite Hosting<br /> <br /> Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  343.  
  344. From: [email protected]
  345. Sent: Mon, 03 Jul 2017 21:16:38 -0400
  346. To: [email protected]
  347. Subject: Cannot connect to network
  348.  
  349. Hello,
  350. Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.
  351. Thank you,
  352. Alex S. - NYC Metro Data Center Manager
  353. ReliableSite Hosting
  354. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  355. Attachments: 1556DAD03327440B95ABCE1C2A6174A3.png (13.935546875 KB)
  356.  
  357.  
  358. Yesterday at 11:16 PM
  359. RE: Cannot connect to network
  360. Here is another MTR from server to client.
  361.  
  362. Sent from Mail for Windows 10
  363. From: Andrew Boeger
  364. Sent: Monday, July 3, 2017 8:10 PM
  365. To: Support - ReliableSite.Net LLC
  366. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  367. Here is an MTR from server to my client.
  368.  
  369. Sent from Mail for Windows 10
  370. From: Support - ReliableSite.Net LLC
  371. Sent: Monday, July 3, 2017 8:02 PM
  372. To: [email protected]
  373. Subject: [239-20EA6EFE-030E] Cannot connect to network
  374. Hello,
  375.       I have transferred the updated info to the networking department for further review 
  376.  
  377. Thank you,
  378. Sean C. - NYC Metro Data Center Tech
  379. ReliableSite Hosting
  380.  
  381. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  382.  
  383. From: Andrew Boeger <[email protected]>
  384. Sent: Mon, 03 Jul 2017 22:56:35 -0400
  385. To: Support - ReliableSite.Net LLC <[email protected]>
  386. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  387.  
  388. Another sample
  389.  
  390. Sent from Mail for Windows 10
  391. From: Andrew Boeger
  392. Sent: Monday, July 3, 2017 7:48 PM
  393. To: Support - ReliableSite.Net LLC
  394. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  395. No it is still bad, see this MTR. Packets are still not getting to my server successfully.
  396.  
  397. Sent from Mail for Windows 10
  398. From: Support - ReliableSite.Net LLC
  399. Sent: Monday, July 3, 2017 6:17 PM
  400. To: [email protected]
  401. Subject: [239-20EA6EFE-030E] Cannot connect to network
  402. Hello,<p>Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.<p><br />Thank you,<br /> Alex S. - NYC Metro Data Center Manager<br />ReliableSite Hosting<br />  <br /> Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  403.  
  404. From: Andrew Boeger <[email protected]>
  405. Sent: Mon, 03 Jul 2017 22:51:33 -0400
  406. To: Support - ReliableSite.Net LLC <[email protected]>
  407. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  408.  
  409. No it is still bad, see this MTR. Packets are still not getting to my server successfully.
  410.  
  411. Sent from Mail for Windows 10
  412. From: Support - ReliableSite.Net LLC
  413. Sent: Monday, July 3, 2017 6:17 PM
  414. To: [email protected]
  415. Subject: [239-20EA6EFE-030E] Cannot connect to network
  416. Hello,<p>Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.<p><br />Thank you,<br /> Alex S. - NYC Metro Data Center Manager<br />ReliableSite Hosting<br /> <br /> Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  417.  
  418. From: [email protected]
  419. Sent: Mon, 03 Jul 2017 21:16:38 -0400
  420. To: [email protected]
  421. Subject: Cannot connect to network
  422.  
  423. Hello,
  424. Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.
  425. Thank you,
  426. Alex S. - NYC Metro Data Center Manager
  427. ReliableSite Hosting
  428. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  429. Attachments: 17771AA88F174848B70F34DA64D1D876.png (19.9609375 KB)
  430.  
  431.  
  432. Yesterday at 11:11 PM
  433. RE: Cannot connect to network
  434. Here is an MTR from server to my client.
  435.  
  436. Sent from Mail for Windows 10
  437. From: Support - ReliableSite.Net LLC
  438. Sent: Monday, July 3, 2017 8:02 PM
  439. To: [email protected]
  440. Subject: [239-20EA6EFE-030E] Cannot connect to network
  441. Hello,
  442.       I have transferred the updated info to the networking department for further review 
  443.  
  444. Thank you,
  445. Sean C. - NYC Metro Data Center Tech
  446. ReliableSite Hosting
  447.  
  448. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  449.  
  450. From: Andrew Boeger <[email protected]>
  451. Sent: Mon, 03 Jul 2017 22:56:35 -0400
  452. To: Support - ReliableSite.Net LLC <[email protected]>
  453. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  454.  
  455. Another sample
  456.  
  457. Sent from Mail for Windows 10
  458. From: Andrew Boeger
  459. Sent: Monday, July 3, 2017 7:48 PM
  460. To: Support - ReliableSite.Net LLC
  461. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  462. No it is still bad, see this MTR. Packets are still not getting to my server successfully.
  463.  
  464. Sent from Mail for Windows 10
  465. From: Support - ReliableSite.Net LLC
  466. Sent: Monday, July 3, 2017 6:17 PM
  467. To: [email protected]
  468. Subject: [239-20EA6EFE-030E] Cannot connect to network
  469. Hello,<p>Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.<p><br />Thank you,<br /> Alex S. - NYC Metro Data Center Manager<br />ReliableSite Hosting<br />  <br /> Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  470.  
  471. From: Andrew Boeger <[email protected]>
  472. Sent: Mon, 03 Jul 2017 22:51:33 -0400
  473. To: Support - ReliableSite.Net LLC <[email protected]>
  474. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  475.  
  476. No it is still bad, see this MTR. Packets are still not getting to my server successfully.
  477.  
  478. Sent from Mail for Windows 10
  479. From: Support - ReliableSite.Net LLC
  480. Sent: Monday, July 3, 2017 6:17 PM
  481. To: [email protected]
  482. Subject: [239-20EA6EFE-030E] Cannot connect to network
  483. Hello,<p>Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.<p><br />Thank you,<br /> Alex S. - NYC Metro Data Center Manager<br />ReliableSite Hosting<br /> <br /> Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  484.  
  485. From: [email protected]
  486. Sent: Mon, 03 Jul 2017 21:16:38 -0400
  487. To: [email protected]
  488. Subject: Cannot connect to network
  489.  
  490. Hello,
  491. Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.
  492. Thank you,
  493. Alex S. - NYC Metro Data Center Manager
  494. ReliableSite Hosting
  495. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  496. Attachments: 0D028C70013642CFA58DAD8742252956.png (22.458984375 KB), 538661FE87924D748A81B0CA922DEEC5.png (1 KB)
  497.  
  498.  
  499. Yesterday at 11:06 PM
  500. RE: Cannot connect to network
  501. Packet loss is so bad that I cannot even hold an SSH session anymore.
  502.  
  503. Sent from Mail for Windows 10
  504. From: Andrew Boeger
  505. Sent: Monday, July 3, 2017 7:53 PM
  506. To: Support - ReliableSite.Net LLC
  507. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  508. Another sample
  509.  
  510. Sent from Mail for Windows 10
  511. From: Andrew Boeger
  512. Sent: Monday, July 3, 2017 7:48 PM
  513. To: Support - ReliableSite.Net LLC
  514. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  515. No it is still bad, see this MTR. Packets are still not getting to my server successfully.
  516.  
  517. Sent from Mail for Windows 10
  518. From: Support - ReliableSite.Net LLC
  519. Sent: Monday, July 3, 2017 6:17 PM
  520. To: [email protected]
  521. Subject: [239-20EA6EFE-030E] Cannot connect to network
  522. Hello,<p>Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.<p><br />Thank you,<br /> Alex S. - NYC Metro Data Center Manager<br />ReliableSite Hosting<br />  <br /> Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  523. Attachments: E37EBEC702644A929784CA74BD2BAE0D.png (11.833984375 KB)
  524.  
  525. Sean C. - NYC Metro Data Center Tech
  526. Yesterday at 11:02 PM Employee Post
  527. Cannot connect to network
  528. Hello,
  529.       I have transferred the updated info to the networking department for further review 
  530.  
  531. Thank you,
  532. Sean C. - NYC Metro Data Center Tech
  533. ReliableSite Hosting
  534.  
  535. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  536.  
  537.  
  538. Yesterday at 10:56 PM
  539. RE: Cannot connect to network
  540. Another sample
  541.  
  542. Sent from Mail for Windows 10
  543. From: Andrew Boeger
  544. Sent: Monday, July 3, 2017 7:48 PM
  545. To: Support - ReliableSite.Net LLC
  546. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  547. No it is still bad, see this MTR. Packets are still not getting to my server successfully.
  548.  
  549. Sent from Mail for Windows 10
  550. From: Support - ReliableSite.Net LLC
  551. Sent: Monday, July 3, 2017 6:17 PM
  552. To: [email protected]
  553. Subject: [239-20EA6EFE-030E] Cannot connect to network
  554. Hello,<p>Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.<p><br />Thank you,<br /> Alex S. - NYC Metro Data Center Manager<br />ReliableSite Hosting<br />  <br /> Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  555. Attachments: E37EBEC702644A929784CA74BD2BAE0D.png (11.833984375 KB), 1FD12A07CAB8446BAADC4FB2733773E9.png (10.8134765625 KB)
  556.  
  557.  
  558. Yesterday at 10:51 PM
  559. RE: Cannot connect to network
  560. No it is still bad, see this MTR. Packets are still not getting to my server successfully.
  561.  
  562. Sent from Mail for Windows 10
  563. From: Support - ReliableSite.Net LLC
  564. Sent: Monday, July 3, 2017 6:17 PM
  565. To: [email protected]
  566. Subject: [239-20EA6EFE-030E] Cannot connect to network
  567. Hello,<p>Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.<p><br />Thank you,<br /> Alex S. - NYC Metro Data Center Manager<br />ReliableSite Hosting<br /> <br /> Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  568. Attachments: 1FD12A07CAB8446BAADC4FB2733773E9.png (10.8134765625 KB)
  569.  
  570. Alex S. - NYC Metro Data Center Manager
  571. Yesterday at 9:16 PM Employee Post
  572. Cannot connect to network
  573. Hello,
  574. Networking has made several configuration changes. Kindly see if the changes have resolved the issue on your end.
  575.  
  576. Thank you,
  577. Alex S. - NYC Metro Data Center Manager
  578. ReliableSite Hosting
  579.  
  580. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  581.  
  582.  
  583. Yesterday at 8:54 PM
  584. RE: Cannot connect to network
  585. Thank you.
  586. Sent from Mail for Windows 10
  587. From: Support - ReliableSite.Net LLC
  588. Sent: Monday, July 3, 2017 5:23 PM
  589. To: [email protected]
  590. Subject: [239-20EA6EFE-030E] Cannot connect to network
  591. Hello,
  592.  
  593. We have prompted Networking to escalate this issue.
  594.  
  595. Thank you,
  596. Alex S. - NYC Metro Data Center Manager
  597. ReliableSite Hosting
  598.  
  599. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  600.  
  601. From: Andrew Boeger <[email protected]>
  602. Sent: Mon, 03 Jul 2017 20:09:11 -0400
  603. To: Support - ReliableSite.Net LLC <[email protected]>
  604. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  605.  
  606. My server has been unplayable for some people for 3 days. The bandwidth charts on dedicated.reliablesite.net reflect the outage when it happens so it should be possible for your networking team to see this. It’s a chart in your system- can they not see in/out transfer goes from normal level to zero for several minutes?
  607. You are costing me business to my server!
  608. Sent from Mail for Windows 10
  609. From: Andrew Boeger
  610. Sent: Monday, July 3, 2017 3:11 PM
  611. To: Support - ReliableSite.Net LLC
  612. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  613. Hmm… I cannot initiate it from server to my local PC when I can’t connect to the server.
  614. Sent from Mail for Windows 10
  615. From: Support - ReliableSite.Net LLC
  616. Sent: Monday, July 3, 2017 3:08 PM
  617. To: [email protected]
  618. Subject: [239-20EA6EFE-030E] Cannot connect to network
  619. Hello,
  620.  
  621. Networking is requesting a MTR in both directions if possible.
  622.  
  623. Thank you,
  624. Alex S. - NYC Metro Data Center Manager
  625. ReliableSite Hosting
  626.  
  627. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  628.  
  629. From: General Support
  630. Sent: Mon, 03 Jul 2017 16:55:39 -0400
  631. To: [email protected]
  632. Subject: [239-20EA6EFE-030E] Cannot connect to network
  633.  
  634. Hello,
  635.  
  636. Networking is evaluating this issue. We will update you as soon as we have a response from them.
  637.  
  638. Thank you,
  639. Alex S. - NYC Metro Data Center Manager
  640. ReliableSite Hosting
  641.  
  642. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  643.  
  644. From: General Support
  645. Sent: Mon, 03 Jul 2017 16:22:53 -0400
  646. To: [email protected]
  647. Subject: [239-20EA6EFE-030E] Cannot connect to network
  648.  
  649. Hello,
  650.  
  651. We will check on this and will update you shortly. 
  652.  
  653. Thank you,
  654. Nithin T. - Systems Administrator
  655. ReliableSite Hosting
  656.  
  657. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  658.  
  659. From: Andrew Boeger <[email protected]>
  660. Sent: Mon, 03 Jul 2017 16:10:52 -0400
  661. To: Support - ReliableSite.Net LLC <[email protected]>
  662. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  663.  
  664. Hello,
  665. Network has gone unavailable again. See below MTR from 207.214.246.130 showing severe packet loss within choopa.net network.
  666.  
  667. Sent from Mail for Windows 10
  668. From: Support - ReliableSite.Net LLC
  669. Sent: Monday, July 3, 2017 9:58 AM
  670. To: [email protected]
  671. Subject: [239-20EA6EFE-030E] Cannot connect to network
  672. Hello,
  673.  
  674. The issue was due to DDoS attack not filtering it properly.
  675.  
  676. Thank you,
  677. Shahalam H. - NYC Metro Center Tech
  678. ReliableSite Hosting
  679.  
  680. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  681.  
  682. From: Andrew Boeger <[email protected]>
  683. Sent: Mon, 03 Jul 2017 12:42:49 -0400
  684. To: Support - ReliableSite.Net LLC <[email protected]>
  685. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  686.  
  687. Hi Shahalam,
  688. Can you please share what you mean by resolved? What was done? Did you change something on my server?
  689. Thanks,
  690. Andrew
  691. Sent from Mail for Windows 10
  692. From: Support - ReliableSite.Net LLC
  693. Sent: Monday, July 3, 2017 9:35 AM
  694. To: [email protected]
  695. Subject: [239-20EA6EFE-030E] Cannot connect to network
  696. Hello,
  697.  
  698. This has been resolved.  Kindly check and let us know if you need further assistance. 
  699.  
  700. Thank you,
  701. Shahalam H. - NYC Metro Center Tech
  702. ReliableSite Hosting
  703.  
  704. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  705.  
  706. From: General Support
  707. Sent: Mon, 03 Jul 2017 11:03:32 -0400
  708. To: [email protected]
  709. Subject: [239-20EA6EFE-030E] Cannot connect to network
  710.  
  711. Hello,
  712.  
  713. We have received your request.
  714.  
  715. We are looking into this and will get back to you shortly. 
  716. ?
  717.  
  718. Thank you,
  719. Shahalam H. - NYC Metro Center Tech
  720. ReliableSite Hosting
  721.  
  722. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  723.  
  724. From: Andrew Boeger <[email protected]>
  725. Sent: Mon, 03 Jul 2017 11:01:17 -0400
  726. To: "Support - ReliableSite.Net LLC" <[email protected]>
  727. Subject: Re: [239-20EA6EFE-030E] Cannot connect to network
  728.  
  729. Network failure happened again this morning and many times since Jun 28 so do not blame ddos.
  730. Sent from my iPhone
  731.  
  732. From: Andrew Boeger <[email protected]>
  733. Sent: Mon, 03 Jul 2017 11:01:17 -0400
  734. To: "Support - ReliableSite.Net LLC" <[email protected]>
  735. Subject: Re: [239-20EA6EFE-030E] Cannot connect to network
  736.  
  737. You saw the MTR in the ticket showing total packet loss on choopa.net systems? My server settings are not causing this.
  738. Sent from my iPhone
  739.  
  740. From: General Support
  741. Sent: Mon, 03 Jul 2017 12:34:50 -0400
  742. To: [email protected]
  743. Subject: [239-20EA6EFE-030E] Cannot connect to network
  744.  
  745. Hello,
  746.  
  747. This has been resolved.  Kindly check and let us know if you need further assistance. 
  748.  
  749. Thank you,
  750. Shahalam H. - NYC Metro Center Tech
  751. ReliableSite Hosting
  752.  
  753. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  754.  
  755. From: General Support
  756. Sent: Mon, 03 Jul 2017 11:03:32 -0400
  757. To: [email protected]
  758. Subject: [239-20EA6EFE-030E] Cannot connect to network
  759.  
  760. Hello,
  761.  
  762. We have received your request.
  763.  
  764. We are looking into this and will get back to you shortly. 
  765. ?
  766.  
  767. Thank you,
  768. Shahalam H. - NYC Metro Center Tech
  769. ReliableSite Hosting
  770.  
  771. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  772.  
  773. From: Andrew Boeger <[email protected]>
  774. Sent: Mon, 03 Jul 2017 18:12:33 -0400
  775. To: Support - ReliableSite.Net LLC <[email protected]>
  776. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  777.  
  778. Hmm… I cannot initiate it from server to my local PC when I can’t connect to the server.
  779. Sent from Mail for Windows 10
  780. From: Support - ReliableSite.Net LLC
  781. Sent: Monday, July 3, 2017 3:08 PM
  782. To: [email protected]
  783. Subject: [239-20EA6EFE-030E] Cannot connect to network
  784. Hello,
  785.  
  786. Networking is requesting a MTR in both directions if possible.
  787.  
  788. Thank you,
  789. Alex S. - NYC Metro Data Center Manager
  790. ReliableSite Hosting
  791.  
  792. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  793.  
  794. From: General Support
  795. Sent: Mon, 03 Jul 2017 16:55:39 -0400
  796. To: [email protected]
  797. Subject: [239-20EA6EFE-030E] Cannot connect to network
  798.  
  799. Hello,
  800.  
  801. Networking is evaluating this issue. We will update you as soon as we have a response from them.
  802.  
  803. Thank you,
  804. Alex S. - NYC Metro Data Center Manager
  805. ReliableSite Hosting
  806.  
  807. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  808.  
  809. From: General Support
  810. Sent: Mon, 03 Jul 2017 16:22:53 -0400
  811. To: [email protected]
  812. Subject: [239-20EA6EFE-030E] Cannot connect to network
  813.  
  814. Hello,
  815.  
  816. We will check on this and will update you shortly. 
  817.  
  818. Thank you,
  819. Nithin T. - Systems Administrator
  820. ReliableSite Hosting
  821.  
  822. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  823.  
  824. From: Andrew Boeger <[email protected]>
  825. Sent: Mon, 03 Jul 2017 16:10:52 -0400
  826. To: Support - ReliableSite.Net LLC <[email protected]>
  827. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  828.  
  829. Hello,
  830. Network has gone unavailable again. See below MTR from 207.214.246.130 showing severe packet loss within choopa.net network.
  831.  
  832. Sent from Mail for Windows 10
  833. From: Support - ReliableSite.Net LLC
  834. Sent: Monday, July 3, 2017 9:58 AM
  835. To: [email protected]
  836. Subject: [239-20EA6EFE-030E] Cannot connect to network
  837. Hello,
  838.  
  839. The issue was due to DDoS attack not filtering it properly.
  840.  
  841. Thank you,
  842. Shahalam H. - NYC Metro Center Tech
  843. ReliableSite Hosting
  844.  
  845. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  846.  
  847. From: Andrew Boeger <[email protected]>
  848. Sent: Mon, 03 Jul 2017 12:42:49 -0400
  849. To: Support - ReliableSite.Net LLC <[email protected]>
  850. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  851.  
  852. Hi Shahalam,
  853. Can you please share what you mean by resolved? What was done? Did you change something on my server?
  854. Thanks,
  855. Andrew
  856. Sent from Mail for Windows 10
  857. From: Support - ReliableSite.Net LLC
  858. Sent: Monday, July 3, 2017 9:35 AM
  859. To: [email protected]
  860. Subject: [239-20EA6EFE-030E] Cannot connect to network
  861. Hello,
  862.  
  863. This has been resolved.  Kindly check and let us know if you need further assistance. 
  864.  
  865. Thank you,
  866. Shahalam H. - NYC Metro Center Tech
  867. ReliableSite Hosting
  868.  
  869. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  870.  
  871. From: General Support
  872. Sent: Mon, 03 Jul 2017 11:03:32 -0400
  873. To: [email protected]
  874. Subject: [239-20EA6EFE-030E] Cannot connect to network
  875.  
  876. Hello,
  877.  
  878. We have received your request.
  879.  
  880. We are looking into this and will get back to you shortly. 
  881. ?
  882.  
  883. Thank you,
  884. Shahalam H. - NYC Metro Center Tech
  885. ReliableSite Hosting
  886.  
  887. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  888.  
  889. From: Andrew Boeger <[email protected]>
  890. Sent: Mon, 03 Jul 2017 11:01:17 -0400
  891. To: "Support - ReliableSite.Net LLC" <[email protected]>
  892. Subject: Re: [239-20EA6EFE-030E] Cannot connect to network
  893.  
  894. Network failure happened again this morning and many times since Jun 28 so do not blame ddos.
  895. Sent from my iPhone
  896.  
  897. From: Andrew Boeger <[email protected]>
  898. Sent: Mon, 03 Jul 2017 11:01:17 -0400
  899. To: "Support - ReliableSite.Net LLC" <[email protected]>
  900. Subject: Re: [239-20EA6EFE-030E] Cannot connect to network
  901.  
  902. You saw the MTR in the ticket showing total packet loss on choopa.net systems? My server settings are not causing this.
  903. Sent from my iPhone
  904.  
  905. From: General Support
  906. Sent: Mon, 03 Jul 2017 12:34:50 -0400
  907. To: [email protected]
  908. Subject: [239-20EA6EFE-030E] Cannot connect to network
  909.  
  910. Hello,
  911.  
  912. This has been resolved.  Kindly check and let us know if you need further assistance. 
  913.  
  914. Thank you,
  915. Shahalam H. - NYC Metro Center Tech
  916. ReliableSite Hosting
  917.  
  918. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  919.  
  920. From: General Support
  921. Sent: Mon, 03 Jul 2017 11:03:32 -0400
  922. To: [email protected]
  923. Subject: [239-20EA6EFE-030E] Cannot connect to network
  924.  
  925. Hello,
  926.  
  927. We have received your request.
  928.  
  929. We are looking into this and will get back to you shortly. 
  930. ?
  931.  
  932. Thank you,
  933. Shahalam H. - NYC Metro Center Tech
  934. ReliableSite Hosting
  935.  
  936. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  937.  
  938. From: General Support
  939. Sent: Mon, 03 Jul 2017 18:07:32 -0400
  940. To: [email protected]
  941. Subject: [239-20EA6EFE-030E] Cannot connect to network
  942.  
  943. Hello,
  944.  
  945. Networking is requesting a MTR in both directions if possible.
  946.  
  947. Thank you,
  948. Alex S. - NYC Metro Data Center Manager
  949. ReliableSite Hosting
  950.  
  951. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  952. Attachments: B56B760C8E14464DBF53447B50694DB9.png (1 KB)
  953.  
  954. Alex S. - NYC Metro Data Center Manager
  955. Yesterday at 8:22 PM Employee Post
  956. Cannot connect to network
  957. Hello,
  958.  
  959. We have prompted Networking to escalate this issue.
  960.  
  961. Thank you,
  962. Alex S. - NYC Metro Data Center Manager
  963. ReliableSite Hosting
  964.  
  965. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  966.  
  967.  
  968. Yesterday at 8:09 PM
  969. RE: Cannot connect to network
  970. My server has been unplayable for some people for 3 days. The bandwidth charts on dedicated.reliablesite.net reflect the outage when it happens so it should be possible for your networking team to see this. It’s a chart in your system- can they not see in/out transfer goes from normal level to zero for several minutes?
  971. You are costing me business to my server!
  972. Sent from Mail for Windows 10
  973. From: Andrew Boeger
  974. Sent: Monday, July 3, 2017 3:11 PM
  975. To: Support - ReliableSite.Net LLC
  976. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  977. Hmm… I cannot initiate it from server to my local PC when I can’t connect to the server.
  978. Sent from Mail for Windows 10
  979. From: Support - ReliableSite.Net LLC
  980. Sent: Monday, July 3, 2017 3:08 PM
  981. To: [email protected]
  982. Subject: [239-20EA6EFE-030E] Cannot connect to network
  983. Hello,
  984.  
  985. Networking is requesting a MTR in both directions if possible.
  986.  
  987. Thank you,
  988. Alex S. - NYC Metro Data Center Manager
  989. ReliableSite Hosting
  990.  
  991. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  992.  
  993. From: General Support
  994. Sent: Mon, 03 Jul 2017 16:55:39 -0400
  995. To: [email protected]
  996. Subject: [239-20EA6EFE-030E] Cannot connect to network
  997.  
  998. Hello,
  999.  
  1000. Networking is evaluating this issue. We will update you as soon as we have a response from them.
  1001.  
  1002. Thank you,
  1003. Alex S. - NYC Metro Data Center Manager
  1004. ReliableSite Hosting
  1005.  
  1006. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1007.  
  1008. From: General Support
  1009. Sent: Mon, 03 Jul 2017 16:22:53 -0400
  1010. To: [email protected]
  1011. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1012.  
  1013. Hello,
  1014.  
  1015. We will check on this and will update you shortly. 
  1016.  
  1017. Thank you,
  1018. Nithin T. - Systems Administrator
  1019. ReliableSite Hosting
  1020.  
  1021. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1022.  
  1023. From: Andrew Boeger <[email protected]>
  1024. Sent: Mon, 03 Jul 2017 16:10:52 -0400
  1025. To: Support - ReliableSite.Net LLC <[email protected]>
  1026. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  1027.  
  1028. Hello,
  1029. Network has gone unavailable again. See below MTR from 207.214.246.130 showing severe packet loss within choopa.net network.
  1030.  
  1031. Sent from Mail for Windows 10
  1032. From: Support - ReliableSite.Net LLC
  1033. Sent: Monday, July 3, 2017 9:58 AM
  1034. To: [email protected]
  1035. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1036. Hello,
  1037.  
  1038. The issue was due to DDoS attack not filtering it properly.
  1039.  
  1040. Thank you,
  1041. Shahalam H. - NYC Metro Center Tech
  1042. ReliableSite Hosting
  1043.  
  1044. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1045.  
  1046. From: Andrew Boeger <[email protected]>
  1047. Sent: Mon, 03 Jul 2017 12:42:49 -0400
  1048. To: Support - ReliableSite.Net LLC <[email protected]>
  1049. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  1050.  
  1051. Hi Shahalam,
  1052. Can you please share what you mean by resolved? What was done? Did you change something on my server?
  1053. Thanks,
  1054. Andrew
  1055. Sent from Mail for Windows 10
  1056. From: Support - ReliableSite.Net LLC
  1057. Sent: Monday, July 3, 2017 9:35 AM
  1058. To: [email protected]
  1059. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1060. Hello,
  1061.  
  1062. This has been resolved.  Kindly check and let us know if you need further assistance. 
  1063.  
  1064. Thank you,
  1065. Shahalam H. - NYC Metro Center Tech
  1066. ReliableSite Hosting
  1067.  
  1068. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1069.  
  1070. From: General Support
  1071. Sent: Mon, 03 Jul 2017 11:03:32 -0400
  1072. To: [email protected]
  1073. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1074.  
  1075. Hello,
  1076.  
  1077. We have received your request.
  1078.  
  1079. We are looking into this and will get back to you shortly. 
  1080. ?
  1081.  
  1082. Thank you,
  1083. Shahalam H. - NYC Metro Center Tech
  1084. ReliableSite Hosting
  1085.  
  1086. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1087.  
  1088. From: Andrew Boeger <[email protected]>
  1089. Sent: Mon, 03 Jul 2017 11:01:17 -0400
  1090. To: "Support - ReliableSite.Net LLC" <[email protected]>
  1091. Subject: Re: [239-20EA6EFE-030E] Cannot connect to network
  1092.  
  1093. Network failure happened again this morning and many times since Jun 28 so do not blame ddos.
  1094. Sent from my iPhone
  1095.  
  1096. From: Andrew Boeger <[email protected]>
  1097. Sent: Mon, 03 Jul 2017 11:01:17 -0400
  1098. To: "Support - ReliableSite.Net LLC" <[email protected]>
  1099. Subject: Re: [239-20EA6EFE-030E] Cannot connect to network
  1100.  
  1101. You saw the MTR in the ticket showing total packet loss on choopa.net systems? My server settings are not causing this.
  1102. Sent from my iPhone
  1103.  
  1104. From: General Support
  1105. Sent: Mon, 03 Jul 2017 12:34:50 -0400
  1106. To: [email protected]
  1107. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1108.  
  1109. Hello,
  1110.  
  1111. This has been resolved.  Kindly check and let us know if you need further assistance. 
  1112.  
  1113. Thank you,
  1114. Shahalam H. - NYC Metro Center Tech
  1115. ReliableSite Hosting
  1116.  
  1117. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1118.  
  1119. From: General Support
  1120. Sent: Mon, 03 Jul 2017 11:03:32 -0400
  1121. To: [email protected]
  1122. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1123.  
  1124. Hello,
  1125.  
  1126. We have received your request.
  1127.  
  1128. We are looking into this and will get back to you shortly. 
  1129. ?
  1130.  
  1131. Thank you,
  1132. Shahalam H. - NYC Metro Center Tech
  1133. ReliableSite Hosting
  1134.  
  1135. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1136. Attachments: A4FCD392AABB470B8969FE737ABA2E53.png (1 KB)
  1137.  
  1138.  
  1139. Yesterday at 6:12 PM
  1140. RE: Cannot connect to network
  1141. Hmm… I cannot initiate it from server to my local PC when I can’t connect to the server.
  1142. Sent from Mail for Windows 10
  1143. From: Support - ReliableSite.Net LLC
  1144. Sent: Monday, July 3, 2017 3:08 PM
  1145. To: [email protected]
  1146. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1147. Hello,
  1148.  
  1149. Networking is requesting a MTR in both directions if possible.
  1150.  
  1151. Thank you,
  1152. Alex S. - NYC Metro Data Center Manager
  1153. ReliableSite Hosting
  1154.  
  1155. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1156.  
  1157. From: General Support
  1158. Sent: Mon, 03 Jul 2017 16:55:39 -0400
  1159. To: [email protected]
  1160. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1161.  
  1162. Hello,
  1163.  
  1164. Networking is evaluating this issue. We will update you as soon as we have a response from them.
  1165.  
  1166. Thank you,
  1167. Alex S. - NYC Metro Data Center Manager
  1168. ReliableSite Hosting
  1169.  
  1170. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1171.  
  1172. From: General Support
  1173. Sent: Mon, 03 Jul 2017 16:22:53 -0400
  1174. To: [email protected]
  1175. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1176.  
  1177. Hello,
  1178.  
  1179. We will check on this and will update you shortly. 
  1180.  
  1181. Thank you,
  1182. Nithin T. - Systems Administrator
  1183. ReliableSite Hosting
  1184.  
  1185. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1186.  
  1187. From: Andrew Boeger <[email protected]>
  1188. Sent: Mon, 03 Jul 2017 16:10:52 -0400
  1189. To: Support - ReliableSite.Net LLC <[email protected]>
  1190. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  1191.  
  1192. Hello,
  1193. Network has gone unavailable again. See below MTR from 207.214.246.130 showing severe packet loss within choopa.net network.
  1194.  
  1195. Sent from Mail for Windows 10
  1196. From: Support - ReliableSite.Net LLC
  1197. Sent: Monday, July 3, 2017 9:58 AM
  1198. To: [email protected]
  1199. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1200. Hello,
  1201.  
  1202. The issue was due to DDoS attack not filtering it properly.
  1203.  
  1204. Thank you,
  1205. Shahalam H. - NYC Metro Center Tech
  1206. ReliableSite Hosting
  1207.  
  1208. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1209.  
  1210. From: Andrew Boeger <[email protected]>
  1211. Sent: Mon, 03 Jul 2017 12:42:49 -0400
  1212. To: Support - ReliableSite.Net LLC <[email protected]>
  1213. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  1214.  
  1215. Hi Shahalam,
  1216. Can you please share what you mean by resolved? What was done? Did you change something on my server?
  1217. Thanks,
  1218. Andrew
  1219. Sent from Mail for Windows 10
  1220. From: Support - ReliableSite.Net LLC
  1221. Sent: Monday, July 3, 2017 9:35 AM
  1222. To: [email protected]
  1223. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1224. Hello,
  1225.  
  1226. This has been resolved.  Kindly check and let us know if you need further assistance. 
  1227.  
  1228. Thank you,
  1229. Shahalam H. - NYC Metro Center Tech
  1230. ReliableSite Hosting
  1231.  
  1232. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1233.  
  1234. From: General Support
  1235. Sent: Mon, 03 Jul 2017 11:03:32 -0400
  1236. To: [email protected]
  1237. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1238.  
  1239. Hello,
  1240.  
  1241. We have received your request.
  1242.  
  1243. We are looking into this and will get back to you shortly. 
  1244. ?
  1245.  
  1246. Thank you,
  1247. Shahalam H. - NYC Metro Center Tech
  1248. ReliableSite Hosting
  1249.  
  1250. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1251.  
  1252. From: Andrew Boeger <[email protected]>
  1253. Sent: Mon, 03 Jul 2017 11:01:17 -0400
  1254. To: "Support - ReliableSite.Net LLC" <[email protected]>
  1255. Subject: Re: [239-20EA6EFE-030E] Cannot connect to network
  1256.  
  1257. Network failure happened again this morning and many times since Jun 28 so do not blame ddos.
  1258. Sent from my iPhone
  1259.  
  1260. From: Andrew Boeger <[email protected]>
  1261. Sent: Mon, 03 Jul 2017 11:01:17 -0400
  1262. To: "Support - ReliableSite.Net LLC" <[email protected]>
  1263. Subject: Re: [239-20EA6EFE-030E] Cannot connect to network
  1264.  
  1265. You saw the MTR in the ticket showing total packet loss on choopa.net systems? My server settings are not causing this.
  1266. Sent from my iPhone
  1267.  
  1268. From: General Support
  1269. Sent: Mon, 03 Jul 2017 12:34:50 -0400
  1270. To: [email protected]
  1271. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1272.  
  1273. Hello,
  1274.  
  1275. This has been resolved.  Kindly check and let us know if you need further assistance. 
  1276.  
  1277. Thank you,
  1278. Shahalam H. - NYC Metro Center Tech
  1279. ReliableSite Hosting
  1280.  
  1281. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1282.  
  1283. From: General Support
  1284. Sent: Mon, 03 Jul 2017 11:03:32 -0400
  1285. To: [email protected]
  1286. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1287.  
  1288. Hello,
  1289.  
  1290. We have received your request.
  1291.  
  1292. We are looking into this and will get back to you shortly. 
  1293. ?
  1294.  
  1295. Thank you,
  1296. Shahalam H. - NYC Metro Center Tech
  1297. ReliableSite Hosting
  1298.  
  1299. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1300. Attachments: EF21863B5FFE49FE820587F9BADD2179.png (1 KB)
  1301.  
  1302. Alex S. - NYC Metro Data Center Manager
  1303. Yesterday at 6:07 PM Employee Post
  1304. Cannot connect to network
  1305. Hello,
  1306.  
  1307. Networking is requesting a MTR in both directions if possible.
  1308.  
  1309. Thank you,
  1310. Alex S. - NYC Metro Data Center Manager
  1311. ReliableSite Hosting
  1312.  
  1313. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1314.  
  1315. Alex S. - NYC Metro Data Center Manager
  1316. Yesterday at 4:55 PM Employee Post
  1317. Cannot connect to network
  1318. Hello,
  1319.  
  1320. Networking is evaluating this issue. We will update you as soon as we have a response from them.
  1321.  
  1322. Thank you,
  1323. Alex S. - NYC Metro Data Center Manager
  1324. ReliableSite Hosting
  1325.  
  1326. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1327.  
  1328. Nithin T. - Systems Administrator
  1329. Yesterday at 4:22 PM Employee Post
  1330. Cannot connect to network
  1331. Hello,
  1332.  
  1333. We will check on this and will update you shortly. 
  1334.  
  1335. Thank you,
  1336. Nithin T. - Systems Administrator
  1337. ReliableSite Hosting
  1338.  
  1339. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1340.  
  1341.  
  1342. Yesterday at 4:10 PM
  1343. RE: Cannot connect to network
  1344. Hello,
  1345. Network has gone unavailable again. See below MTR from 207.214.246.130 showing severe packet loss within choopa.net network.
  1346.  
  1347. Sent from Mail for Windows 10
  1348. From: Support - ReliableSite.Net LLC
  1349. Sent: Monday, July 3, 2017 9:58 AM
  1350. To: [email protected]
  1351. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1352. Hello,
  1353.  
  1354. The issue was due to DDoS attack not filtering it properly.
  1355.  
  1356. Thank you,
  1357. Shahalam H. - NYC Metro Center Tech
  1358. ReliableSite Hosting
  1359.  
  1360. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1361.  
  1362. From: Andrew Boeger <[email protected]>
  1363. Sent: Mon, 03 Jul 2017 12:42:49 -0400
  1364. To: Support - ReliableSite.Net LLC <[email protected]>
  1365. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  1366.  
  1367. Hi Shahalam,
  1368. Can you please share what you mean by resolved? What was done? Did you change something on my server?
  1369. Thanks,
  1370. Andrew
  1371. Sent from Mail for Windows 10
  1372. From: Support - ReliableSite.Net LLC
  1373. Sent: Monday, July 3, 2017 9:35 AM
  1374. To: [email protected]
  1375. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1376. Hello,
  1377.  
  1378. This has been resolved.  Kindly check and let us know if you need further assistance. 
  1379.  
  1380. Thank you,
  1381. Shahalam H. - NYC Metro Center Tech
  1382. ReliableSite Hosting
  1383.  
  1384. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1385.  
  1386. From: General Support
  1387. Sent: Mon, 03 Jul 2017 11:03:32 -0400
  1388. To: [email protected]
  1389. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1390.  
  1391. Hello,
  1392.  
  1393. We have received your request.
  1394.  
  1395. We are looking into this and will get back to you shortly. 
  1396. ?
  1397.  
  1398. Thank you,
  1399. Shahalam H. - NYC Metro Center Tech
  1400. ReliableSite Hosting
  1401.  
  1402. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1403.  
  1404. From: Andrew Boeger <[email protected]>
  1405. Sent: Mon, 03 Jul 2017 11:01:17 -0400
  1406. To: "Support - ReliableSite.Net LLC" <[email protected]>
  1407. Subject: Re: [239-20EA6EFE-030E] Cannot connect to network
  1408.  
  1409. Network failure happened again this morning and many times since Jun 28 so do not blame ddos.
  1410. Sent from my iPhone
  1411.  
  1412. From: Andrew Boeger <[email protected]>
  1413. Sent: Mon, 03 Jul 2017 11:01:17 -0400
  1414. To: "Support - ReliableSite.Net LLC" <[email protected]>
  1415. Subject: Re: [239-20EA6EFE-030E] Cannot connect to network
  1416.  
  1417. You saw the MTR in the ticket showing total packet loss on choopa.net systems? My server settings are not causing this.
  1418. Sent from my iPhone
  1419.  
  1420. From: General Support
  1421. Sent: Mon, 03 Jul 2017 12:34:50 -0400
  1422. To: [email protected]
  1423. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1424.  
  1425. Hello,
  1426.  
  1427. This has been resolved.  Kindly check and let us know if you need further assistance. 
  1428.  
  1429. Thank you,
  1430. Shahalam H. - NYC Metro Center Tech
  1431. ReliableSite Hosting
  1432.  
  1433. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1434.  
  1435. From: General Support
  1436. Sent: Mon, 03 Jul 2017 11:03:32 -0400
  1437. To: [email protected]
  1438. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1439.  
  1440. Hello,
  1441.  
  1442. We have received your request.
  1443.  
  1444. We are looking into this and will get back to you shortly. 
  1445. ?
  1446.  
  1447. Thank you,
  1448. Shahalam H. - NYC Metro Center Tech
  1449. ReliableSite Hosting
  1450.  
  1451. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1452. Attachments: C87158EC5D854ECD9AE86E221AF9156C.png (132.4365234375 KB), 8279EA985D5D4997BBF5EF9F97E1715A.png (1 KB)
  1453.  
  1454. Shahalam H. - NYC Metro Center Tech
  1455. Yesterday at 12:57 PM Employee Post
  1456. Cannot connect to network
  1457. Hello,
  1458.  
  1459. The issue was due to DDoS attack not filtering it properly.
  1460.  
  1461. Thank you,
  1462. Shahalam H. - NYC Metro Center Tech
  1463. ReliableSite Hosting
  1464.  
  1465. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1466.  
  1467.  
  1468. Yesterday at 12:42 PM
  1469. RE: Cannot connect to network
  1470. Hi Shahalam,
  1471. Can you please share what you mean by resolved? What was done? Did you change something on my server?
  1472. Thanks,
  1473. Andrew
  1474. Sent from Mail for Windows 10
  1475. From: Support - ReliableSite.Net LLC
  1476. Sent: Monday, July 3, 2017 9:35 AM
  1477. To: [email protected]
  1478. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1479. Hello,
  1480.  
  1481. This has been resolved.  Kindly check and let us know if you need further assistance. 
  1482.  
  1483. Thank you,
  1484. Shahalam H. - NYC Metro Center Tech
  1485. ReliableSite Hosting
  1486.  
  1487. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1488.  
  1489. From: General Support
  1490. Sent: Mon, 03 Jul 2017 11:03:32 -0400
  1491. To: [email protected]
  1492. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1493.  
  1494. Hello,
  1495.  
  1496. We have received your request.
  1497.  
  1498. We are looking into this and will get back to you shortly. 
  1499. ?
  1500.  
  1501. Thank you,
  1502. Shahalam H. - NYC Metro Center Tech
  1503. ReliableSite Hosting
  1504.  
  1505. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1506.  
  1507. From: Andrew Boeger <[email protected]>
  1508. Sent: Mon, 03 Jul 2017 11:01:17 -0400
  1509. To: "Support - ReliableSite.Net LLC" <[email protected]>
  1510. Subject: Re: [239-20EA6EFE-030E] Cannot connect to network
  1511.  
  1512. Network failure happened again this morning and many times since Jun 28 so do not blame ddos.
  1513. Sent from my iPhone
  1514.  
  1515. From: Andrew Boeger <[email protected]>
  1516. Sent: Mon, 03 Jul 2017 11:01:17 -0400
  1517. To: "Support - ReliableSite.Net LLC" <[email protected]>
  1518. Subject: Re: [239-20EA6EFE-030E] Cannot connect to network
  1519.  
  1520. You saw the MTR in the ticket showing total packet loss on choopa.net systems? My server settings are not causing this.
  1521. Sent from my iPhone
  1522. Attachments: 24141D0B2BC849DFB053A17F80B521AB.png (1 KB)
  1523.  
  1524. Shahalam H. - NYC Metro Center Tech
  1525. Yesterday at 12:34 PM Employee Post
  1526. Cannot connect to network
  1527. Hello,
  1528.  
  1529. This has been resolved.  Kindly check and let us know if you need further assistance. 
  1530.  
  1531. Thank you,
  1532. Shahalam H. - NYC Metro Center Tech
  1533. ReliableSite Hosting
  1534.  
  1535. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1536.  
  1537. Shahalam H. - NYC Metro Center Tech
  1538. Yesterday at 11:03 AM Employee Post
  1539. Cannot connect to network
  1540. Hello,
  1541.  
  1542. We have received your request.
  1543.  
  1544. We are looking into this and will get back to you shortly. 
  1545. ​
  1546.  
  1547. Thank you,
  1548. Shahalam H. - NYC Metro Center Tech
  1549. ReliableSite Hosting
  1550.  
  1551. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1552.  
  1553.  
  1554. Yesterday at 11:01 AM
  1555. Re: Cannot connect to network
  1556. Network failure happened again this morning and many times since Jun 28 so do not blame ddos.
  1557. Sent from my iPhone
  1558.  
  1559.  
  1560. Yesterday at 11:01 AM
  1561. Re: Cannot connect to network
  1562. You saw the MTR in the ticket showing total packet loss on choopa.net systems? My server settings are not causing this.
  1563. Sent from my iPhone
  1564.  
  1565. Nithin T. - Systems Administrator
  1566. July 2 at 9:56 PM Employee Post
  1567. Cannot connect to network
  1568. Hello,
  1569.  
  1570. We can understand your frustration on this matter. The network related issues mainly occur firewall rules, DDoS on the IP, packet loss at the routing etc. When we checked the server, we could not find any network related issues. 
  1571.  
  1572. Upon checking your server bandwidth graph on the dedicated panel, we could see that the sever traffic was slightly increased at some point. Also, checked the IP '104.243.32.218' in DDoS history, we could see that there was a DDoS entry on last June 28. That was UDP attack towards the server on the port '25565'. You would need to configure your server DDoS configuration to mitigate this type of traffic. Also, you can block all the UDP traffic to the server. We recommend you to enable the option "Mitigation Block All UDP" which will block all UDP connections to the server and you can whitelist the needed UDP ports in the DDoS protection settings. Please refer the below links for configuring the DDoS settings as per your requirement.
  1573.  
  1574. http://support.reliablesite.net/kb/a228/service-ddos-management.aspx
  1575. http://support.reliablesite.net/kb/a195/advanced-ddos-settings.aspx
  1576.  
  1577. Thank you,
  1578. Nithin T. - Systems Administrator
  1579. ReliableSite Hosting
  1580.  
  1581. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1582.  
  1583.  
  1584. July 2 at 9:36 PM
  1585. Re: Cannot connect to network
  1586. You still are not answering my question. I will not keep asking it.
  1587. The problem is not the firewall, I have not changed the firewall in months!!!
  1588. Please ask billing to stop rebilling on my account. I do not want to do business with you anymore If your server firewall acts like this and blocks all traffic without ANY rules that say to do so!!!
  1589. Sent from my iPhone
  1590.  
  1591. Nithin T. - Systems Administrator
  1592. July 2 at 9:24 PM Employee Post
  1593. Cannot connect to network
  1594. Hello,
  1595.  
  1596. I have gone through the ticket and understand that you are facing network issue. When I checked the server the firewall is on and disabled the firewall on the server. I have monitored the server for 45 minutes and could not see any packet loss or network issue. I have taken mtr to the server from different geographic location and no packets was lost at our network. Also, I sent plenty of packets to the server and all the transmitted packet is received at the server. Please see the snippet.
  1597.  
  1598. -----------------
  1599. ping 104.243.32.218
  1600. --- 104.243.32.218 ping statistics ---
  1601. 860 packets transmitted, 860 received, 0% packet loss, time 860473ms
  1602. rtt min/avg/max/mdev = 87.000/87.222/91.320/0.385 ms
  1603. -------------------
  1604.  
  1605. It looks like the firewall get started automatically on the server which caused the connectivity issue. When you face the network connectivity issue again, please check the server firewall status via KVM console to verify the firewall is enabled or not. Currently, the server firewall is disabled. If you are still facing connectivity issue again on server firewall disabled, we need to bring the server in live OS environment for couple of hours for checking network connectivity for determine the issue is OS related or network related.
  1606.  
  1607.  
  1608. Thank you,
  1609. Nithin T. - Systems Administrator
  1610. ReliableSite Hosting
  1611.  
  1612. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1613.  
  1614. Nithin T. - Systems Administrator
  1615. July 2 at 8:22 PM Employee Post
  1616. Cannot connect to network
  1617. Hello,
  1618.  
  1619. I am going through the ticket and will update you shortly. 
  1620.  
  1621. Thank you,
  1622. Nithin T. - Systems Administrator
  1623. ReliableSite Hosting
  1624.  
  1625. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1626.  
  1627.  
  1628. July 2 at 8:05 PM
  1629. Re: Cannot connect to network
  1630. Firewall is not changing so it doesn’t make sense that server goes down for 10mins every few hours. It’s an intermittent issue. The firewall is permanent and not intermittent.
  1631. Sent from my iPhone
  1632.  
  1633. Shalikh T.J. - Systems Administrator
  1634. July 2 at 3:48 AM Employee Post
  1635. Cannot connect to network
  1636. Hello,
  1637.  
  1638. We are able to ping the server when the firewall is enabled or disabled. When the firewall was enabled, the server was not accessible from our end via SSH. The server was only accessible when the firewall was disabled. Currently, the firewall is disabled now. We recommend you to keep the firewall disabled to check whether this issue persists again. If not we can confirm that the issue will be with the firewall else we can proceed with a network test.
  1639.  
  1640. Please be noted that the server will be offline for 45-60 min during the network test.
  1641.  
  1642. Let us know your thoughts.
  1643.  
  1644. Thank you,
  1645. Shalikh T.J. - Systems Administrator
  1646. ReliableSite Hosting
  1647.  
  1648. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1649.  
  1650. Shalikh T.J. - Systems Administrator
  1651. July 2 at 3:33 AM Employee Post
  1652. Cannot connect to network
  1653. Hello,
  1654.  
  1655. We are looking into this and will get back to you shortly. 
  1656. ​
  1657.  
  1658. Thank you,
  1659. Shalikh T.J. - Systems Administrator
  1660. ReliableSite Hosting
  1661.  
  1662. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1663.  
  1664.  
  1665. July 2 at 2:44 AM
  1666. Re: Cannot connect to network
  1667. Why is the issue intermittent through the day if the firewall is the problem? I am not changing the firewall so it does not make sense that it is he problem.
  1668. Do you ping before and after changing the firewall?
  1669. Sent from my iPhone
  1670.  
  1671. Shalikh T.J. - Systems Administrator
  1672. July 2 at 1:26 AM Employee Post
  1673. Cannot connect to network
  1674. Hello,
  1675.  
  1676. By disabling the firewall I can connect to the server. Before enabling the firewall, please remove the particular rule which is rejecting the incoming connections to the server.and let us know if you face any issues regarding this.
  1677.  
  1678. Thank you,
  1679. Shalikh T.J. - Systems Administrator
  1680. ReliableSite Hosting
  1681.  
  1682. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1683.  
  1684.  
  1685.  
  1686.  
  1687. July 2 at 1:18 AM
  1688. RE: Cannot connect to network
  1689. Network is unavailable again.
  1690. I cannot provide you anything from the server to my machine, I cannot connect to the server! Below is from my machine to the server. Note all of my customers are also offline currently, around the United States. None can connect.
  1691.  
  1692. Sent from Mail for Windows 10
  1693. From: Support - ReliableSite.Net LLC
  1694. Sent: Saturday, July 1, 2017 10:05 PM
  1695. To: [email protected]
  1696. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1697. Hello,
  1698.  
  1699. I was monitoring your server and couldn't find any network drop till this time and your firewall has been enabled. Please check the firewall rules from your end and remove any particular rule which blocks the external connections. This might be the reason for the network issue. 
  1700.  
  1701. If you are facing this issue again. Kindly provide an MTR from the server to your local machine IP and from your local machine to the server at the time of issue so that I can assist you better in resolving this issue.
  1702.  
  1703. Please see the following for more information:
  1704.  
  1705. http://support.reliablesite.net/kb/a192/troubleshooting-reporting-network-and-packet-loss-issues.aspx
  1706.  ?
  1707. Thank you,
  1708. Shalikh T.J. - Systems Administrator
  1709. ReliableSite Hosting
  1710.  
  1711. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1712.  
  1713. From: Andrew Boeger <[email protected]>
  1714. Sent: Sun, 02 Jul 2017 00:47:09 -0400
  1715. To: "Support - ReliableSite.Net LLC" <[email protected]>
  1716. Subject: Re: [239-20EA6EFE-030E] Cannot connect to network
  1717.  
  1718. Is the firewall still down? It has been up for a very long time and is enforcing security that is imperative to the software I am running.
  1719. I cannot run this server without a firewall. Any user can take admin rights in my application if the firewall is down!!
  1720. Sent from my iPhone
  1721.  
  1722. From: General Support
  1723. Sent: Sun, 02 Jul 2017 00:11:01 -0400
  1724. To: [email protected]
  1725. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1726.  
  1727. Hello,
  1728.  
  1729. Upon checking the results you have provided, we can see the loss is at the server end. We have disabled the firewall on the server which might be blocking the incoming connections. While performing an MTR test from the server to your local IP, we were not able to find any issues from our end. Please see the results attached below for further clarification.
  1730. ===
  1731. root@RunicUniverse:~# mtr --report 142.254.177.57
  1732. Start: Sat Jul  1 21:04:45 2017
  1733. HOST: RunicUniverse               Loss%   Snt   Last   Avg  Best  Wrst StDev
  1734.   1.|-- hosted-by.reliablesite.ne  0.0%    10    1.2  36.2   0.8 243.7  77.1
  1735.   2.|-- vl325-br2.pnj1.choopa.net  0.0%    10    0.2   0.5   0.1   2.6   0.6
  1736.   3.|-- vl24-er2.pnj1.choopa.net   0.0%    10    0.3   3.2   0.2   9.5   3.8
  1737.   4.|-- ae5.cr1-nyc4.ip4.gtt.net   0.0%    10    0.7   4.5   0.7  36.8  11.3
  1738.   5.|-- xe-3-2-2.cr8-nyc3.ip4.gtt  0.0%    10    1.1   2.5   1.1   6.6   1.9
  1739.   6.|-- be3257.ccr21.jfk05.atlas.  0.0%    10    1.3   2.0   1.2   5.3   1.1
  1740.   7.|-- be2060.ccr41.jfk02.atlas.  0.0%    10    1.7  40.6   1.7  79.2  40.6
  1741.   8.|-- if-ae-12-2.tcore1.SQN-San  0.0%    10   79.2  44.4   8.0  87.2  38.4
  1742.   9.|-- if-ae-13-2.tcore2.LVW-Los  0.0%    10   78.9  48.9  18.8  78.9  31.6
  1743.  10.|-- be2687.ccr41.iah01.atlas.  0.0%    10   32.8  55.8  32.8  78.7  24.1
  1744.  11.|-- be2927.ccr21.elp01.atlas.  0.0%    10   48.8  65.8  48.6  85.4  17.9
  1745.  12.|-- agg2.lsancarc01r.socal.rr  0.0%    10   82.0  69.7  56.6  86.2  13.8
  1746.  13.|-- agg1.lamrcadq01r.socal.rr  0.0%    10   89.2  77.4  67.9  90.5  10.0
  1747.  14.|-- be2965.ccr41.lax04.atlas.  0.0%    10   68.6  74.6  68.4  79.9   5.5
  1748.  15.|-- 142.254.177.57             0.0%    10   78.0  80.3  77.8  82.7   2.4
  1749.  
  1750. ===
  1751. We will monitor your server for sometime to check whether the issue occurs again and will let you know the results.
  1752.  
  1753. Thank you,
  1754. Shalikh T.J. - Systems Administrator
  1755. ReliableSite Hosting
  1756.  
  1757. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1758.  
  1759. From: General Support
  1760. Sent: Sat, 01 Jul 2017 23:00:24 -0400
  1761. To: [email protected]
  1762. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1763.  
  1764. Hello,
  1765.     We are looking into this and let you know our findings 
  1766.  
  1767. Thank you,
  1768. Sean C. - NYC Metro Data Center Tech
  1769. ReliableSite Hosting
  1770.  
  1771. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1772. Attachments: 4BE56C076C874A7BBAB1B2EE2EAF5F9D.png (13.6640625 KB), EC81002619BF46BABE5DC6721DF97D0A.png (1 KB)
  1773.  
  1774. Shalikh T.J. - Systems Administrator
  1775. July 2 at 1:05 AM Employee Post
  1776. Cannot connect to network
  1777. Hello,
  1778.  
  1779. I was monitoring your server and couldn't find any network drop till this time and your firewall has been enabled. Please check the firewall rules from your end and remove any particular rule which blocks the external connections. This might be the reason for the network issue. 
  1780.  
  1781. If you are facing this issue again. Kindly provide an MTR from the server to your local machine IP and from your local machine to the server at the time of issue so that I can assist you better in resolving this issue.
  1782.  
  1783. Please see the following for more information:
  1784.  
  1785. http://support.reliablesite.net/kb/a192/troubleshooting-reporting-network-and-packet-loss-issues.aspx
  1786.  ​
  1787. Thank you,
  1788. Shalikh T.J. - Systems Administrator
  1789. ReliableSite Hosting
  1790.  
  1791. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1792.  
  1793.  
  1794. July 2 at 12:47 AM
  1795. Re: Cannot connect to network
  1796. Is the firewall still down? It has been up for a very long time and is enforcing security that is imperative to the software I am running.
  1797. I cannot run this server without a firewall. Any user can take admin rights in my application if the firewall is down!!
  1798. Sent from my iPhone
  1799.  
  1800. Shalikh T.J. - Systems Administrator
  1801. July 2 at 12:11 AM Employee Post
  1802. Cannot connect to network
  1803. Hello,
  1804.  
  1805. Upon checking the results you have provided, we can see the loss is at the server end. We have disabled the firewall on the server which might be blocking the incoming connections. While performing an MTR test from the server to your local IP, we were not able to find any issues from our end. Please see the results attached below for further clarification.
  1806. ===
  1807. root@RunicUniverse:~# mtr --report 142.254.177.57
  1808. Start: Sat Jul  1 21:04:45 2017
  1809. HOST: RunicUniverse               Loss%   Snt   Last   Avg  Best  Wrst StDev
  1810.   1.|-- hosted-by.reliablesite.ne  0.0%    10    1.2  36.2   0.8 243.7  77.1
  1811.   2.|-- vl325-br2.pnj1.choopa.net  0.0%    10    0.2   0.5   0.1   2.6   0.6
  1812.   3.|-- vl24-er2.pnj1.choopa.net   0.0%    10    0.3   3.2   0.2   9.5   3.8
  1813.   4.|-- ae5.cr1-nyc4.ip4.gtt.net   0.0%    10    0.7   4.5   0.7  36.8  11.3
  1814.   5.|-- xe-3-2-2.cr8-nyc3.ip4.gtt  0.0%    10    1.1   2.5   1.1   6.6   1.9
  1815.   6.|-- be3257.ccr21.jfk05.atlas.  0.0%    10    1.3   2.0   1.2   5.3   1.1
  1816.   7.|-- be2060.ccr41.jfk02.atlas.  0.0%    10    1.7  40.6   1.7  79.2  40.6
  1817.   8.|-- if-ae-12-2.tcore1.SQN-San  0.0%    10   79.2  44.4   8.0  87.2  38.4
  1818.   9.|-- if-ae-13-2.tcore2.LVW-Los  0.0%    10   78.9  48.9  18.8  78.9  31.6
  1819.  10.|-- be2687.ccr41.iah01.atlas.  0.0%    10   32.8  55.8  32.8  78.7  24.1
  1820.  11.|-- be2927.ccr21.elp01.atlas.  0.0%    10   48.8  65.8  48.6  85.4  17.9
  1821.  12.|-- agg2.lsancarc01r.socal.rr  0.0%    10   82.0  69.7  56.6  86.2  13.8
  1822.  13.|-- agg1.lamrcadq01r.socal.rr  0.0%    10   89.2  77.4  67.9  90.5  10.0
  1823.  14.|-- be2965.ccr41.lax04.atlas.  0.0%    10   68.6  74.6  68.4  79.9   5.5
  1824.  15.|-- 142.254.177.57             0.0%    10   78.0  80.3  77.8  82.7   2.4
  1825.  
  1826. ===
  1827. We will monitor your server for sometime to check whether the issue occurs again and will let you know the results.
  1828.  
  1829. Thank you,
  1830. Shalikh T.J. - Systems Administrator
  1831. ReliableSite Hosting
  1832.  
  1833. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1834.  
  1835. Sean C. - NYC Metro Data Center Tech
  1836. July 1 at 11:00 PM Employee Post
  1837. Cannot connect to network
  1838. Hello,
  1839.     We are looking into this and let you know our findings 
  1840.  
  1841. Thank you,
  1842. Sean C. - NYC Metro Data Center Tech
  1843. ReliableSite Hosting
  1844.  
  1845. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1846.  
  1847.  
  1848. July 1 at 10:51 PM
  1849. RE: Cannot connect to network
  1850. Network problems happening again. MTR is attached.
  1851.  
  1852. Sent from Mail for Windows 10
  1853. From: Support - ReliableSite.Net LLC
  1854. Sent: Saturday, July 1, 2017 12:53 PM
  1855. To: [email protected]
  1856. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1857. Hello,
  1858.  
  1859. It appears that the attachment you sent with the reply was blocked by the support system. Could you please copy and paste the result in your reply.
  1860.  
  1861.  
  1862. Thank you,
  1863. Ajay J. - Systems Administrator
  1864. ReliableSite Hosting
  1865.  
  1866. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1867.  
  1868. From: Andrew Boeger <[email protected]>
  1869. Sent: Sat, 01 Jul 2017 15:45:16 -0400
  1870. To: Support - ReliableSite.Net LLC <[email protected]>
  1871. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  1872.  
  1873. This is a sample now in case it helps.
  1874. Sent from Mail for Windows 10
  1875. From: Support - ReliableSite.Net LLC
  1876. Sent: Saturday, July 1, 2017 12:36 PM
  1877. To: [email protected]
  1878. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1879. Hello,
  1880.  
  1881. Kindly provide a MTR with source and destination IP's when you face the issue again, so that we may better assist you in resolving this issue.
  1882.  
  1883. If your firewall is blocking pings, kindly temporarily allow pings when creating an MTR.
  1884.  
  1885. Please see the following for more information:
  1886.  
  1887. http://support.reliablesite.net/kb/a192/troubleshooting-reporting-network-and-packet-loss-issues.aspx
  1888.  
  1889. Thank you,
  1890. Ajay J. - Systems Administrator
  1891. ReliableSite Hosting
  1892.  
  1893. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1894.  
  1895. From: Andrew Boeger <[email protected]>
  1896. Sent: Sat, 01 Jul 2017 15:29:46 -0400
  1897. To: Support - ReliableSite.Net LLC <[email protected]>
  1898. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  1899.  
  1900. Hi,
  1901. Please explain why your system shows networking keeps dropping out if ping is fine? My server has become unavailable for users around the world more than 4 times in the past 6 hours. It is fine right now but it will go down again, please tell me why networking keeps on failing.
  1902.  
  1903.  
  1904. Sent from Mail for Windows 10
  1905. From: Support - ReliableSite.Net LLC
  1906. Sent: Saturday, July 1, 2017 12:25 PM
  1907. To: [email protected]
  1908. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1909. Hello,
  1910.  
  1911. I'm able to ping the IP from my end.
  1912.  
  1913. ========
  1914. $ ping 104.243.32.218 -c 4
  1915. PING 104.243.32.218 (104.243.32.218) 56(84) bytes of data.
  1916. 64 bytes from 104.243.32.218: icmp_seq=1 ttl=53 time=87.1 ms
  1917. 64 bytes from 104.243.32.218: icmp_seq=2 ttl=53 time=87.2 ms
  1918. 64 bytes from 104.243.32.218: icmp_seq=3 ttl=53 time=87.2 ms
  1919. 64 bytes from 104.243.32.218: icmp_seq=4 ttl=53 time=87.1 ms
  1920. --- 104.243.32.218 ping statistics ---
  1921. 4 packets transmitted, 4 received, 0% packet loss, time 3091ms
  1922. rtt min/avg/max/mdev = 87.148/87.194/87.273/0.050 ms
  1923. ===========
  1924.  
  1925. Please check this from your end and let me know if you are facing any issues.
  1926.  
  1927. Thank you,
  1928. Ajay J. - Systems Administrator
  1929. ReliableSite Hosting
  1930.  
  1931. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1932.  
  1933. From: Andrew Boeger <[email protected]>
  1934. Sent: Sat, 01 Jul 2017 15:09:37 -0400
  1935. To: "Support - ReliableSite.Net LLC" <[email protected]>
  1936. Subject: Re: [239-20EA6EFE-030E] Cannot connect to network
  1937.  
  1938. Hello server has been unreachable for 30 minutes now - 2nd time today.
  1939. Please review and fix.
  1940. On Sat, Jul 1, 2017 at 7:51 AM, Support - ReliableSite.Net LLC <
  1941. [email protected]> wrote:
  1942.  
  1943. From: General Support
  1944. Sent: Sat, 01 Jul 2017 10:51:28 -0400
  1945. To: [email protected]
  1946. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1947.  
  1948. Hello,
  1949.  
  1950. We are happy to assist you.
  1951.  
  1952. Please re-open this ticket if you require any further support in this matter.
  1953.  
  1954. Our technicians are standing by for your convenience.
  1955.  
  1956. Thank you,
  1957. Suraj N. - Systems Administrator
  1958. ReliableSite Hosting
  1959.  
  1960. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1961.  
  1962. From: Andrew Boeger <[email protected]>
  1963. Sent: Sat, 01 Jul 2017 10:50:46 -0400
  1964. To: Support - ReliableSite.Net LLC <[email protected]>
  1965. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  1966.  
  1967. It’s working now… recovered on its own I guess.
  1968.  
  1969. Sent from Mail for Windows 10
  1970. From: Support - ReliableSite.Net LLC
  1971. Sent: Saturday, July 1, 2017 7:45 AM
  1972. To: [email protected]
  1973. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1974. Hello,
  1975.  
  1976. I'm able to ping the IP from my end.
  1977.  
  1978. ========
  1979.  
  1980. ping 104.243.32.218
  1981. PING 104.243.32.218 (104.243.32.218) 56(84) bytes of data.
  1982. 64 bytes from 104.243.32.218: icmp_seq=1 ttl=53 time=87.5 ms
  1983. 64 bytes from 104.243.32.218: icmp_seq=2 ttl=53 time=87.1 ms
  1984.  
  1985. ===========
  1986.  
  1987. Please check this from your end and let me know if you are facing any issues.
  1988.  
  1989. Thank you,
  1990. Suraj N. - Systems Administrator
  1991. ReliableSite Hosting
  1992.  
  1993. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  1994.  
  1995. From: General Support
  1996. Sent: Sat, 01 Jul 2017 10:39:29 -0400
  1997. To: [email protected]
  1998. Subject: [239-20EA6EFE-030E] Cannot connect to network
  1999.  
  2000. Hello,
  2001.  
  2002. We have received your request.
  2003.  
  2004. We are looking into this and will get back to you shortly. 
  2005.  
  2006. Thank you,
  2007. Suraj N. - Systems Administrator
  2008. ReliableSite Hosting
  2009.  
  2010. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2011.  
  2012. From: [email protected]
  2013. Sent: Sat, 01 Jul 2017 10:32:30 -0400
  2014. To: General Support
  2015. Subject: Cannot connect to network
  2016.  
  2017. Hello, no users can connect to or ping my server (104.243.32.218). Please urgently help. This is happening @ 7:30am Pacific time. [Los Angeles]
  2018.  
  2019. From: General Support
  2020. Sent: Sat, 01 Jul 2017 15:24:59 -0400
  2021. To: [email protected]
  2022. Subject: [239-20EA6EFE-030E] Cannot connect to network
  2023.  
  2024. Hello,
  2025.  
  2026. I'm able to ping the IP from my end.
  2027.  
  2028. ========
  2029. $ ping 104.243.32.218 -c 4
  2030. PING 104.243.32.218 (104.243.32.218) 56(84) bytes of data.
  2031. 64 bytes from 104.243.32.218: icmp_seq=1 ttl=53 time=87.1 ms
  2032. 64 bytes from 104.243.32.218: icmp_seq=2 ttl=53 time=87.2 ms
  2033. 64 bytes from 104.243.32.218: icmp_seq=3 ttl=53 time=87.2 ms
  2034. 64 bytes from 104.243.32.218: icmp_seq=4 ttl=53 time=87.1 ms
  2035. --- 104.243.32.218 ping statistics ---
  2036. 4 packets transmitted, 4 received, 0% packet loss, time 3091ms
  2037. rtt min/avg/max/mdev = 87.148/87.194/87.273/0.050 ms
  2038. ===========
  2039.  
  2040. Please check this from your end and let me know if you are facing any issues.
  2041.  
  2042. Thank you,
  2043. Ajay J. - Systems Administrator
  2044. ReliableSite Hosting
  2045.  
  2046. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2047.  
  2048. From: Andrew Boeger <[email protected]>
  2049. Sent: Sat, 01 Jul 2017 15:09:37 -0400
  2050. To: "Support - ReliableSite.Net LLC" <[email protected]>
  2051. Subject: Re: [239-20EA6EFE-030E] Cannot connect to network
  2052.  
  2053. Hello server has been unreachable for 30 minutes now - 2nd time today.
  2054. Please review and fix.
  2055. On Sat, Jul 1, 2017 at 7:51 AM, Support - ReliableSite.Net LLC <
  2056. [email protected]> wrote:
  2057.  
  2058. From: General Support
  2059. Sent: Sat, 01 Jul 2017 15:35:58 -0400
  2060. To: [email protected]
  2061. Subject: [239-20EA6EFE-030E] Cannot connect to network
  2062.  
  2063. Hello,
  2064.  
  2065. Kindly provide a MTR with source and destination IP's when you face the issue again, so that we may better assist you in resolving this issue.
  2066.  
  2067. If your firewall is blocking pings, kindly temporarily allow pings when creating an MTR.
  2068.  
  2069. Please see the following for more information:
  2070.  
  2071. http://support.reliablesite.net/kb/a192/troubleshooting-reporting-network-and-packet-loss-issues.aspx
  2072.  
  2073. Thank you,
  2074. Ajay J. - Systems Administrator
  2075. ReliableSite Hosting
  2076.  
  2077. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2078.  
  2079. From: Andrew Boeger <[email protected]>
  2080. Sent: Sat, 01 Jul 2017 15:29:46 -0400
  2081. To: Support - ReliableSite.Net LLC <[email protected]>
  2082. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  2083.  
  2084. Hi,
  2085. Please explain why your system shows networking keeps dropping out if ping is fine? My server has become unavailable for users around the world more than 4 times in the past 6 hours. It is fine right now but it will go down again, please tell me why networking keeps on failing.
  2086.  
  2087.  
  2088. Sent from Mail for Windows 10
  2089. From: Support - ReliableSite.Net LLC
  2090. Sent: Saturday, July 1, 2017 12:25 PM
  2091. To: [email protected]
  2092. Subject: [239-20EA6EFE-030E] Cannot connect to network
  2093. Hello,
  2094.  
  2095. I'm able to ping the IP from my end.
  2096.  
  2097. ========
  2098. $ ping 104.243.32.218 -c 4
  2099. PING 104.243.32.218 (104.243.32.218) 56(84) bytes of data.
  2100. 64 bytes from 104.243.32.218: icmp_seq=1 ttl=53 time=87.1 ms
  2101. 64 bytes from 104.243.32.218: icmp_seq=2 ttl=53 time=87.2 ms
  2102. 64 bytes from 104.243.32.218: icmp_seq=3 ttl=53 time=87.2 ms
  2103. 64 bytes from 104.243.32.218: icmp_seq=4 ttl=53 time=87.1 ms
  2104. --- 104.243.32.218 ping statistics ---
  2105. 4 packets transmitted, 4 received, 0% packet loss, time 3091ms
  2106. rtt min/avg/max/mdev = 87.148/87.194/87.273/0.050 ms
  2107. ===========
  2108.  
  2109. Please check this from your end and let me know if you are facing any issues.
  2110.  
  2111. Thank you,
  2112. Ajay J. - Systems Administrator
  2113. ReliableSite Hosting
  2114.  
  2115. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2116.  
  2117. From: Andrew Boeger <[email protected]>
  2118. Sent: Sat, 01 Jul 2017 15:09:37 -0400
  2119. To: "Support - ReliableSite.Net LLC" <[email protected]>
  2120. Subject: Re: [239-20EA6EFE-030E] Cannot connect to network
  2121.  
  2122. Hello server has been unreachable for 30 minutes now - 2nd time today.
  2123. Please review and fix.
  2124. On Sat, Jul 1, 2017 at 7:51 AM, Support - ReliableSite.Net LLC <
  2125. [email protected]> wrote:
  2126.  
  2127. From: General Support
  2128. Sent: Sat, 01 Jul 2017 10:51:28 -0400
  2129. To: [email protected]
  2130. Subject: [239-20EA6EFE-030E] Cannot connect to network
  2131.  
  2132. Hello,
  2133.  
  2134. We are happy to assist you.
  2135.  
  2136. Please re-open this ticket if you require any further support in this matter.
  2137.  
  2138. Our technicians are standing by for your convenience.
  2139.  
  2140. Thank you,
  2141. Suraj N. - Systems Administrator
  2142. ReliableSite Hosting
  2143.  
  2144. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2145.  
  2146. From: Andrew Boeger <[email protected]>
  2147. Sent: Sat, 01 Jul 2017 10:50:46 -0400
  2148. To: Support - ReliableSite.Net LLC <[email protected]>
  2149. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  2150.  
  2151. It’s working now… recovered on its own I guess.
  2152.  
  2153. Sent from Mail for Windows 10
  2154. From: Support - ReliableSite.Net LLC
  2155. Sent: Saturday, July 1, 2017 7:45 AM
  2156. To: [email protected]
  2157. Subject: [239-20EA6EFE-030E] Cannot connect to network
  2158. Hello,
  2159.  
  2160. I'm able to ping the IP from my end.
  2161.  
  2162. ========
  2163.  
  2164. ping 104.243.32.218
  2165. PING 104.243.32.218 (104.243.32.218) 56(84) bytes of data.
  2166. 64 bytes from 104.243.32.218: icmp_seq=1 ttl=53 time=87.5 ms
  2167. 64 bytes from 104.243.32.218: icmp_seq=2 ttl=53 time=87.1 ms
  2168.  
  2169. ===========
  2170.  
  2171. Please check this from your end and let me know if you are facing any issues.
  2172.  
  2173. Thank you,
  2174. Suraj N. - Systems Administrator
  2175. ReliableSite Hosting
  2176.  
  2177. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2178.  
  2179. From: General Support
  2180. Sent: Sat, 01 Jul 2017 10:39:29 -0400
  2181. To: [email protected]
  2182. Subject: [239-20EA6EFE-030E] Cannot connect to network
  2183.  
  2184. Hello,
  2185.  
  2186. We have received your request.
  2187.  
  2188. We are looking into this and will get back to you shortly. 
  2189.  
  2190. Thank you,
  2191. Suraj N. - Systems Administrator
  2192. ReliableSite Hosting
  2193.  
  2194. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2195.  
  2196. From: [email protected]
  2197. Sent: Sat, 01 Jul 2017 10:32:30 -0400
  2198. To: General Support
  2199. Subject: Cannot connect to network
  2200.  
  2201. Hello, no users can connect to or ping my server (104.243.32.218). Please urgently help. This is happening @ 7:30am Pacific time. [Los Angeles]
  2202. Attachments: A5CDC5680D5647668EDA5D7AE6C4D01E.png (15.6298828125 KB), 08C19E7B571E43849761F898333A958D.png (1 KB)
  2203.  
  2204. Ajay J. - Systems Administrator
  2205. July 1 at 3:52 PM Employee Post
  2206. Cannot connect to network
  2207. Hello,
  2208.  
  2209. It appears that the attachment you sent with the reply was blocked by the support system. Could you please copy and paste the result in your reply.
  2210.  
  2211.  
  2212. Thank you,
  2213. Ajay J. - Systems Administrator
  2214. ReliableSite Hosting
  2215.  
  2216. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2217.  
  2218.  
  2219. July 1 at 3:45 PM
  2220. RE: Cannot connect to network
  2221. This is a sample now in case it helps.
  2222.  
  2223. Sent from Mail for Windows 10
  2224. From: Support - ReliableSite.Net LLC
  2225. Sent: Saturday, July 1, 2017 12:36 PM
  2226. To: [email protected]
  2227. Subject: [239-20EA6EFE-030E] Cannot connect to network
  2228. Hello,
  2229.  
  2230. Kindly provide a MTR with source and destination IP's when you face the issue again, so that we may better assist you in resolving this issue.
  2231.  
  2232. If your firewall is blocking pings, kindly temporarily allow pings when creating an MTR.
  2233.  
  2234. Please see the following for more information:
  2235.  
  2236. http://support.reliablesite.net/kb/a192/troubleshooting-reporting-network-and-packet-loss-issues.aspx
  2237.  
  2238. Thank you,
  2239. Ajay J. - Systems Administrator
  2240. ReliableSite Hosting
  2241.  
  2242. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2243.  
  2244. From: Andrew Boeger <[email protected]>
  2245. Sent: Sat, 01 Jul 2017 15:29:46 -0400
  2246. To: Support - ReliableSite.Net LLC <[email protected]>
  2247. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  2248.  
  2249. Hi,
  2250. Please explain why your system shows networking keeps dropping out if ping is fine? My server has become unavailable for users around the world more than 4 times in the past 6 hours. It is fine right now but it will go down again, please tell me why networking keeps on failing.
  2251.  
  2252.  
  2253. Sent from Mail for Windows 10
  2254. From: Support - ReliableSite.Net LLC
  2255. Sent: Saturday, July 1, 2017 12:25 PM
  2256. To: [email protected]
  2257. Subject: [239-20EA6EFE-030E] Cannot connect to network
  2258. Hello,
  2259.  
  2260. I'm able to ping the IP from my end.
  2261.  
  2262. ========
  2263. $ ping 104.243.32.218 -c 4
  2264. PING 104.243.32.218 (104.243.32.218) 56(84) bytes of data.
  2265. 64 bytes from 104.243.32.218: icmp_seq=1 ttl=53 time=87.1 ms
  2266. 64 bytes from 104.243.32.218: icmp_seq=2 ttl=53 time=87.2 ms
  2267. 64 bytes from 104.243.32.218: icmp_seq=3 ttl=53 time=87.2 ms
  2268. 64 bytes from 104.243.32.218: icmp_seq=4 ttl=53 time=87.1 ms
  2269. --- 104.243.32.218 ping statistics ---
  2270. 4 packets transmitted, 4 received, 0% packet loss, time 3091ms
  2271. rtt min/avg/max/mdev = 87.148/87.194/87.273/0.050 ms
  2272. ===========
  2273.  
  2274. Please check this from your end and let me know if you are facing any issues.
  2275.  
  2276. Thank you,
  2277. Ajay J. - Systems Administrator
  2278. ReliableSite Hosting
  2279.  
  2280. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2281.  
  2282. From: Andrew Boeger <[email protected]>
  2283. Sent: Sat, 01 Jul 2017 15:09:37 -0400
  2284. To: "Support - ReliableSite.Net LLC" <[email protected]>
  2285. Subject: Re: [239-20EA6EFE-030E] Cannot connect to network
  2286.  
  2287. Hello server has been unreachable for 30 minutes now - 2nd time today.
  2288. Please review and fix.
  2289. On Sat, Jul 1, 2017 at 7:51 AM, Support - ReliableSite.Net LLC <
  2290. [email protected]> wrote:
  2291.  
  2292. From: General Support
  2293. Sent: Sat, 01 Jul 2017 10:51:28 -0400
  2294. To: [email protected]
  2295. Subject: [239-20EA6EFE-030E] Cannot connect to network
  2296.  
  2297. Hello,
  2298.  
  2299. We are happy to assist you.
  2300.  
  2301. Please re-open this ticket if you require any further support in this matter.
  2302.  
  2303. Our technicians are standing by for your convenience.
  2304.  
  2305. Thank you,
  2306. Suraj N. - Systems Administrator
  2307. ReliableSite Hosting
  2308.  
  2309. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2310.  
  2311. From: Andrew Boeger <[email protected]>
  2312. Sent: Sat, 01 Jul 2017 10:50:46 -0400
  2313. To: Support - ReliableSite.Net LLC <[email protected]>
  2314. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  2315.  
  2316. It’s working now… recovered on its own I guess.
  2317.  
  2318. Sent from Mail for Windows 10
  2319. From: Support - ReliableSite.Net LLC
  2320. Sent: Saturday, July 1, 2017 7:45 AM
  2321. To: [email protected]
  2322. Subject: [239-20EA6EFE-030E] Cannot connect to network
  2323. Hello,
  2324.  
  2325. I'm able to ping the IP from my end.
  2326.  
  2327. ========
  2328.  
  2329. ping 104.243.32.218
  2330. PING 104.243.32.218 (104.243.32.218) 56(84) bytes of data.
  2331. 64 bytes from 104.243.32.218: icmp_seq=1 ttl=53 time=87.5 ms
  2332. 64 bytes from 104.243.32.218: icmp_seq=2 ttl=53 time=87.1 ms
  2333.  
  2334. ===========
  2335.  
  2336. Please check this from your end and let me know if you are facing any issues.
  2337.  
  2338. Thank you,
  2339. Suraj N. - Systems Administrator
  2340. ReliableSite Hosting
  2341.  
  2342. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2343.  
  2344. From: General Support
  2345. Sent: Sat, 01 Jul 2017 10:39:29 -0400
  2346. To: [email protected]
  2347. Subject: [239-20EA6EFE-030E] Cannot connect to network
  2348.  
  2349. Hello,
  2350.  
  2351. We have received your request.
  2352.  
  2353. We are looking into this and will get back to you shortly. 
  2354.  
  2355. Thank you,
  2356. Suraj N. - Systems Administrator
  2357. ReliableSite Hosting
  2358.  
  2359. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2360.  
  2361. From: [email protected]
  2362. Sent: Sat, 01 Jul 2017 10:32:30 -0400
  2363. To: General Support
  2364. Subject: Cannot connect to network
  2365.  
  2366. Hello, no users can connect to or ping my server (104.243.32.218). Please urgently help. This is happening @ 7:30am Pacific time. [Los Angeles]
  2367.  
  2368. From: General Support
  2369. Sent: Sat, 01 Jul 2017 15:24:59 -0400
  2370. To: [email protected]
  2371. Subject: [239-20EA6EFE-030E] Cannot connect to network
  2372.  
  2373. Hello,
  2374.  
  2375. I'm able to ping the IP from my end.
  2376.  
  2377. ========
  2378. $ ping 104.243.32.218 -c 4
  2379. PING 104.243.32.218 (104.243.32.218) 56(84) bytes of data.
  2380. 64 bytes from 104.243.32.218: icmp_seq=1 ttl=53 time=87.1 ms
  2381. 64 bytes from 104.243.32.218: icmp_seq=2 ttl=53 time=87.2 ms
  2382. 64 bytes from 104.243.32.218: icmp_seq=3 ttl=53 time=87.2 ms
  2383. 64 bytes from 104.243.32.218: icmp_seq=4 ttl=53 time=87.1 ms
  2384. --- 104.243.32.218 ping statistics ---
  2385. 4 packets transmitted, 4 received, 0% packet loss, time 3091ms
  2386. rtt min/avg/max/mdev = 87.148/87.194/87.273/0.050 ms
  2387. ===========
  2388.  
  2389. Please check this from your end and let me know if you are facing any issues.
  2390.  
  2391. Thank you,
  2392. Ajay J. - Systems Administrator
  2393. ReliableSite Hosting
  2394.  
  2395. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2396.  
  2397. From: Andrew Boeger <[email protected]>
  2398. Sent: Sat, 01 Jul 2017 15:09:37 -0400
  2399. To: "Support - ReliableSite.Net LLC" <[email protected]>
  2400. Subject: Re: [239-20EA6EFE-030E] Cannot connect to network
  2401.  
  2402. Hello server has been unreachable for 30 minutes now - 2nd time today.
  2403. Please review and fix.
  2404. On Sat, Jul 1, 2017 at 7:51 AM, Support - ReliableSite.Net LLC <
  2405. [email protected]> wrote:
  2406. Attachments: 84BD3D32480D4FA49747F72BB0B7D8BD.png (1 KB)
  2407.  
  2408. Ajay J. - Systems Administrator
  2409. July 1 at 3:35 PM Employee Post
  2410. Cannot connect to network
  2411. Hello,
  2412.  
  2413. Kindly provide a MTR with source and destination IP's when you face the issue again, so that we may better assist you in resolving this issue.
  2414.  
  2415. If your firewall is blocking pings, kindly temporarily allow pings when creating an MTR.
  2416.  
  2417. Please see the following for more information:
  2418.  
  2419. http://support.reliablesite.net/kb/a192/troubleshooting-reporting-network-and-packet-loss-issues.aspx
  2420.  
  2421. Thank you,
  2422. Ajay J. - Systems Administrator
  2423. ReliableSite Hosting
  2424.  
  2425. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2426.  
  2427.  
  2428. July 1 at 3:29 PM
  2429. RE: Cannot connect to network
  2430. Hi,
  2431. Please explain why your system shows networking keeps dropping out if ping is fine? My server has become unavailable for users around the world more than 4 times in the past 6 hours. It is fine right now but it will go down again, please tell me why networking keeps on failing.
  2432.  
  2433.  
  2434. Sent from Mail for Windows 10
  2435. From: Support - ReliableSite.Net LLC
  2436. Sent: Saturday, July 1, 2017 12:25 PM
  2437. To: [email protected]
  2438. Subject: [239-20EA6EFE-030E] Cannot connect to network
  2439. Hello,
  2440.  
  2441. I'm able to ping the IP from my end.
  2442.  
  2443. ========
  2444. $ ping 104.243.32.218 -c 4
  2445. PING 104.243.32.218 (104.243.32.218) 56(84) bytes of data.
  2446. 64 bytes from 104.243.32.218: icmp_seq=1 ttl=53 time=87.1 ms
  2447. 64 bytes from 104.243.32.218: icmp_seq=2 ttl=53 time=87.2 ms
  2448. 64 bytes from 104.243.32.218: icmp_seq=3 ttl=53 time=87.2 ms
  2449. 64 bytes from 104.243.32.218: icmp_seq=4 ttl=53 time=87.1 ms
  2450. --- 104.243.32.218 ping statistics ---
  2451. 4 packets transmitted, 4 received, 0% packet loss, time 3091ms
  2452. rtt min/avg/max/mdev = 87.148/87.194/87.273/0.050 ms
  2453. ===========
  2454.  
  2455. Please check this from your end and let me know if you are facing any issues.
  2456.  
  2457. Thank you,
  2458. Ajay J. - Systems Administrator
  2459. ReliableSite Hosting
  2460.  
  2461. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2462.  
  2463. From: Andrew Boeger <[email protected]>
  2464. Sent: Sat, 01 Jul 2017 15:09:37 -0400
  2465. To: "Support - ReliableSite.Net LLC" <[email protected]>
  2466. Subject: Re: [239-20EA6EFE-030E] Cannot connect to network
  2467.  
  2468. Hello server has been unreachable for 30 minutes now - 2nd time today.
  2469. Please review and fix.
  2470. On Sat, Jul 1, 2017 at 7:51 AM, Support - ReliableSite.Net LLC <
  2471. [email protected]> wrote:
  2472.  
  2473. From: General Support
  2474. Sent: Sat, 01 Jul 2017 10:51:28 -0400
  2475. To: [email protected]
  2476. Subject: [239-20EA6EFE-030E] Cannot connect to network
  2477.  
  2478. Hello,
  2479.  
  2480. We are happy to assist you.
  2481.  
  2482. Please re-open this ticket if you require any further support in this matter.
  2483.  
  2484. Our technicians are standing by for your convenience.
  2485.  
  2486. Thank you,
  2487. Suraj N. - Systems Administrator
  2488. ReliableSite Hosting
  2489.  
  2490. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2491.  
  2492. From: Andrew Boeger <[email protected]>
  2493. Sent: Sat, 01 Jul 2017 10:50:46 -0400
  2494. To: Support - ReliableSite.Net LLC <[email protected]>
  2495. Subject: RE: [239-20EA6EFE-030E] Cannot connect to network
  2496.  
  2497. It’s working now… recovered on its own I guess.
  2498.  
  2499. Sent from Mail for Windows 10
  2500. From: Support - ReliableSite.Net LLC
  2501. Sent: Saturday, July 1, 2017 7:45 AM
  2502. To: [email protected]
  2503. Subject: [239-20EA6EFE-030E] Cannot connect to network
  2504. Hello,
  2505.  
  2506. I'm able to ping the IP from my end.
  2507.  
  2508. ========
  2509.  
  2510. ping 104.243.32.218
  2511. PING 104.243.32.218 (104.243.32.218) 56(84) bytes of data.
  2512. 64 bytes from 104.243.32.218: icmp_seq=1 ttl=53 time=87.5 ms
  2513. 64 bytes from 104.243.32.218: icmp_seq=2 ttl=53 time=87.1 ms
  2514.  
  2515. ===========
  2516.  
  2517. Please check this from your end and let me know if you are facing any issues.
  2518.  
  2519. Thank you,
  2520. Suraj N. - Systems Administrator
  2521. ReliableSite Hosting
  2522.  
  2523. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2524.  
  2525. From: General Support
  2526. Sent: Sat, 01 Jul 2017 10:39:29 -0400
  2527. To: [email protected]
  2528. Subject: [239-20EA6EFE-030E] Cannot connect to network
  2529.  
  2530. Hello,
  2531.  
  2532. We have received your request.
  2533.  
  2534. We are looking into this and will get back to you shortly. 
  2535.  
  2536. Thank you,
  2537. Suraj N. - Systems Administrator
  2538. ReliableSite Hosting
  2539.  
  2540. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2541.  
  2542. From: [email protected]
  2543. Sent: Sat, 01 Jul 2017 10:32:30 -0400
  2544. To: General Support
  2545. Subject: Cannot connect to network
  2546.  
  2547. Hello, no users can connect to or ping my server (104.243.32.218). Please urgently help. This is happening @ 7:30am Pacific time. [Los Angeles]
  2548. Attachments: BF36BBB054F040108796065C5709B230.png (102.2216796875 KB), D11DBC2192AD4D6B85C066F9244B07CA.png (1 KB)
  2549.  
  2550. Ajay J. - Systems Administrator
  2551. July 1 at 3:24 PM Employee Post
  2552. Cannot connect to network
  2553. Hello,
  2554.  
  2555. I'm able to ping the IP from my end.
  2556.  
  2557. ========
  2558. $ ping 104.243.32.218 -c 4
  2559. PING 104.243.32.218 (104.243.32.218) 56(84) bytes of data.
  2560. 64 bytes from 104.243.32.218: icmp_seq=1 ttl=53 time=87.1 ms
  2561. 64 bytes from 104.243.32.218: icmp_seq=2 ttl=53 time=87.2 ms
  2562. 64 bytes from 104.243.32.218: icmp_seq=3 ttl=53 time=87.2 ms
  2563. 64 bytes from 104.243.32.218: icmp_seq=4 ttl=53 time=87.1 ms
  2564. --- 104.243.32.218 ping statistics ---
  2565. 4 packets transmitted, 4 received, 0% packet loss, time 3091ms
  2566. rtt min/avg/max/mdev = 87.148/87.194/87.273/0.050 ms
  2567. ===========
  2568.  
  2569. Please check this from your end and let me know if you are facing any issues.
  2570.  
  2571. Thank you,
  2572. Ajay J. - Systems Administrator
  2573. ReliableSite Hosting
  2574.  
  2575. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2576.  
  2577.  
  2578. July 1 at 3:09 PM
  2579. Re: Cannot connect to network
  2580. Hello server has been unreachable for 30 minutes now - 2nd time today.
  2581. Please review and fix.
  2582. On Sat, Jul 1, 2017 at 7:51 AM, Support - ReliableSite.Net LLC <
  2583. [email protected]> wrote:
  2584.  
  2585. Suraj N. - Systems Administrator
  2586. July 1 at 10:51 AM Employee Post
  2587. Cannot connect to network
  2588. Hello,
  2589.  
  2590. We are happy to assist you.
  2591.  
  2592. Please re-open this ticket if you require any further support in this matter.
  2593.  
  2594. Our technicians are standing by for your convenience.
  2595.  
  2596. Thank you,
  2597. Suraj N. - Systems Administrator
  2598. ReliableSite Hosting
  2599.  
  2600. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2601.  
  2602.  
  2603. July 1 at 10:50 AM
  2604. RE: Cannot connect to network
  2605. It’s working now… recovered on its own I guess.
  2606.  
  2607.  
  2608. Sent from Mail for Windows 10
  2609. From: Support - ReliableSite.Net LLC
  2610. Sent: Saturday, July 1, 2017 7:45 AM
  2611. To: [email protected]
  2612. Subject: [239-20EA6EFE-030E] Cannot connect to network
  2613. Hello,
  2614.  
  2615. I'm able to ping the IP from my end.
  2616.  
  2617. ========
  2618.  
  2619. ping 104.243.32.218
  2620. PING 104.243.32.218 (104.243.32.218) 56(84) bytes of data.
  2621. 64 bytes from 104.243.32.218: icmp_seq=1 ttl=53 time=87.5 ms
  2622. 64 bytes from 104.243.32.218: icmp_seq=2 ttl=53 time=87.1 ms
  2623.  
  2624. ===========
  2625.  
  2626. Please check this from your end and let me know if you are facing any issues.
  2627.  
  2628. Thank you,
  2629. Suraj N. - Systems Administrator
  2630. ReliableSite Hosting
  2631.  
  2632. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2633.  
  2634. From: General Support
  2635. Sent: Sat, 01 Jul 2017 10:39:29 -0400
  2636. To: [email protected]
  2637. Subject: [239-20EA6EFE-030E] Cannot connect to network
  2638.  
  2639. Hello,
  2640.  
  2641. We have received your request.
  2642.  
  2643. We are looking into this and will get back to you shortly. 
  2644.  
  2645. Thank you,
  2646. Suraj N. - Systems Administrator
  2647. ReliableSite Hosting
  2648.  
  2649. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2650.  
  2651. From: [email protected]
  2652. Sent: Sat, 01 Jul 2017 10:32:30 -0400
  2653. To: General Support
  2654. Subject: Cannot connect to network
  2655.  
  2656. Hello, no users can connect to or ping my server (104.243.32.218). Please urgently help. This is happening @ 7:30am Pacific time. [Los Angeles]
  2657. Attachments: 883E8C2062C74715A59300270C81EB15.png (44.478515625 KB), CB988A21CBA44A7791A609D74DCDB7DB.png (1 KB)
  2658.  
  2659. Suraj N. - Systems Administrator
  2660. July 1 at 10:44 AM Employee Post
  2661. Cannot connect to network
  2662. Hello,
  2663.  
  2664. I'm able to ping the IP from my end.
  2665.  
  2666. ========
  2667.  
  2668. ping 104.243.32.218
  2669. PING 104.243.32.218 (104.243.32.218) 56(84) bytes of data.
  2670. 64 bytes from 104.243.32.218: icmp_seq=1 ttl=53 time=87.5 ms
  2671. 64 bytes from 104.243.32.218: icmp_seq=2 ttl=53 time=87.1 ms
  2672.  
  2673. ===========
  2674.  
  2675. Please check this from your end and let me know if you are facing any issues.
  2676.  
  2677. Thank you,
  2678. Suraj N. - Systems Administrator
  2679. ReliableSite Hosting
  2680.  
  2681. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2682.  
  2683. Suraj N. - Systems Administrator
  2684. July 1 at 10:39 AM Employee Post
  2685. Cannot connect to network
  2686. Hello,
  2687.  
  2688. We have received your request.
  2689.  
  2690. We are looking into this and will get back to you shortly. 
  2691.  
  2692. Thank you,
  2693. Suraj N. - Systems Administrator
  2694. ReliableSite Hosting
  2695.  
  2696. Need a server setup fast? Our rapid deploy servers are setup in 10 minutes.
  2697.  
  2698. Andrew Boeger
  2699. July 1 at 10:32 AM
  2700. Cannot connect to network
  2701. Hello, no users can connect to or ping my server (104.243.32.218). Please urgently help. This is happening @ 7:30am Pacific time. [Los Angeles]
Advertisement
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!