EQ2Botcommander problem with Windows 7

Y

yabong

Active Member
I've reloaded two machines with Windows 7 Ultimate. Had Symantec Enterprise Protection (SEP), then uninstalled, then installed Avast! antivirus suite. In both cases I turned on and off the Windows 7 firewall.

I could not get the EQ2Botcommander to connect from machine1 to machine2 on the default port 10101. When I switched to port 138 or 139, machine1 was able to connect, but it was basically a one-way communication. I could send an invite from machine1, but machine2 would not auto-accept the invite.

I configured the Windows firewall to accept Everquest2.exe and Innerspace.exe, TCP & UCP inbound and outbound on port 10101 on both machines. This still didn't work, whether it was on or off.

Can anyone tell me what protocols and/or what *.exe the EQ2Botcommander uses so that I can make exceptions through the firewall? Or, offer some suggestions as to how to get this to work?

I have used this successfully (on default settings) before on a Window7 Ultimate and Vista box. But basically had to turn off the firewall on the Vista box and make all the firewall exceptions on both machines.

Thanks in advance.
 
Y

yabong

Active Member
Okay...I tried this on machine2 in the IS Console:

"Uplink RemoteUplink -Connect machine1 139" AND I ran EQ2BotCommander on machine1. The default 10101 port did not work.

This solution still did not work for me, it's still a one way connection. I can send an invite from machine1, but machine2 doesn't do the --relay "all other" eq2execute acceptinvite" command from machine1

Although, if I manually do the command, it will work when the invite window is up when sent from machine1's EQ2BotCommander.

Any other suggestions?
 
Last edited:
W

wired203

Active Member
Either you don't have innerspace set to accept inbound connections on port whatever or you have a firewall enabled. I have been using Win7 enterprise since a month after it's release.

Just to clarify it's not a 1 way communication you are seeing, the invite is done via local client so there is no communication at all at that point. The communication occurs with the relay to accept the invite.
 
T

toleranse

Member
I have encountered a similar problem with the uplinks in eq2botcommander but only when attempting to uplink to 2 computers instead of just one.

If i try to uplink to either or of my other computers the uplink session connects and i can send invites that are accepted and can launch eq2bot from botcommander on both pc's.

If i however attempt to uplink all three computers at once the sessions claim to connect successfully but then no commands work on the remote PC's.

Anyone have any ideas what might be causing this? have looked up every thread i could find on this subject to no avail. I have confirmed that all three pc's have a unique name for this uplink and that incoming conncetions or port 10101 are enabled.

Whats frustrating is that i can connect to either or but not all three at once.

Thanks in advance
 
E

eddie43302

Senior Member
Did you update your main pc to the innerspace dev version.. cause when i do that on my main pc(tank pc) it wont let me send commands it basically breaks it.. i had to revert back to the non dev one for it to work..Just a thought..
 
T

toleranse

Member
Hey Eddie,

Thanks for the tip, but the problem of all things for me was a static IP set on the third PC. Why that causing this behavior I cannot begin to imagine but as soon as I set it for DHCP along with the rest they all work beautifuly now.

Thanks though,
T
 
You must log in or register to reply here.
Top Bottom