can't run fifa 13 demo
I have tried to run the FIFA 13 demo = nothing happens. Also I cannot access Reiss.com website although I can on my iPhone on the same wifi so it's definitely a problem with the iMac. any ideas?
Mac Pro, Mac OS X (10.6.8)
Apple Event: May 7th at 7 am PT
I have tried to run the FIFA 13 demo = nothing happens. Also I cannot access Reiss.com website although I can on my iPhone on the same wifi so it's definitely a problem with the iMac. any ideas?
Mac Pro, Mac OS X (10.6.8)
Is this a Windows only game?
I think you may be right. Thanks.
Would you have any idea about the second part of my question? I was able to access Reiss.com with no problem until very recently.
Now I get:
"Safari can't open the page http://www.reiss.com because the server where this page is located isn't responding"
I have got this message for about 2 weeks now - can't be Reiss's site as I've contected them & they say all is fine.
I am able to access all the other websites I want, and can easily access Reiss.com on my iPhone using the same wifi.
I am stuck.
Hmmmm, try this in your broeser, does it get you there?
5.79.33.8
Unfortunately no.
This time I get "Safari can't open the page http://5.79.33.8 because the server where this page is located is't responding". So much the same as before.
It is a real mystery. I've been on the website loads of times before. Maybe an auto-update changed my settings somehow & is preventing me from doing so now.
Thanks for trying though.
Hmmm, something must be blocking it on your Mac I think... any AV software or such?
I think you're right. Don't know about AV software. What is that please?
Sorry - brain bit slow this morning. Anti-Virus software!
None that I've installed myself. Only security is that which Mac updates generate. Firewall is off. Do you know how I could check there's no other AV sofware?
Hmmm,
Open Network Utility in Applications>Utilities>Ping tab & see if you can Ping that IP, then try the Traceroute tab to that IP to see how far it goes...
Ping has started ...
PING 5.79.33.8 (5.79.33.8): 56 data bytes
64 bytes from 5.79.33.8: icmp_seq=0 ttl=233 time=218.445 ms
64 bytes from 5.79.33.8: icmp_seq=1 ttl=233 time=198.491 ms
64 bytes from 5.79.33.8: icmp_seq=2 ttl=233 time=213.095 ms
64 bytes from 5.79.33.8: icmp_seq=3 ttl=233 time=213.080 ms
64 bytes from 5.79.33.8: icmp_seq=4 ttl=233 time=192.753 ms
64 bytes from 5.79.33.8: icmp_seq=5 ttl=233 time=207.896 ms
64 bytes from 5.79.33.8: icmp_seq=6 ttl=233 time=217.583 ms
64 bytes from 5.79.33.8: icmp_seq=7 ttl=233 time=217.487 ms
64 bytes from 5.79.33.8: icmp_seq=8 ttl=233 time=197.511 ms
64 bytes from 5.79.33.8: icmp_seq=9 ttl=233 time=212.174 ms
--- 5.79.33.8 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 192.753/208.852/218.445/8.865 ms
Ignore * in the output, but report the last IP it reports...
Traceroute has started ...
traceroute to 5.79.33.8 (5.79.33.8), 64 hops max, 40 byte packets
1 192.168.1.2 (192.168.1.2) 16.401 ms 2.217 ms 0.959 ms
2 192.168.15.1 (192.168.15.1) 5.417 ms 12.903 ms 1.623 ms
3 * * *
4 10.41.164.193 (10.41.164.193) 74.514 ms 56.848 ms 64.877 ms
5 64.13.115.205 (64.13.115.205) 60.856 ms 65.807 ms 59.966 ms
6 64-13-49-226.war.clearwire-dns.net (64.13.49.226) 63.673 ms 59.124 ms 59.828 ms
7 xe-10-3-0.edge1.seattle3.level3.net (4.59.232.9) 95.223 ms 69.430 ms 54.824 ms
8 ae-32-52.ebr2.seattle1.level3.net (4.69.147.182) 210.385 ms 204.914 ms 209.801 ms
9 ae-2-2.ebr2.denver1.level3.net (4.69.132.54) 210.316 ms 194.193 ms 204.929 ms
10 ae-3-3.ebr1.chicago2.level3.net (4.69.132.62) 220.189 ms 230.458 ms 218.515 ms
11 ae-6-6.ebr1.chicago1.level3.net (4.69.140.189) 195.065 ms 204.424 ms 214.495 ms
12 ae-2-2.ebr2.newyork2.level3.net (4.69.132.66) 205.237 ms 214.397 ms 209.271 ms
13 ae-1-100.ebr1.newyork2.level3.net (4.69.135.253) 203.859 ms 214.358 ms 203.835 ms
14 ae-4-4.ebr1.newyork1.level3.net (4.69.141.17) 212.607 ms 204.264 ms 214.442 ms
15 ae-41-41.ebr2.london1.level3.net (4.69.137.65) 199.365 ms ae-43-43.ebr2.london1.level3.net (4.69.137.73) 206.266 ms ae-41-41.ebr2.london1.level3.net (4.69.137.65) 208.646 ms
16 vlan103.ebr1.london1.level3.net (4.69.143.93) 205.257 ms vlan102.ebr1.london1.level3.net (4.69.143.89) 209.226 ms 229.072 ms
17 ae-1-3.edge4.london2.level3.net (4.69.141.190) 232.587 ms 202.893 ms 209.715 ms
18 ae-0-11.edge3.london2.level3.net (4.69.200.125) 209.695 ms 208.842 ms 200.413 ms
19 rackspace-m.edge3.london2.level3.net (195.50.91.210) 214.577 ms 200.151 ms 194.041 ms
20 corea-edge5.lon3.rackspace.net (164.177.137.38) 205.733 ms coreb-edge5.lon3.rackspace.net (164.177.137.40) 209.593 ms corea-edge5.lon3.rackspace.net (164.177.137.38) 204.342 ms
21 core3-coreb.lon3.rackspace.net (164.177.137.19) 200.276 ms core3-corea.lon3.rackspace.net (164.177.137.7) 204.552 ms core3-coreb.lon3.rackspace.net (164.177.137.19) 204.492 ms
22 aggr331a-2-core3.lon3.rackspace.net (31.222.133.147) 226.234 ms 198.811 ms 219.886 ms
23 * * *
24 * * *
25 * * *
26 * * *
At first this looked very complicated but I did as you suggested. Results were disappointingly as follows
Ping has started…
ping: sendto: No route to host
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
...and so on until I stopped it
Then using Traceroute:
Traceroute has started...
traceroute to 5.79.33.8 (5.79.33.8), 64 hops max, 52 byte packets
1 * * *
2 * *traceroute: sendto: No route to host
traceroute: wrote 5.79.33.8 52 chars, ret=-1
*
traceroute: sendto: Host is down
3 traceroute: wrote 5.79.33.8 52 chars, ret=-1
*traceroute: sendto: Host is down
traceroute: wrote 5.79.33.8 chars, ret=-1
*traceroute: sendto: Host is down
traceroute: wrote 5.79.33.8 52 chars, ret=-1
*
4 * * *
...and so on until I stopped it.
This is weird because the website is fine. Thanks for your help so far. Any frther ideas are most welcome.
Yes! That workes instantly. Thank you.
Now my only question is why?
Thanks very much for your help.
There is something on your Mac or in your Router it seems that is banning http://www.reiss.com or it's IP, now normally that'd be some parental control SW, Anit Virus SW, or a listing in your hosts file, or something really strange like a Proxy setting that sends you to gaga land.
What this Prxy server does is not allow your computer, Router, Modem, ISP see that you're going to http://www.reiss.com at all, sort of a middle man passing notes back & forth.
Stumped but mulling...
can't run fifa 13 demo