EVE Search - Singularity - not for mac users?

All Channels

Macintosh

Singularity - not for mac users?

» Click here to find additional results for this topic using Google

Monitor this thread via RSS [?]

Pages: [1] :: one page
Author	Thread Statistics \| Show CCP posts - 5 post(s)
Real Poison Minmatar Stormlord Battleforce Vanguard.	Posted - 2008.08.25 18:12:00 - [1] since weeks i've trying to get a test client to connect to singularity. it never ever worked, if at all i got satus unknown and now way of connecting to it (when i click connect anyway it just times out after a while). Today i've tried for the 10th time now, all i get is a dialog "New Build Available" -> There is a new build available. Would you like to download it now? The build is 0 MB in size.
Nenteculate	Posted - 2008.08.25 19:24:00 - [2] Should be a quick download then.
Remus Navillum z3r0 Gravity Sylph Alliance	Posted - 2008.08.25 19:38:00 - [3] I've had similar problems. If you're unable to download or install the new build, you may want to just install a fresh client, then apply the current Singularity patch. It's a slow and annoying process, but the Singularity patch installer seems kind of dysfunctional.

CCP Casqade	Posted - 2008.08.25 21:02:00 - [4] The mac patch is working and can be found here: http://www.eve-online.com/patches/patches.asp?s=singularity&system=mac&edition=classic Here are instructions on how to connect to Singularity: http://oldforums.eveonline.com/?a=topic&threadID=714213

