what happened to the online documentation?

[Former Member]

Hi!

I can no longer reach the documentation for SQL Anywhere 16

http://dcx.sybase.com/index.html#sa160/en/sqlanywhere_en16/help_top_index.htm

Do anyone know what happend, has it changed location or what?

Could someone provide my with another link that works?

Thanks...

[VolkerBarth]

Hm, I can reach that URL as usual - what error message did you get?

[former_SQLA_member1694880]

Works as expected.

[Former Member]

I only get the response

that "The server on dcx.sybase.com does not respond"

[Former Member]

I can still not access it, but I can access

http://infocenter.sybase.com/help/index.jsp?topic=

but there is no doc about SQL Anywhere 16...

[Breck_Carter]

Seems ok in China: http://www.blockedinchina.net/?siteurl=dcx.sybase.com

[VolkerBarth]

In contrast to that one: http://www.blockedinchina.net/?siteurl=sqlanywhere.blogspot.ca

Hm, I'm puzzled.

[Former Member]

I am not in china, I'm in northern europe ...

I have nothing on my computer or job network that should block a page like this...

[Former Member]

if i try

http://network-tools.com

with dcx.sybase.com i just get time out and network is unreachable...

[Breck_Carter]

I see the same thing doing that... something is funky

[MarkCulp]

Which service request type did you try on network-tools? I just tried a http-headers request and it came back immediately with the correct response (302 Moved Temporarily)

Note: if you tried a 'ping' request then 'network is unreachable' is the correct response because Sybase servers/firewalls blocks all pings requests.

[Former Member]

192.138.151.171 is from United States(US) in region North America

TraceRoute from Network-Tools.com to 192.138.151.171 [dcx.sybase.com] Hop (ms) (ms) (ms) IP Address Host name 1 0 0 0 8.9.232.73 xe-5-3-0.edge3.dallas1.level3.net
2 42 42 42 4.69.145.62 vlan60.csw1.dallas1.level3.net
3 42 42 43 4.69.151.134 ae-63-63.ebr3.dallas1.level3.net
4 42 42 42 4.69.132.77 ae-3-3.ebr2.losangeles1.level3.net
5 42 42 42 4.69.148.202 ae-6-6.ebr2.sanjose5.level3.net
6 42 42 43 4.69.148.109 ae-1-100.ebr1.sanjose5.level3.net
7 41 42 42 4.69.148.138 ae-5-5.ebr1.sanjose1.level3.net
8 42 42 42 4.69.153.2 ae-61-61.csw1.sanjose1.level3.net
9 42 42 42 4.69.152.3 ae-11-60.car1.sanjose1.level3.net
10 Destination network unreachable Timed out Destination network unreachable -
11 Timed out Destination network unreachable Timed out -
12 Timed out Destination network unreachable Timed out -
13 Timed out Timed out Destination network unreachable -

Trace aborted.

[reimer_pods]

As the given URL works for other people (including me as of now), you might want to check for network access restrictions, gateways, filters, firewalls or other software blocking your access to that page.

[Former Member]

Much later I tried to access it at home, and I could, but it took along time to load the page, and I had no truble at all with other webpages...

today at the office I have absolutley no trouble at all accessing the documentation

but now I am going to download the documentation.....

[VolkerBarth]

I am going to download the documentation...

That's my recommendation, anyway - cf. Breck's rant article: Product Suggestion: Local Docs

[Breck_Carter]

Something at Sybase is stopping tracert, which fails for BOTH dcx.sybase.com AND sybase.com, but works for oracle.com.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\\Users\\Breck>tracert dcx.sybase.com

Tracing route to dcx.sybase.com [192.138.151.171]
over a maximum of 30 hops:

1     3 ms     1 ms     1 ms  192.168.1.1
  2    11 ms    40 ms    11 ms  agas-lns2a-m-lo.sentex.ca [67.43.128.6]
  3    12 ms    11 ms    11 ms  205.211.164.33
  4    12 ms    11 ms    11 ms  teleglobe-vl108.sentex.ca [67.43.129.244]
  5    13 ms    11 ms    12 ms  ix-20-513.tcore1.TNK-Toronto.as6453.net [209.58.
16.21]
  6    12 ms    12 ms    12 ms  if-11-0-0-4.core4.TNK-Toronto.as6453.net [64.86.
33.42]
  7    22 ms    24 ms    22 ms  if-2-3-2-0.tcore1.CT8-Chicago.as6453.net [63.243
.172.42]
  8    21 ms    50 ms    21 ms  ae7.edge3.chicago3.level3.net [4.68.110.193]
  9    76 ms    88 ms    76 ms  vlan51.ebr1.Chicago2.Level3.net [4.69.138.158]
 10    76 ms    77 ms    76 ms  ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
 11    76 ms    76 ms    78 ms  ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

12    76 ms    75 ms    76 ms  ae-3-3.ebr2.SanJose1.Level3.net [4.69.132.57]
 13    75 ms    74 ms    74 ms  ae-92-92.csw4.SanJose1.Level3.net [4.69.153.30]

