|Unfortunately I cannot place the DVR in a wired location so I recently purchased a Linksys WET610N Bridge to place it onto the wireless network. I set on the router to take the position as the static ip : 192.168.1.101 and on the primary router I set the port forwarding to access the ip.|
Everything I see in your post tells me you're accessing the DVR internally. If this is correct then a port forward isn't needed. You forward a port to allow external traffic in past your firewall to a client or server on the internal (LAN) side.
Why would you use the IP of the DVR on the bridge? I would have used a different IP on the bridge, preferably one outside the DHCP scope. The reason I ask is, you had it working with the DVR set to 192.168.1.101 and then you make the Bridge that IP and it stops working.
If it were me doing this, I would do it one step at a time.
Step 1: setup the bridge and connect it.
Step 2: connect a laptop or PC that's set to get it's IP from DHCP and test. Does it work? If not, you have problems and start troubleshooting the issue with the Bridge.
If it does, then your DVR should connect and be accessible in the same fashion it always was (ie: type: http://192.168.1.101:2000)
If you are actually trying to get this setup to remotely access the DVR, first get it working internally (on the LAN). Once you have it working on the LAN, I would set it up so I can remote in to a computer in the LAN using RDC and then I'd open a web browser on that PC and connect to the DVR from the internal PC instead of trying to remote in directly to the DVR.
It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.