ooh, that sucks.

Was about to offer dyndns.org but looks like their old free service I used way back is gone. But http://www.noip.com is still around. Chances are there is a client for it in the EVG so you can set it all up in there.

Then the EVG updates noip and you'l get a hostname which always points to your IP.

On the FTP forwarding...yeah, you'll need to forward to a PC that is on the same subnet the EVG is on most probably. Anything behind the R6300 would be fun/wont work.

On having a PC connected to the EV being able to communicate with a PC behind the R6300.
You should be able to setup a static route in the EV pointing to the R6300.

Not knowing your network setup...
say the EV was 192.168.0.1  (setup in the 192.168.0.x subnet)

R6300 is in the 192.168.1.x subnet (as are all the devices behind this router)
The WAN interface of the R6300 would have an IP in the first subnet's range (eg. 192.168.0.2)

There should be a spot in the EV to set a static route to say
anything for subnet 192.168.1.x, go through the gateway, 192.168.0.2
(I guess if I had the manual handy or you did some screenshots if you need help)

To help you configure this it would probably be a good idea to turn off the windows firewall on a PC connected to the EV, and a PC on the other subnet so you can freely ping between them with no local firewall issues.

So say a PC behind the EV has an IP of 192.168.0.50
a PC behind the R6300 has an IP of 192.168.1.50

You should be able to ping each other (with firewalls off)

The windows way of doing the static route (instead of doing it in the router) would be something like
route add 192.168.1.0 mask 255.255.255.0 192.168.0.2
            (network you want to get at)            (ip of router that knows how to get to the network)

The other way, PC behind R6300 to PC behind EV route I'm not sure you'll need as a packet for 192.168.0.x would hit the R6300, it would then flow down to the EV which is on the correct LAN and route to where it needs to go.
If you did need to explicitly set the route for the other direction, you'd do the opposite, set a static route the other way in the R6300

The windows way for a PC behind the R6300 would be something like...
...assuming the LAN gateway IP of the R6300 is 192.168.1.1
route add 192.168.0.0 mask 255.255.255.0 192.168.1.1

Hope I'm not confusing the hell out of you :)  I might have to get Visio out and draw a diagram.

You should be able to get PCs/devices on both LANs being able to communicate to each other.

What you cannot do (being separate subnets) is use software which communicates via broadcasts, as the broadcast won't reach across subnets. eg, auto discovery stuff, like media servers, itunes finding another iTunes to share with etc

sounds more like an evg2k issue than anything else.

Well, after much faffin' around I'm pretty much back to where I was on Thursday night.

So what has happened?

1. Had whole network on same subnet (EVG as DHCP and gateway, R6300 acting dumb) but I couldn't get Parental Controls working because it looks at the gateway device. Sort of defeated the purpose of having the R6300 but there's other features on it which I wanted as well.
2. Tried different subnets
- EVG2000 on xxx.0.1
- R6300 on xxx.1.1 and DI-624S on xxx.1.2 each as a gateway
- was hoping devices could talk across different gateways but I guess that's the whole point of gateways. Didn't work.
3. Decided I'd use the USB FTP facility in either EVG2000 (192.168.0.1) or R6300 (192.168.1.3) - both acting again as gateways in their own right - rather than try to get them through the firewall to the NAS. Still yet to try this. Perhaps that's even safer, having the FTP outside the LAN.
4. Found out that the EVG2000 port forwarding screen hides shit from me making it impossible to port forward properly - had to restore a very old configuration to get it working again. A few frustrating hours indeed.

So, if I can make the simple FTP on the EVG2000 work then I'll be happy because I've got the system all routing back through the R6300 now and (I hope) can reinstate my parental controls.

Oh.  Didn't see you there.

Pixie, mine will just seem to pause for 25 seconds, then it will drop back to the file directory and give an error "can not play file". I will press play and it will work fine (even taking it to the same spot) for a few hours then it will do the same thing. Another bug i get sometimes is that it can't find any of my network shares  - even though nothing has changed and the WDTV has access to the internet no probs. Bit strange sometimes but worth the $50 i paid for it ($100 and got $50 cash back).