Ami Nia	Posted - 2008.08.25 23:29:00 - [5] For CCP Cascade: Why don't you try doing what you suggest, before posting? I appreciate the fact that you are the only person in CCP that seems to actually read this forum. But I wonder how comes you did not do what I did: -) suspect that Real Poison did not read the sticky (you probably did this) -) prepare a reply to Real Poison pointing him to the sticky (you did this) -) verify the information you are about to give (that's where you stopped!) -) go to the sticky thread and follow the instructions in there before posting the reply -) notice they do not work -) read the rest of the sticky and realize that Real Poison did read it and even did post in it, multiple times -) refrain from posting in this thread until you found out more info For Real Poison: I never tried to connect to SySy (or any other test server) before. But seeing that you lament problems AND had read the sticky AND after I tried it myself and verified the problem, I wanted to dig further. It turns out that the instructions in the sticky OP are not sufficient and that the patching program lacks many features that it should have (and granted, this time there's no resort to "Apple drivers are bugged"). However, either you have some peculiar problem or you did not do your homework. The information needed to make it all working IS in that thread (but not in the OP). Curiously, the complete information has been posted in a sticky in the Game Development Forum as an addendum to the sticky in this forum (wouldn't it have made more sense to actually edit this sticky? I think yes, but somehow CCP disagrees). Here are the problems as I see them: -) there's no need to do the double install as per the instructions, you can simply copy the application. However make sure you understand the problem of file permissions for whatever is in /Applications if you do this (as for my way of doing it, I had never put the EvE application in /Applications to begin with: I created ~/Applications and work from there. This also solves some problems with multiple users on my machine). -) the patcher is bugged and will rename your SySy app to the default name, eventually deleting any default Eve app. Therefore make sure you DID rename the TQ app as suggested by the instructions (there's a reply in the sticky to this effect. This info should be added to the OP but they never did). You'll eventually want to rename the SySy app again after patching. -) if you simply follow the instructions, the patched app will still try to connect to TQ. For some reason the patcher fails to change the default server address. Under windows this is solved with a switch on the command line. The proposed solution for Macs is to change the .ini file to point to the SySy server (there's a reply in the sticky to this effect. This should definitively be put in the OP. It is specified in the Game Development Forum sticky but curiously it has never been edited into this sticky OP). -) there's an annoying side effect to the above: if you did not put the SySy server address in the .ini, then the SySy patched app will not work (because it tries to connect to TQ), but if you DO put it there, then the TQ app will not work (trying to connect to SySy). The easy solution, that nobody seems to have ever suggested, is to setup a separate preference folder for the SySy app (how? Well, that's exactly what you do when you want to run two clients concurrently, not really difficult. And there's a sticky for this). Now, let me know if the above is sufficient information for you to manage or if you need detailed instructions.
Real Poison Minmatar Stormlord Battleforce Vanguard.	Posted - 2008.08.26 07:18:00 - [6] @ami: thank you. and yes of course i've followed the instructions to the word, each and everytime in the last months whenever i tried to get a test client to connect. honestly i can only read cascade's comment as a disguised way of calling me stupid :P ok if it's that hard: <rant> THE MAC PATCHES FOR SINGULARITY ARE PLAIN BROKEN! THEY DO NOT WORK AT ALL! THEY HAVEN'T BEEN WORKING SINCE AT LEAST WEEKS OR MONTHS. AND OBVIOUSLY THE RESPONSIBLE DEVELOPER DIDN'T EVEN CARE TO TEST HIS WORK IN WEEKS/MONTHS! IN FACT HE WASTED A LOT OF YOUR CUSTOMERS AND SUPPORT STAFF'S TIME AND A LOT OF SERVER BANDWIDTH FOR DOWNLOADING BROKEN SOFTWARE. NOW, GO AHEAD AND TRY TO PROVE ME WRONG! BUT YOU'LL FAIL MISERABLY! GO TO THE DEV THAT'S IN CHARGE, TAKE AWAY HIS CANDY SUPPLIES FROM HIS DESK, LOCK HIM INTO THE OFFICE AND DON'T LET HIM OUT UNTIL IT'S FIXED. (AND DON'T FORGET TO CONFISCATE HIS SECRET BEER STASH FOR IMPROVED CODE QUALITY!) </rant>
Maria Kalista	Posted - 2008.08.26 10:49:00 - [7] Edited by: Maria Kalista on 26/08/2008 10:49:11 and then peeps wonder why the devs stay away from here.... Edit: szpellink
Real Poison Minmatar Stormlord Battleforce Vanguard.	Posted - 2008.08.26 11:06:00 - [8] Originally by: Maria Kalista Edited by: Maria Kalista on 26/08/2008 10:49:11 and then peeps wonder why the devs stay away from here.... Edit: szpellink i surely didn't not insult anyone, i just stated that the test client doesn't work, all in caps - maybe it was the caps. but what should i do when asking for help since weeks and all i get is a link to thread where i already posted 3 times without getting an answer.

CCP Casqade	Posted - 2008.08.26 13:24:00 - [9] After some investigation, I believe that the problem here has been a series of unfortunate coincidences. Originally by: Ami Nia -) suspect that Real Poison did not read the sticky (you probably did this) -) prepare a reply to Real Poison pointing him to the sticky (you did this) -) verify the information you are about to give (that's where you stopped!) Since I was able to find the patch and confirm that it was not 0MB in size I suspected that the auto patcher was somehow disabled or the patch was not uploaded to it. That's why I provided a link to the correct patch. The sticky instructions were also posted because there are more than Real Posion reading this thread and might be interested in connecting to Singularity. Originally by: Ami Nia -) go to the sticky thread and follow the instructions in there before posting the reply -) notice they do not work -) read the rest of the sticky and realize that Real Poison did read it and even did post in it, multiple times -) refrain from posting in this thread until you found out more info Done and point taken. The reason however that they do not work is that yesterday evening at 19:20 the test server Singularity was updated. Note that this was between the thread started and my reply. The change was that the patches built default to Tranquility instead of Singularity. This is not a normal case, that is why they are not in the instructions to begin with. Hagis McBree has provided instructions for how to solve this here. While I agree that this should probably be added to a section called "If Singularity patch is pointing to Tranquility do this:", that was not the original problem. I will however make sure that there is such a section after this post. Originally by: Ami Nia However, either you have some peculiar problem or you did not do your homework. The information needed to make it all working IS in that thread (but not in the OP). Curiously, the complete information has been posted in a sticky in the Game Development Forum as an addendum to the sticky in this forum (wouldn't it have made more sense to actually edit this sticky? I think yes, but somehow CCP disagrees). Again, this is true for you. Since you were trying this out after the server was updated. Originally by: Ami Nia -) there's no need to do the double install as per the instructions, you can simply copy the application. However make sure you understand the problem of file permissions for whatever is in /Applications if you do this (as for my way of doing it, I had never put the EvE application in /Applications to begin with: I created ~/Applications and work from there. This also solves some problems with multiple users on my machine). The reason for a simple 10-step instruction is that it is easy. There might be better ways of doing it and there is no need to have multiple installs to connect to Singularity. But most people that say "Hey, I want to try out the test server today" usually already have the Tranquility client installed and do not want it ruined. If they are met with simple instructions they will be encouraged to try it out rather than afraid. Originally by: Ami Nia -) the patcher is bugged and will rename your SySy app to the default name, eventually deleting any default Eve app. Therefore make sure you DID rename the TQ app as suggested by the instructions (there's a reply in the sticky to this effect. This info should be added to the OP but they never did). You'll eventually want to rename the SySy app again after patching. The patcher is not bugged. This is how it works and the workaround, to rename your installed client, has been in the instructions since they were posted in February. Continue next post...


CCP Casqade	Posted - 2008.08.26 13:24:00 - [10] Originally by: Ami Nia -) if you simply follow the instructions, the patched app will still try to connect to TQ. For some reason the patcher fails to change the default server address. Under windows this is solved with a switch on the command line. The proposed solution for Macs is to change the .ini file to point to the SySy server (there's a reply in the sticky to this effect. This should definitively be put in the OP. It is specified in the Game Development Forum sticky but curiously it has never been edited into this sticky OP). Again, this is a special case that does not often happen. But point taken again and I will make sure that this is added. I hope that this is sufficient info provided, for me to continue posting in this thread. Originally by: Real Poison and yes of course i've followed the instructions to the word, each and everytime in the last months whenever i tried to get a test client to connect. The test server has for fact been working and the mac patches too, maybe not all the time since, well it is the test server and sometimes builds and patches break. Originally by: Real Poison honestly i can only read cascade's comment as a disguised way of calling me stupid :P I'm very sorry if that is the way you took it. It was not my intention at all. I wanted to help you find the correct patch, that was all. I was not aware of your other posts in the instructions thread. In the future, please remember that the best and fastest way to report that something is wrong with the test server is to use the bug report system. The test server is after all a test server, so problems like this will occur at times. When they do, bug report and we'll get on it as soon as we can. Everything should be working now. Please let me know if it isn't.

Ami Nia	Posted - 2008.08.26 14:21:00 - [11] Originally by: Real Poison Edited by: Real Poison on 26/08/2008 11:06:53 @ami: thank you. and yes of course i've followed the instructions to the word, each and everytime in the last months whenever i tried to get a test client to connect. One thing that is not clear from your post is if you did succeed in having a working SySy connection. Please tell me, as I may be able to help you further if you did not (I say I may because I was successful in doing it, but if you have some very peculiar problem nobody else has, I cannot give you any guarantee).
Ami Nia	Posted - 2008.08.26 15:02:00 - [12] Originally by: CCP Casqade The reason however that they do not work is that yesterday evening at 19:20 the test server Singularity was updated. Note that this was between the thread started and my reply. The change was that the patches built default to Tranquility instead of Singularity. This is not a normal case, that is why they are not in the instructions to begin with. Hagis McBree has provided instructions for how to solve this here. While I agree that this should probably be added to a section called "If Singularity patch is pointing to Tranquility do this:", that was not the original problem SiSi went up ad down multiple times yesterday. And also just past midnight this morning. (GMT times). I've read somewhere that yesterday it has been used for a while as an internal testing server. There's definitvely been some upgrade on SiSi sometime yesterday as the version number has changed (see Server Status) and the current patch (the one I downloaded) was built yesterday evening. You say the fact that the patch points to TQ is a temporary problem. I cannot know for sure what patch was available erlier, but there's some evidence that the patch has always been pointing to TQ and that it is not a temporary problem. -) Hagis McBree post is dated 2008.06.04 -) A post from CCP Tanis (fifth of the thread) in the Game Development Forum sticky indicates that as permanent, not as a temporary workaround (this is the post that puzzles me: why didn't CCP Tanis edit the incomplete instructions in the Macintosh forum sticky instead of amending them there? Note that whoever will edit this forum's sticky will then have to ALSO edit the post from CCP Tanis over there. This is a sick hidden dependency. I really hope CCP Tanis is a community manager but not a developer/programmer as this is exactly the sort of thing that makes code totally unmanageable). -) both the instructions for windows and those for Linux tell the users to add a command line switch to explicitly point the program to the SiSi server, hinting that the patch does NOT change the default server address in the program. Interestingly it's Hagis McBree to figure this out and provide a solution for the Mac, which make me wonder if there actually is a tester in CCP that takes a freshly installed Mac and goes though the suggested instructions to verify them at each patch. However it's true that the current patch was build yesterday evening. Therefore it may be that it was actually pointing to SiSi earlier and it is only an accident that it points to TQ today (in which case the instructions in the post from CCP Tanis were incorrect yesterday and it is an accident that they are correct now). Originally by: CCP Casqade The reason for a simple 10-step instruction is that it is easy. There might be better ways of doing it and there is no need to have multiple installs to connect to Singularity. But most people that say "Hey, I want to try out the test server today" usually already have the Tranquility client installed and do not want it ruined. If they are met with simple instructions they will be encouraged to try it out rather than afraid. True and agreed. Except that the instructions are not complete! And they are 11 steps (there are two step 9). Originally by: CCP Casqade Originally by: Ami Nia -) the patcher is bugged and will rename your SySy app to the default name, eventually deleting any default Eve app. The patcher is not bugged. This is how it works and the workaround, to rename your installed client, has been in the instructions since they were posted in February. A program that, while patching an installation, DELETES another installation WITH NO WARNING, is bugged. Really. Besides, since it renames the SiSi installation back to the default, I wonder if one can simply run the patcher first and rename it then.
Real Poison Minmatar Stormlord Battleforce Vanguard.	Posted - 2008.08.26 17:41:00 - [13] well the auto patcher dtill doesn't work: There was an unexpected error while retrieving patch status: Unable to download file o2/test/mac/eveclassicpatch60973-61505_test-mac.tgz from the server. Error: url //ccp.vo.llnwd.net/o2/test/mac/eveclassicpatch60973-61505_test-mac.tgz not found ...trying the latest manual patch with a complete fresh install next...
Ami Nia	Posted - 2008.08.26 17:55:00 - [14] Originally by: Real Poison ...trying the latest manual patch with a complete fresh install next... It should work. It worked for me yesterday. Keep us updated with success/failure.

CCP Casqade	Posted - 2008.08.26 18:02:00 - [15] Originally by: Ami Nia Originally by: Real Poison ...trying the latest manual patch with a complete fresh install next... It should work. It worked for me yesterday. Keep us updated with success/failure. No, it should not work to update yourself to the latest version if there is one or more released clients between the one you are currently on and the one you are trying to get. The autopatcher only offers autopatch from the previous to latest. Example: Monday: Build 50000 Tuesday: Build 50001 Wednesday: Build 50002 Then you will not be able to update from Monday to Wednesday via auto patching. But Tueday to Wednesday should be offered. Please do not present your speculation as facts on this forum.

Real Poison Minmatar Stormlord Battleforce Vanguard.	Posted - 2008.08.26 18:03:00 - [16] ok latest patch applied, my SiSi client is now: 5.11.61505 (the same as SiSi at this very time). Server Status page at http://games.chruker.dk/eve_online/server_status.php says it's online. but like everytime before i cannot connect :( it takes about 4 (!!!) minutes while it is "Checking Status". then i get Server: TEST SERVER (SINGULARITY) Status: UNKNOWN i have no outbound firewall active that could interfere. so what's wrong? is there any mac user currently able to connect to SiSi ?

CCP Casqade	Posted - 2008.08.26 18:21:00 - [17] Originally by: Real Poison Says it's online. but like everytime before i cannot connect :( it takes about 4 (!!!) minutes while it is "Checking Status". then i get Server: TEST SERVER (SINGULARITY) Status: UNKNOWN i have no outbound firewall active that could interfere. so what's wrong? is there any mac user currently able to connect to SiSi ? Singularity is up and running and accepting connections. I'm able to connect without any problems. A problem like this would indicate that there is something blocking your connection, what it is I cannot say. This might further explain why you have been experiencing problems over a long period of time.

Real Poison Minmatar Stormlord Battleforce Vanguard.	Posted - 2008.08.26 18:38:00 - [18] Originally by: CCP Casqade Singularity is up and running and accepting connections. I'm able to connect without any problems. when you say you're able to connect without any problems, you mean from a windows installation or from a mac? a couple of corpmates are logging onto SiSi without problems, it's just me that cannot connect from my mac. and yeah that's the problem i'm having and reporting in the other thread for quite a while. and if i cannot find help here where else? system.log also doesn't show much: Aug 26 20:28:58 neonmac tgUpdate[15377]: tgUpdate:INIT (0x0) Aug 26 20:28:58 neonmac tgUpdate[15377]: tgUpd:init Aug 26 20:28:59 neonmac tgUpdate[15377]: Error 70000001 Aug 26 20:28:59 neonmac tgUpdate[15377]: tgUpdate:DEALLOC (0x0) Aug 26 20:28:59 neonmac tgUpdate[15377]: Launching "/Applications/EVE Online SiSi.app/Contents/MacOS/cider" -psn & Aug 26 20:28:59 neonmac cider[15379]: Error reading affiliate.plist:The file ôaffiliate.plistö does not exist. Aug 26 20:28:59 neonmac [0x0-0x2d02d0].com.transgaming.EVEOnline[15377]: 2008-08-26 20:28:59.865 cider[15379:10b] Error reading affiliate.plist:The file ôaffiliate.plistö does not exist. Aug 26 20:29:00 neonmac [0x0-0x2d02d0].com.transgaming.EVEOnline[15377]: Could not stat /Applications/EVE Online SiSi.app/Contents/Resources/transgaming/f_drive (No such file or directory), ignoring drive F: Aug 26 20:29:02: --- last message repeated 1 time --- Aug 26 20:29:00 neonmac com.apple.launchd[146] ([0x0-0x2d02d0].com.transgaming.EVEOnline[15377]): Stray process with PGID equal to this dead job: PID 15383 PPID 15379 cider Aug 26 20:29:00 neonmac com.apple.launchd[146] ([0x0-0x2d02d0].com.transgaming.EVEOnline[15377]): Stray process with PGID equal to this dead job: PID 15379 PPID 1 cider
Ami Nia	Posted - 2008.08.26 19:25:00 - [19] Originally by: CCP Casqade Originally by: Ami Nia Originally by: Real Poison ...trying the latest manual patch with a complete fresh install next... It should work. It worked for me yesterday. Keep us updated with success/failure. No, it should not work to update yourself to the latest version if there is one or more released clients between the one you are currently on and the one you are trying to get. The autopatcher only offers autopatch from the previous to latest. Example: Monday: Build 50000 Tuesday: Build 50001 Wednesday: Build 50002 Then you will not be able to update from Monday to Wednesday via auto patching. But Tueday to Wednesday should be offered. Please do not present your speculation as facts on this forum. Whut? Real Poison wrote she would try the latest manual patch with a complete fresh install. Why are you talking of the autopatcher? The latest manual patch shall be eveclassicpatch58188-61505_test-mac, and a complete fresh install shall come from eve-001481_58188_mac. I say it should work as it worked for me yesterday. And it is not a speculation. It is a fact: I did that yesterday and it worked.
Ami Nia	Posted - 2008.08.26 19:32:00 - [20] Originally by: Real Poison ok latest patch applied, my SiSi client is now: 5.11.61505 (the same as SiSi at this very time). This means your patching worked. Originally by: Real Poison then i get Server: TEST SERVER (SINGULARITY) Status: UNKNOWN That means, for some reason, it is not talking to the server. Originally by: Real Poison i have no outbound firewall active that could interfere. so what's wrong? I do not know, at the moment. But it's something with the communication with the server. Originally by: Real Poison is there any mac user currently able to connect to SiSi ? Me. Just tried while I was editing this post and it worked.
Ami Nia	Posted - 2008.08.26 19:51:00 - [21] Originally by: Real Poison it takes about 4 (!!!) minutes while it is "Checking Status". then i get Server: TEST SERVER (SINGULARITY) Status: UNKNOWN I did a little test. First I disconnected my machine from all the networks (both ethernet and wireless). In this condition the EvE client starts near instantly and tells me that Singularity is status Unknown. Then I reconnected to the lan, but I disconnected the router from the internet. In this way the computer does see a network and has no way of locally knowing there's no connectivity past one hop (except by trying to communicate and failing by timeout, of course). In this condition the client takes a while to start up, then goes in the "checking status" mode for another while, then finally tells me status Unknown. It really seems you have connectivity problems toward the server. Next step is to try to ping SiSi and see if the pings go through. For me they do: $ ping 87.237.38.50 PING 87.237.38.50 (87.237.38.50): 56 data bytes 64 bytes from 87.237.38.50: icmp_seq=0 ttl=116 time=33.566 ms 64 bytes from 87.237.38.50: icmp_seq=1 ttl=116 time=34.607 ms 64 bytes from 87.237.38.50: icmp_seq=2 ttl=116 time=33.440 ms ^C --- 87.237.38.50 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max/stddev = 33.440/33.871/34.607/0.523 ms Can you ping? If not, where does your traceroute stop? Note: I'm assuming you are comfortable with tools like ping and traceroute and the command line in general, if this is not the case just tell me and I'll give you more detailed instructions.
Ami Nia	Posted - 2008.08.26 19:53:00 - [22] Originally by: CCP Casqade Singularity is up and running and accepting connections. I'm able to connect without any problems. A problem like this would indicate that there is something blocking your connection, what it is I cannot say. This might further explain why you have been experiencing problems over a long period of time. QFT. CCP Casqade is spot on about this.
Real Poison Minmatar Stormlord Battleforce Vanguard.	Posted - 2008.08.26 20:01:00 - [23] PING 87.237.38.50 (87.237.38.50): 56 data bytes 64 bytes from 87.237.38.50: icmp_seq=0 ttl=122 time=42.743 ms 64 bytes from 87.237.38.50: icmp_seq=1 ttl=122 time=43.225 ms 64 bytes from 87.237.38.50: icmp_seq=2 ttl=122 time=41.966 ms 64 bytes from 87.237.38.50: icmp_seq=3 ttl=122 time=42.436 ms 64 bytes from 87.237.38.50: icmp_seq=4 ttl=122 time=43.089 ms --- 87.237.38.50 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max/stddev = 41.966/42.692/43.225/0.455 ms neonmac:~ neongrau$ traceroute 87.237.38.50 traceroute to 87.237.38.50 (87.237.38.50), 64 hops max, 40 byte packets 1 192.168.1.2 (192.168.1.2) 0.815 ms 0.486 ms 0.713 ms 2 217.0.119.199 (217.0.119.199) 24.484 ms 23.688 ms 23.792 ms 3 217.0.89.138 (217.0.89.138) 23.964 ms 24.198 ms 23.688 ms 4 f-ea5.F.DE.net.DTAG.DE (62.154.16.165) 25.089 ms 25.356 ms 25.217 ms 5 62.156.138.94 (62.156.138.94) 26.661 ms 194.670 ms 24.428 ms 6 ffm-bb1-link.telia.net (80.91.249.81) 24.730 ms 30.629 ms ffm-bb1-link.telia.net (80.91.251.150) 24.972 ms 7 prs-bb1-pos7-0-0.telia.net (213.248.64.110) 41.327 ms prs-bb2-pos7-0-0.telia.net (213.248.65.117) 35.066 ms prs-bb2-link.telia.net (80.91.248.61) 34.921 ms 8 ldn-bb2-pos7-0-0.telia.net (213.248.65.113) 43.601 ms 42.974 ms ldn-bb1-link.telia.net (80.91.254.208) 42.133 ms 9 ldn-b4-link.telia.net (80.91.251.17) 43.065 ms 42.365 ms 41.507 ms 10 ccp-ic-124901-ldn-thon-s2.c.telia.net (213.248.90.90) 42.225 ms 43.326 ms 42.823 ms 11 * * * neonmac:~ neongrau$ traceroute -P icmp 87.237.38.50 traceroute to 87.237.38.50 (87.237.38.50), 64 hops max, 60 byte packets 1 192.168.1.2 (192.168.1.2) 0.655 ms 0.355 ms 0.413 ms 2 217.0.119.199 (217.0.119.199) 25.395 ms 23.855 ms 24.274 ms 3 217.0.89.138 (217.0.89.138) 24.570 ms 23.596 ms 24.975 ms 4 f-ea5.F.DE.net.DTAG.DE (62.154.16.165) 45.237 ms 82.754 ms 24.294 ms 5 62.156.138.94 (62.156.138.94) 25.567 ms 25.241 ms 25.174 ms 6 ffm-bb2-link.telia.net (80.91.254.166) 24.979 ms 25.848 ms 25.548 ms 7 prs-bb2-link.telia.net (80.91.248.65) 34.672 ms prs-bb2-link.telia.net (80.91.249.47) 35.955 ms prs-bb2-pos7-0-0.telia.net (213.248.65.117) 35.101 ms 8 ldn-bb2-link.telia.net (80.91.254.210) 44.801 ms ldn-bb1-link.telia.net (80.91.254.208) 41.980 ms ldn-bb1-pos7-2-0.telia.net (213.248.64.10) 42.473 ms 9 ldn-b4-link.telia.net (80.91.251.17) 44.145 ms 49.122 ms 46.491 ms 10 ccp-ic-124901-ldn-thon-s2.c.telia.net (213.248.90.90) 43.392 ms 42.512 ms 43.018 ms 11 87.237.38.50 (87.237.38.50) 42.547 ms 44.124 ms 42.283 ms dear ccp admins please forgive me the port scan... neonmac:~ neongrau$ nmap -sT -vv 87.237.38.50 Starting Nmap 4.20 ( http://insecure.org ) at 2008-08-26 21:57 CEST Note: Host seems down. If it is really up, but blocking our ping probes, try -P0 Nmap finished: 1 IP address (0 hosts up) scanned in 2.066 seconds neonmac:~ neongrau$ nmap -sT -vv -P0 87.237.38.50 Starting Nmap 4.20 ( http://insecure.org ) at 2008-08-26 21:58 CEST Initiating Parallel DNS resolution of 1 host. at 21:58 Completed Parallel DNS resolution of 1 host. at 21:58, 1.29s elapsed Initiating Connect() Scan at 21:58 Scanning 87.237.38.50 [1697 ports] Completed Connect() Scan at 21:58, 45.19s elapsed (1697 total ports) Host 87.237.38.50 appears to be up ... good. Interesting ports on 87.237.38.50: Not shown: 1695 filtered ports PORT STATE SERVICE 22/tcp closed ssh 23/tcp closed telnet what port is the test server normally supposed to be listening on? the scan might not have probed the correct port.
brainball GoonFleet GoonSwarm	Posted - 2008.08.26 20:14:00 - [24] Edited by: brainball on 26/08/2008 20:14:57 nmap by default does not scan high port ranges by default, so the server ports for eve are probably excluded as they are all above 2500 afaik. Also Ami Nia just because your paranoid doesn't mean there is a conspiracy in the videogame your playing.
Ami Nia	Posted - 2008.08.26 20:30:00 - [25] Originally by: brainball Edited by: brainball on 26/08/2008 20:14:57 nmap by default does not scan high port ranges by default, so the server ports for eve are probably excluded as they are all above 2500 afaik. Also Ami Nia just because your paranoid doesn't mean there is a conspiracy in the videogame your playing. I'm not sure what you are talking about. When did I say there was a conspiracy? Real Poison, I'm really puzzled by your results. I'm afraid your specific problem is not something I can help with from here. But since you have shown to be technically competent, if I were CCP/Cedega I would contact you directly and direct you to more tests to diagnose what is going on.
Real Poison Minmatar Stormlord Battleforce Vanguard.	Posted - 2008.08.26 20:38:00 - [26] seems to be port 26000: neonmac:~ neongrau$ telnet 87.237.38.50 26000 Trying 87.237.38.50... Connected to 87.237.38.50. Escape character is '^]'. *~??? q= ףp@ALIVE@ccp so connection works, is there a different port for the login?
brainball GoonFleet GoonSwarm	Posted - 2008.08.26 20:50:00 - [27] Originally by: Real Poison seems to be port 26000: neonmac:~ neongrau$ telnet 87.237.38.50 26000 Trying 87.237.38.50... Connected to 87.237.38.50. Escape character is '^]'. *~??? q= ףp@ALIVE@ccp so connection works, is there a different port for the login? It seems to be turning into a true mystery. Have you tried the magic trick of clearing your cache?

Pages: [1] :: one page
First page \| Previous page \| Next page \| Last page

COPYRIGHT NOTICE
EVE Online, the EVE logo, EVE and all associated logos and designs are the intellectual property of CCP hf. All artwork, screenshots, characters, vehicles, storylines, world facts or other recognizable features of the intellectual property relating to these trademarks are likewise the intellectual property of CCP hf. EVE Online and the EVE logo are the registered trademarks of CCP hf. All rights are reserved worldwide. All other trademarks are the property of their respective owners. CCP hf. has granted permission to EVE-Search.com to use EVE Online and all associated logos and designs for promotional and information purposes on its website but does not endorse, and is not in any way affiliated with, EVE-Search.com. CCP is in no way responsible for the content on or functioning of this website, nor can it be liable for any damage arising from the use of this website.