|
|
Rank: Member
Groups: Member
Joined: 7/18/2009
Posts: 6
Points: 18
Location: Orlando
|
We are grabbing the .RemoteEndpoing from the Connection object which is returned on CONNECTIONCOMPLETE event.
Consistantly on Vista32, when executing the ConnectAsync, then in ConnectionComplete delegate, we then pull for the REMOTEENDPOINT Value, and always have a "196.x.x.x" address. Which is completely incorrect.
Can you please look at this, and let me know when their is a fix for it.
Thank you
Shawn
|
|
Rank: Administration
Groups: Administration
Joined: 2/15/2008
Posts: 130
Points: 835
|
Hi,
Why do you think that the address you receive is incorrect?
|
|
Rank: Member
Groups: Member
Joined: 7/18/2009
Posts: 6
Points: 18
Location: Orlando
|
I'm sorry. Why do i think it is incorrect? Because the source was from one of our test systems here to which we know the IP address'. The 196.x.x.x was in italy somewhere??????
Are you saying you dont see this problem?
Shawn
|
|
Rank: Administration
Groups: Administration
Joined: 2/15/2008
Posts: 130
Points: 835
|
Thank you for bug posting. Updated version will be available this week.
|
|
Rank: Newbie
Groups: Member
Joined: 3/12/2010
Posts: 1
Points: 3
|
I'm getting this also. Making XF clients unable to send anything back to the server using this connection object that I get from Connect. Some data does comes through anyway when enough clients connects at once, which is very strange imo.
"Updated version will be available this week."
Where can I find this updated version?
|
|
|
Guest |
