evertime i hit "connect" to the nodes, it starts to show the status of 3 or 4 nodes at once, then after like 1 minute i get the errors in the log "Disconnected due to port error" or "Disconnected due to time check error"
But I am NOT behind a router and i dont have any firewalls on only the windows fireall..
I get the same stuff man...."Disconnected due to time check error" and the software doesn´t have an option to auto conect!!!Share is sooo nice but winny doesn´t have this problems!!
Disconnected due to time check error is usualy caused by an incorrect system time. Check your clock and make sure it's set to the right time.
"Disconnected due to time check error is usualy caused by an incorrect system time. Check your clock and make sure it's set to the right time."
I´ve alredy did that and it continues to auto disconect me after some time....THIS SUCKS because share is really nice and I wanted to switch from winny to share....but after "TRYING" to use it for a month and been disconected ALL the time i give up man!!
Sucks to come back from work at night everyday and have NOTHING to watch!!Just because this stupid F...G program doesn´t have an auto connecting option!!!!!!And I am an expertise on P2P!!!
Another possible reason for the time check error is that the timestamp on the cache file(s) is wrong (say it's 2006 but the a cache file has the create date of 2007), which I found out once while messing with the system calendar. Solution to this was to copy the cache somewhere, removing the cache folder then replace it with the copy.
Oh and if all fails reinstall Share (remove everything first or unpack it to a new folder).
I think i´ve found the problem guys:
everytime my brother opens the bitcomet software on our network after a few minutes my share auto disconnect and the same thing happens if I open my bitspirit software to download torrents!!!!
This share program is very unstable and doesn´t have an auto reconnect option and THIS SUCKS!!!
Share is not unstable, in fact I've had it run for sometimes over a month nonstop in conjunction with several other p2p apps (winny and BT just to name a few) without any disconnection. What you said could only mean that there's some port conflict with the BT program you run, I don't use bitcomet nor bitspirit so I don't know how to do it but you need to configure them to use different port(s) than Share.
I am MCSE and work with network my friend.....my connections here at more than 20 p2p softwares(not that i use that at the same time...OF COURSE!!!)doesn´t have a single conflict and my router is one of the best on the market and very well configured!!winny + BT + emule here are like water in the rain...simple transparent!!!!!!
This share is a nice software but I can see ALOT of bugs in it(I am a programer too) bugs like time checking error and cache bugs....ETC...ETC....
And it´s a shame because it´s multiple download connection for files are simple better than winny in my opinion....but what can i do to fight against the force of a SUCKING CODE!!!
that´s why the winny creator has been arrested and the share hasn´t!!!( NICE CODING ).And don´t come with IP MASK with this one because today we live in a society that MASKED IPS are going to be overpassed by superior technology in security!!!
anyway... it´s a fucking SHAME here because when this works fine it can get you what you want REALLY FAST!!!(and that´s what matter)
Right if your router's so good why do you still have problem running the damn program with others while like I said I can run it along with anything else for months without any disconnection on my crappy router? Complain all you want but if you were such a computer genius figuring out how to set it up so it ran properly shouldn't be that hard.
Well I am running for a month emule and BT(2 bt clients at the same time on network)and NO SR. NO PROBLEMS HERE!!winny never crashes or disconnect and share does all this shit BUGS(YEAH BUGS) at the same time......so my fault.......my router´s fault......NAHHHHH!! I REALLY DON´T THINK SO!!
AND YEAH I AM A FREAKING GENIUS USING COMPUTERS , NETWORKS(ALL PROGRAMS AND OS) AND PROGRAMING TOO!!You don´t have to call me genius next time ,CALL ME " GOD " T_T
as I have more thab 15 years of networking, programing, hacking, coding, surfing and all the verbs you can find in the computer´s area!So please if you find SOME GOOD and really USEFUL information about this problems " SHARE " with the community!! Don´t " SHARE " just BUGS with your replies!!
Go write your own program. If Share was so buggy and such you don't have to use it, plenty of fish in the sea as they say.
Solutions have been given to your problems, both time check error and port error, if they don't work tough luck.
The time checking error isn't a bug, its just how the program works.
And since youre such a genius why don't you just go fix the problem yourself.
I get this error: "Disconnected due to port error" after being connected to Share for about 2 minutes... I've tried changing the ports around randomly to ones used by AIM... I am currently at college... is it the server blocking share? or is my port incorrectly configured?
college... yep pretty much sol by conventional means.
Okay, I thought it must have been my college blocking the port for Share to connect to, so I installed Share at my home, but I'm having the save "Disconnected due to port error" problems. I allowed Share past Windows Firewall, and port forwarded for my router... but I can't seem to get it to stay connected -____- can anyone help?
Try turning DMZ on if your router has it. I kept getting that error until I did. (Even though the port was forwarded correctly!)
I had the same problem. I use Win-XP and I have Zone Alarm firewall. I solved it when I opened my internet connection properties/Advanced and unchecked my Windows firewall. I still have Zone Alarm firewall blocking unwanted internet traffic. But Share works perfectly now.
Make sure your system time is correct in order to prevent the
"Disconnected due to time check error".
"Disconnected due to time check error"
i adjusted the BIOS and windows and router time to tokyo time.
then reinstalled Share.
firewall is off. port forwarded. tried turn oon DMZ.
and the error presists. any thought? or should give it up?
Thx!
lol... I turned my clock back 1 hour and the problem went away. I'm in Chicago (central time zone). It's possible that Share checks your location against your system time, but has some bug with daylight savings
Bingo te2rx! Nice catch! It makes sense now. Japan doesn't HAVE daylight savings time - they don't use it. The coder obviously didn't take international users into consideration when adding in this "feature" (I question the point of it period). Set your clock back a voila - it works (for me at least).
>>The coder obviously didn't take international users into consideration
that's cause the coder is Japanese and doesn't give a f**k about people in other countries and possibly didnt even want non japanese people to be using it.
What a faggot coded this crap? My system time is of no fucking business to your shitty p2p client, asshead.
I live in Venezuela, so we don't have to deal with DST... Share works fine here. I only had that problem once, and it was after installing Linux on my box, that messed with the clock (make sure to disable "The System Clock uses UTC" in your Linux installer!!!)
Tip #4123541 for Share: make sure that your clock has the correct hour!
Tip #4123542 for Share: If you live on some DST zone, ignore DST, it's a waste of time anyway.
Damn! My Share started just today to "disconnect due to port error"... I'm NOT behind any router/firewall, my connection is direct, BUT... Share keeps disconnecting after 5-10 minutes of being connected.
This is the first time in my life that i experience this problem with Share on my home DSL connection... so it's very weird.. I've tried changing the port, restarting Share/Windows/my DSL modem... but no luck, it keeps disconnecting :(
Any hint?
OK, that incident seems to be fixed (it was not my Share settings, because it happened in another computer plugged to the same modem)... just another odd issue with my ISP :?
What a faggot coded this crap? My system time is of no fucking business to your shitty p2p client, asshead.
This thread is all about running Japanese P2P software on GNU/Linux and other alternative platforms using Wine and other methods.
Well my isp block all my ports which means I cannot use share at all. if you got other isp then try it but I have no luck since there is only one isp that works at my area.
same issue: won't stay connected to a node for more than a minute, and disconnects with "port error" after 30-60 seconds. i've only seen "diffuse" connections once or twice briefly. port is forwarded correctly. i've even seen jp 2ch posts about this (search for the japanese text of the error message), with no better suggestions than "check your router" there, either, which we've all done. i even dumped packets, and I see the remote nodes connecting to my forwarded port, and share seems to immediately drop the connection. telnetting to the port disconnects immediately (that may be by design at that stage of initialization, though I suspect it isn't). buggy ...
also, despite setting upstream speed to 50k/sec, traffic on my router shows 800k/sec during this time, an order of magnitude more than I have, so it seems like share is completely saturating my upstream--thanks, I guess ...
maybe i'll get out the disassembler and try to hack the 50k/sec minimum away, since most people in the US don't have that much upstream, though it seems to be ignoring it anyway
"ignore dst"? uhh, you can't just "ignore" dst, unless you don't mind missing every appointment and schedule by an hour
api hooks might fix it
800KB/s??? This is not normal! It may not be Share, but another program (a trojan, perharps?). I've never experienced such issue (Share always obey my upstream speed limit).
Using a dissassembler would be a bit extreme, and Share does check itself aganist tampering, so your proposed solution may not work.
The traffic was directly corrolated to Share trying to connect. I don't really know what's going on, as TCP windows scaling shouldn't be letting that much data out. It seemed more like it was doing a bandwidth test.
I've yet to get a stable connection on this thing. Right now, it's not giving the port error (nothing has changed!), but still persistently disconnecting from each node after less than five seconds. I've seen other reports of this.
If I connect directly to its port on my IP, it just disconnects immediately. If I connect to its port on 127.0.0.1, however, I see protocol junk and it waits. I don't know why it's behaving differently there--it's accepting connections from localhost, but dropping them from the LAN IP. Each time it connects to a remote node, the remote node tries to connect back, so that may be related--if it drops the connection for some reason, decides the connection doesn't work, and drops the node, over and over. Still no clues as to why.
I put it in front of the router (directly on the internet), and it worked. I'm sure my port is forwarded, though, and I can't leave it like that.
If it's connecting to hosts for 3-4 seconds and disconnecting, you may either have a lot of stale nodes (clear your node list and add new ones), or you may just need to wait a minute for it to find some good ones (and it'll find new nodes automatically). I think connecting to search nodes for 30-60 seconds and disconnecting is normal: it's iterating through nodes, running your searches and moving on.
I've found that if I connect (via telnet) to the port on localhost, see the protocol garbage, and just disconnect, it seems to prevent the port error from coming up. It probably thinks it's an incoming connection (where connections on the real IP are being discarded for some reason) and stops thinking the port isn't forwarded.
But, it still never downloads. It just keeps searching. It probably needs to be able to connect to that port properly to receive data. I still have no idea why it's dropping the connections.
(I don't know why I'm saying all this, since nobody here has any clue, but maybe spelling it out to myself in this tiny text box will give me some ideas ...)
The same crap keeps happening to me. System time is correct, port is forwarded through the firewall and router, DMZ was attempted and failed, yet this program worked last week.