ID:1300981
 
Descriptive Problem Summary:
It appears to be specific to me, as my friends can't replicate this, but Export/Topic aren't functioning under a specific set of circumstances.
I'm fairly sure this is more a problem with my network than the software but it is proving to be a nuisance and I don't really know where else to go for help. I am aware that there are workarounds via checking to see if world.address is the same and then using localhost, but I'd rather get to the bottom of this now.

Numbered Steps to Reproduce Problem:
Both the client and the server are on my network
The client sends an Export() to the server using the IP of the server
The Export() is never sent and returns 0

Does the problem occur:
Every time

When does the problem NOT occur?
The problem doesn't occur if:
A: I use localhost:port instead of ip:port
B: The client or server aren't on my network

I feel like I should of mentioned:

Yes I'm portforwarded
No I'm not using a firewall
No I'm not using an antivirus
More notes:

He is able to receive Topic messages from others, and send to others. Just not to himself.
Are you using the internal or external IP of the server? Does either work?

Also, you say that both the client and server are on your network, but keep mentioning localhost. Are they both running on the same machine? Or separate machines?
tried world.internet_address instead of world.address??
In response to DarkCampainger
DarkCampainger wrote:
Are you using the internal or external IP of the server? Does either work?

Using the internal IP works, the external doesn't.

Also, you say that both the client and server are on your network, but keep mentioning localhost. Are they both running on the same machine? Or separate machines?

Both are running on my machine

FIREking wrote:
tried world.internet_address instead of world.address??

Irrelevent, I think.
Just...a correction:
byond://localhost:port works for him between his two servers.
byond://hisactualip:port does not.

He's using an actual constant string, not a variable.
mob/verb/sendText(T as text)
world.Export("byond://2.24.234.113:3065?[T]")

world
Topic(T)
world << T
Just so you know, world.address does not work on ec2 servers while world.internet_address does, so I mentioned this for you to try because they will give you different results on different machines.
Have you tried typing in your external ip into a browser? Does it redirect you to the router page?

A few routers for some reason which is unknown by me won't let a local computer use the external ip and will redirect you to the router config page, I've had two do this I don't know the reason but it may be the issue..
Yup, works as intended. I can ping my external perfectly fine too.
I don't see how this is a bug. Everything points to this being an issue with your network setup. If you can reach yourself via the local IP, there's no reason it should have a problem via the external one unless something on your network or your system is interfering.
I did kind of say that it was a network problem I just didn't particularly know where else to put it, plus it MAY of been an issue with the software, I just honestly don't know.
In response to Rushnut
Rushnut wrote:
I did kind of say that it was a network problem I just didn't particularly know where else to put it, plus it MAY of been an issue with the software, I just honestly don't know.

In those cases, it's usually best to post in Developer Help or BYOND Help first (depending on the issue) to rule out other causes before making a bug report. Because of the fact that no significant code difference is involved between working and non-working, just a change of IP address, that points to a network issue. I've moved this thread to Developer Help.
You mentioned it doesn't happen when the client or the server are not on your network. This means that someone can reach you by using the client. Is that a correct statement?
I can send Export()s to anyone not on my network, and receive them from anyone not on my network.

The ONLY case in which it doesn't work, is when I use my external IP as the address to Export() to.
Does your router have anything in it's logs of what is happening?

PortQry2.exe may help tell you if the port is open, blocked, or not listening, which may help. (http://support.microsoft.com/kb/832919)

Can you download wireshark to trace the communication? (Let me know if you need help reading the output)