Old Indain

That makes some sense, there are a few hubs that simply don't allow any mod clients, and we are considered a mod i suppose.....silly purist!

where are downloading from?....http://www.apexdc.net/download/, you should grab the setup file. If you want to save all your settings, here is the safest way, make a copy of your current apex folder and save it someplace out of the way. After you download the new apex install it in the same folder as your current apex and it will save all your settings. If for any reason things go to hell with the install you have the copy that you saved, just delete the one that bad and put the one you saved back where you had your old one.

this is off topic a bit, but reading back through the post here, I am kind of wondering why I am getting none of the errors or crashes, The only thing I have noticed on my side is the thing with the check IP in connection settings, but once I typed in my IP, as well as binding my static ip for my machine, it hasn't been a problem. as far as the other thing with the notification of your hub being hacked or having unseemly types nosing around I do believe it is a good thing and I would be checking it out promptly...Did I mention it would freak me right out if I saw that message? Other than that the thing seems to run very smooth for me and uses less memory to do it. I run XP pro and host a hub on the same machine I am using apex on and bot are doing great.

Mine is looking better than ever....probably the best since peerweb I do believe. =[ ApexDC++ 1.2.0B Compiled on: 2008-12-24 ]=- -=[ Uptime: 16 hours 35 min 29 sec ][ Cpu time: 0:06:00 ]=- -=[ Memory usage (peak): 28.04 MiB (35.95 MiB) ]=- -=[ Virtual memory usage (peak): 30.76 MiB (38.14 MiB) ]=- -=[ Downloaded: 239.92 KiB ][ Uploaded: 1.54 GiB ]=- -=[ Total download: 95.18 GiB ][ Total upload: 203.58 GiB ]=- -=[ System Uptime: 4 days 14 hours 14 min ]=- -=[ CPU Clock: 2004.607499 MHz ]=-

Yep that works just dandy, or it did for me, just used my own port numbers that i chose and my own p/w....I also used the IP address for my my machine, it did not like the local host...127. address. Handy thing, keeps from having to open windows in the client.

I'm afraid that is the case......unless you can find a way to work around the campus side firewall.

I run my hub on a remote server from time to time and there is no slow down whatsoever...and yes I use a dynamic updater to hold the hub address on the remote server, all connections to the hub will go through the server IP , It works the same as if you were hosting from on campus. only your not. ...heh The way mine is set up I use remote desktop to access the server and start and stop the hub as though it were on my machine You can also run the Apex client remotely in that fashion if you choose, we have a few users who have their home PC set up to run a client and access it from work or school. On the client side , if all your users are going to be on campus, I would think you would all be passive due to the fire wall issue, but it will not affect those off campus, the client's..i.e users connect direct to one another, not through the hub...the hub is just the train station, we the users are the train. hope that helps ya bud.

The reason You get that message is because shnshare.or is shut down...........however there is another shnshare hub made up of the old op's from there. If anyone needs the address pm me or email me.

I think this topic has come up before, but I haven't found it. But,...this tth inconsistency is getting worse, most of our users have been using apex and since the last client upgrade we have all experienced problems with , and it is getting worse. Is there a bug fix for this in the works?

Well, I thought about that, however the user's are all ops on my hub, and we are all using 1.10 apex I find a lot of this stuff is software and ISP issues in the long run. It could be the hub software itself I imagine. We use the newest version of Ynhub, and I have it on a dedicated server with a static ip. But it has been very steady and I see no errors showing from that side. I have this little thing with the favorite users going on for some time, just waited to bring it up, just to see if maybe it was me or them, or if it would clear up.

If this has be discussed before please feel free to slander/browbeat and take away my dc++ for a day. I have noticed that I am having some issues with the client remembering users that I have set to favorite, with a open slot at all times. I have to grant them a slot no matter what, isn't the client supposed to take care of that? Anyone else having this problem?

Damn Satan , thanks, I have been trying to figure out that little problem and what you had said about it, this little string made it perfectly clear....thanks

Heh, this thing just don't want to go away eh.... big Mucles post above has a lot of merit, I found this to be the case on tth inconsistency Several people were experiencing this problem, it turned out that we were all downloading from the same user and this user had a modem that was doing the dying cock roach thing. After it died completely and was replaced, the downloads started up with him again and the tth thing cleared right up. Little glitches in a file transfer can also bring it on. Personally I think it has something to do with Voo Doo dolls and black magic. In other words I think it may proove to be something that we just have to deal with from time to time, somebody mentioned that if you give it enough time it will clear up eventually.lol, yeah after hours and days of tossing around ideas and trying this and that it will clear up. In the case of a corrupted file the rebuilding of your hash index will work, but not so with a hardware problem. Thanks for taking this little problem as far as it has gone though, this is how we end up with a better client. Pass me one of those beers would ya?

have you tried to install a fresh copy of apex?.... something may have happened when you installed it, maybe corrupted it somewhere along the line. also make sure that you type in the hub address you are trying to connect to, don't use copy and paste, sometimes that will not work. IN the settings also make sure you put in a user name that you will use and also on the favorite hubs settings must have a user name, give those things a going over, and see if it helps. Peace.

seems like I have seen this before, are you connecting to your hub through the IP or through the hub domain name? If you are connecting via the IP try just going in through the domain name, that may help, I assume you are using something like no-ip to hold your domain.

I sent a couple of private messages to Crise and nothing seems to be getting through from my account Mgr. At least they are not showing in my sent box. Anyone else having that problem?

Right Oh on that one, ya need to find out the ip of your machine and enter that in your port settings in your router...I found it best to just go ahead and set a static ip for my machine, saves a tone of resetting. in case you need to know how to do that, just use command prompt and type ipconfig

Doh!!.......it was me....got to turn on send a copy of message to me thingy....so sorry1

which one? windows or router? if you are running xp got to your window firewalls setting and open a tcp and udp port for apexdc++..if you have XP you will find it in the control panel. If you are behind a router, you must have both the windows firewall, either open or turned off, then get into your router setup, in the port range forwarding.

It sounds like you need to open ports for your client, either in your windows firewall settings, or if you are using a router, in your router.

OK satan, toast and the rest of you....I know your sick and tired of this topic, and frankly, so am I, but that does not change the fact that we are still having this problem, there are at least 4 other folks with apex in my hub that has the same issue. We have all taken the steps suggested in here and the problem will stop for a time and start right back up again. I am finding it very hard to believe this is strictly a user problem...I know that i have started from scratch, fresh install and complete hash rebuild...several times. I think this things needs to be looked at a little more closely and not just pushed off on the user...Just my humble opinion. I do know one thing it is damned annoying.

seems kinda odd that if you have it all turned off, yet you still are segmenting or multi sourcing.....I have used every copy of apec thats came down the pike and it has worked for me....Maybe try grabbing another copy of the client and do a fresh install, or stick with dc++.

I re-did mine and it has been smooth as silk....I get dropped a lot also on the ISP side. It appears that re hashing has solved the problem for now, it may be a cumulative problem with consistant drop outs, only time will tell I suppose. Your lucky on the hour rehash time though, try a day or a good part of it, an hour would be a blessing.

Yep, that looks like it took care of it....thanx toast...It's a pain but it works !!