14    76 ms    76 ms    76 ms  ae-41-90.car1.SanJose1.Level3.net [4.69.152.195]

15  SYBASE-INC.car1.SanJose1.Level3.net [4.53.16.162]  reports: Destination net
 unreachable.

Trace complete.

C:\\Users\\Breck>tracert sybase.com

Tracing route to sybase.com [192.138.151.104]
over a maximum of 30 hops:

1     1 ms     1 ms     1 ms  192.168.1.1
  2    11 ms    11 ms    11 ms  agas-lns2a-m-lo.sentex.ca [67.43.128.6]
  3    11 ms    11 ms    11 ms  205.211.164.33
  4    11 ms    11 ms    12 ms  teleglobe-vl108.sentex.ca [67.43.129.244]
  5    12 ms    14 ms    12 ms  ix-20-513.tcore1.TNK-Toronto.as6453.net [209.58.
16.21]
  6    13 ms    13 ms    11 ms  if-5-0-0-5.core4.TNK-Toronto.as6453.net [63.243.
172.25]
  7    51 ms    25 ms    32 ms  if-2-3-2-0.tcore1.CT8-Chicago.as6453.net [63.243
.172.42]
  8    22 ms    22 ms    21 ms  ae7.edge3.chicago3.level3.net [4.68.110.193]
  9    76 ms    76 ms    76 ms  vlan51.ebr1.Chicago2.Level3.net [4.69.138.158]
 10    76 ms    76 ms    76 ms  ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
 11    76 ms    76 ms    76 ms  ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

12    76 ms    76 ms    77 ms  ae-3-3.ebr2.SanJose1.Level3.net [4.69.132.57]
 13    74 ms    76 ms    77 ms  ae-82-82.csw3.SanJose1.Level3.net [4.69.153.26]

14    76 ms    76 ms    76 ms  ae-31-80.car1.SanJose1.Level3.net [4.69.152.131]

15     *     SYBASE-INC.car1.SanJose1.Level3.net [4.53.16.162]  reports: Destin
ation net unreachable.

Trace complete.

C:\\Users\\Breck>tracert oracle.com

Tracing route to oracle.com [137.254.120.50]
over a maximum of 30 hops:

1     1 ms     1 ms    <1 ms  192.168.1.1
  2    11 ms    11 ms    11 ms  agas-lns2a-m-lo.sentex.ca [67.43.128.6]
  3    11 ms    11 ms    11 ms  205.211.164.33
  4    11 ms    12 ms    11 ms  teleglobe-vl108.sentex.ca [67.43.129.244]
  5    12 ms    12 ms    12 ms  ix-20-513.tcore1.TNK-Toronto.as6453.net [209.58.
16.21]
  6    12 ms    12 ms    29 ms  if-11-0-0-4.core4.TNK-Toronto.as6453.net [64.86.
33.42]
  7    26 ms    23 ms    26 ms  if-0-3-2-0.tcore1.CT8-Chicago.as6453.net [63.243
.172.34]
  8    24 ms    24 ms    24 ms  ae7.edge3.chicago3.level3.net [4.68.110.193]
  9    59 ms    59 ms    60 ms  vlan52.ebr2.Chicago2.Level3.net [4.69.138.190]
 10    59 ms    60 ms    60 ms  ae-14-14.ebr1.Dallas1.Level3.net [4.69.151.118]

11    60 ms    59 ms    60 ms  ae-71-71.csw2.Dallas1.Level3.net [4.69.151.137]

12    61 ms    60 ms    60 ms  ae-2-70.edge5.Dallas3.Level3.net [4.69.145.78]
 13    60 ms    61 ms    60 ms  ORACLE-CORP.edge4.Dallas3.Level3.net [4.59.32.6]

14    83 ms    67 ms    66 ms  adcq7-itr-rtr-3-xe-3-0-1.oracle.com [141.146.0.1
77]
 15    62 ms    61 ms    61 ms  vp-ocoma-cms-adc.oracle.com [137.254.120.50]

Trace complete.

C:\\Users\\Breck>

[Breck_Carter]

ping fails for sybase.com, works for oracle.com

[MarkCulp]

See my comment above (to your comment in the question section): Sybase (and SAP) blocks all ICMP (aka ping) packets at their firewalls and this results in a Network / Destination Unreachable response when you try. This response is normal and expected when ICMP packets are blocked.

FWIW: Lots of companies (and security conscious individuals) block ICMP packets in their firewalls to protect themselves from potential security threats - there have been numerous attacks in the past on internet sites through the use of malformed / malicious ICMP packets; by blocking these types of packets the potential problem goes away.

[Breck_Carter]

LOL... I guess Oracle and Google don't care about security!

...and it doesn't explain the OP's difficulty with HTTP.

[graeme_perrow]

FWIW I also had trouble accessing dcx earlier today. I tried again a half hour later and it was fine.