Need Some Xbslink Help

[JJIJR 666]

*RESOLVED* It ended up just working even though it had an error

 

 

I had this working back when Halo 4 was leaked. I'm not sure what went wrong since then... 

 

Anyways, the error I get is "could not resolve external IP address"

You can see it here:

22:19:10 : starting Engine

22:19:10 : @ UPnP device discovery started
22:19:16 : * udp listener dispatcher thread starting...
22:19:16 : * udp outgoing dispatcher thread starting...
22:19:16 : * initialized udp listener on port 31415
22:19:16 : * udp receiver thread started
22:19:16 : !! Could not resolve external IP Address.
22:19:16 : - sniffer created on device Network adapter 'Broadcom NetXtreme Gigabit Ethernet Driver' on local host
22:19:16 : - sniffer dispatcher thread starting...
22:19:16 : engine ready. waiting for incoming requests.

 

There is no actual popup (except a windows notification telling me the error was non-fatal). this is from the messages tab. My console is not detected under the info tabs either. Except when I am in the dashboard.

 

I really don't now what the problem could be. The only thing that changed since back when it worked was my antivirus, but I tried to disable it and it still didn't work.

 

Also, I don't know if this is significant, but xlink kai says network is reachable but doesn't find my console.

 

Hopefully i can get fixed before Saturday 

EDIT: I got my ports to work now but I still get the error. You can see it here:

23:43:02 : starting Engine
23:43:02 : * udp listener dispatcher thread starting...
23:43:02 : * udp outgoing dispatcher thread starting...
23:43:02 : * initialized udp listener on port 31415
23:43:02 : * udp receiver thread started
23:43:02 : !! Could not resolve external IP Address.
23:43:02 : - sniffer created on device Network adapter 'Broadcom NetXtreme Gigabit Ethernet Driver' on local host
23:43:02 : - sniffer dispatcher thread starting...
23:43:02 : contacting cloud server...
23:43:03 : incoming Port is OPEN
23:43:03 : engine ready. waiting for incoming requests.

[ddxcb 14]

Picture of the app, i think i know the problem, but suck at explaining.

 

team view is an option to help?

Edited February 15, 2013 by ddxcb

[JJIJR 666]

Picture of the app, i think i know the problem, but suck at explaining.

 

team view is an option to help?

im down for TV

[ddxcb 14]

im down for TV

send me teh id and such.

[JJIJR 666]

send me teh id and such.

sent

[ddxcb 14]

the last two things are wincap is installed and working properly, and also to turn off wireless.

 

that is a head BLOWN.

[JJIJR 666]

the last two things are wincap is installed and working properly, and also to turn off wireless.

 

that is a head BLOWN.

nope no luck

[ddxcb 14]

nope no luck

somthing with not able to bind the external ip. do not what to do.

Try with another pc?

[JJIJR 666]

Try with another pc?

Weird. same error, different PC. So at this point its either the Xbox or the entire network

[Thunder 468]

When it says cannot resolve external, that is probably connection based. I would checks ports and maybe change your external IP.

[JJIJR 666]

anyone else think they could help?

[Thunder 468]

It's definitely your network.  I'd see if you can get the DMZ plus thing to work.

[selyb 117]

"Could not resolve external IP", IIRC, means that XBSLink could not figure out your router/modem IP address. The most solid solution I can think of is to set up a dyndns account with some site, install a dyndns updater client, and put the dyndns address into xbslink as your external IP.

[JJIJR 666]

"Could not resolve external IP", IIRC, means that XBSLink could not figure out your router/modem IP address. The most solid solution I can think of is to set up a dyndns account with some site, install a dyndns updater client, and put the dyndns address into xbslink as your external IP.

for some reason it worked even with this error.

[selyb 117]

The following is not from experience with XBSLink but with other apps like P2P etc. It may be acting in passive only mode, meaning outgoing connections only. That means you could not connect to others who are passive only. It is also possible that XBSLink is trying to initialize things too quickly and generates that error once but on a subsequent attempt, succeeds.