[PeerCache] Count=30 Server_000=cache0.winmxworld.net Server_001=cache1.winmxworld.net Server_002=cache2.winmxworld.net Server_003=cache3.winmxworld.net Server_004=cache4.winmxworld.net Server_005=cache5.winmxworld.net Server_006=cache6.winmxworld.net Server_007=cache7.winmxworld.net Server_008=cache8.winmxworld.net Server_009=cache9.winmxworld.net Server_010=cache0.winmxcache.com Server_011=cache1.winmxcache.net Server_012=cache2.winmxcache.com Server_013=cache3.winmxcache.net Server_014=cache4.winmxcache.com Server_015=cache4.winmxcache.net Server_016=cache6.winmxcache.com Server_017=cache7.winmxcache.net Server_018=cache8.winmxcache.com Server_019=cache9.winmxcache.net Server_020=cache0.winmxconex.com Server_021=cache1.winmxconex.net Server_022=cache2.winmxconex.com Server_023=cache3.winmxconex.net Server_024=cache4.winmxconex.com Server_025=cache5.winmxconex.net Server_026=cache6.winmxconex.com Server_027=cache7.winmxconex.net Server_028=cache8.winmxconex.com Server_029=cache9.winmxconex.net in my robomx but wont auto join it did then stopped same with ws2_32dll in my fxs i have removed all fxs and robomx from my norton allow list clicked allow on start up and still no connection so nothing to do with firewall my bot sits with yellow bar and says connecting also as u can see my bot as no connection string in the room <Uncle-Bob410_00000>, the dll is in my fxs and that says peer cache sucsesfull and is green but the 3 connections remann red and say connection failed, and 1,s again iv striped all robomx and fxs from norton and re tryed, i have also diabled norton all together and windows fire wall and still the same,
If you changed the cache list, then there in no need for the dll.... Delete the dll and use only the changed cache lists to connect... this worked for me
Love you posted about this else where.. and I must admit im just making my rounds today so if you have replied there sorry for this..
I have to think that something other then the cache list or ws2_32.dll is causing this problem if niether work and they both work for others. Remove RoboMX from your firewall rules and restrat it. Let it ask for persmissions again or readd it to the firewall rules...
robomx as it stands right now (2.07/8) comes supplied with an outdated cache list you need to enable expert options, go to the network sheet & edit the peer cache list.. hostnames to enter can be found on the cache status page
Metis 2.6 with RoboMX 1.2.3.0 running fine here. I updated the RoboMX a few days ago to the latest 2.08, and it would not connect, so I reinstalled the Metis bot that I have used for the last 2 years and that connects fine.
Currently running metis 2.6 with robomx version 1.40 (at least thats what it says when I click about robomx on the help tab). I know its an older version but his was connecting with wpn fine with autojoin and autologin working up until about a week ago and, as the old saying goes "if it aint broke dont fix it!!". Now its broke! The problem with the messages when people leave started at the same time. Since then I have added the dll patch to the folder, rebooted pc and restarted with no effect. Keeping fingers crossed that some kind person out there has the solution to my problem.
That is hardly likely to be a dll problem, the dll simply allows you to connect to the WPN nothing more, perhaps you could let us know what Robo version you have your Metis running on as there are a few versions and some dont require patching.
my metis with the dll is NOT connecting - furthermore when people leave I get a "has left the room" without any username and end up with user showing twice in the room list when they return!
i have the latest 3rd party connection dll and having trouble with fxs as been fine untill today now cache succsessful but all 3 connections red no connections also in metis and shareguard changed connection addys to latest and thay are not connecting ne 1 else having this probb or is there a reason for it ??
