Should I assign
WiRNS to 192.168.0.44 (for example)? I thought the instructions said it should be assigned to my pc IP address!

My DVA works quite nicely. It has two servers:
the server is 192.168.0.111 (my pc!) on port 80
webserver is 192.168.0.111 on port 8080

Due to all the problems I only have DVArchive installed. I uninstalled WiRNS (it stopped working somehow) and IVSMagic.

I know you know more about this than me, but the instructions posted are not clear. I cannot "port forward" on my router, as shown in the instructions. I wish I could post a screenshot of my portforward page in my router...

Thanks! I hope not to confuse you, but being confused myself is like the blind leading the sighted!!!
Pete

Should I assign
WiRNS to 192.168.0.44 (for example)? I thought the instructions said it should be assigned to my pc IP address!

My DVA works quite nicely. It has two servers:
the server is 192.168.0.111 (my pc!) on port 80
webserver is 192.168.0.111 on port 8080

OK, no problem. Let's start from the beginning. All of the instructions assume that you are running only the application for which they're written.

First you need to set up three IP addresses for your PC. They can be 192.168.0.111, 192.168.0.112, 192.168.0.113 or any others. Imagine that your PC is three different boxes each of which is identified on your internal network by its unique IP address.

Leave DVA installed with IP 192.168.0.111.

Next install WiRNS and set its IP to 192.168.0.112, and its port to 19000.

Then install IVSM using IP 192.168.0.113 and ports of 8888 and 20000.

Port forwarding only comes into play for IVS transfers. So let's get the three applications coexisting on your PC then solve the router problems.

Do you know how to set up additional IP addresses for your PC?_________________Frank

Now you install the applications and check that each one starts and runs before going to the next one. Use the install instructions for each but with the IP addresses and ports we've already talked about._________________Frank

Well, Frank...I could not determine which of the three ip addresses the pc is using for itself...

So, since I had three reserved (as above) and I could not determine if .111 or .107 was being used by the pc, I figured I would try to bind WiRNS to .105. So, I went into my router, under port forwarding for 192.168.0.105 I told it to open TCP port 80 and UDP port 53 & 153, and saved the settings.

Then I did a repair of WiRNS, resulting in a reboot and request for new binding ip address and I used 192.168.0.105. Still, I cannot get access to the ip address for configuration purposes ("firefox can't establish connection" message).

Thanks for your help Frank. I am still lost and trying to understand what is going on.

I got to the firewall settings, and the WiRNS Service Monitor.exe was already an exception, so I opened TCP 80, UDPs 53 & 153. At first I permitted all (including the internet) to have access to those ports, but I got scared and changed it to my network only.

I tried all three ip addresses for the WiRNS address bind yet none of them can get access to WiRNS for configuration. I changed the binding address by running the setup program multiple times, using the repair button to force a reboot and request for the new WiRNS address.

Well, I had uninstalled WiRNS as the repair did not work. After reboot I attempted to reinstall WiRNS and received this error message:
Service 'WiRNS.exe' (WiRNS.exe) failed to start. Verify you have sufficient priveledges to start system services.

THat took me by surprise. I restored the system to yesterday's state, opened ports and services on the firewall and added static ips as before. Then I rebooted and reinstalled WiRNS sucessfully.

You appear to have your "WiRNS IP" configured for 192.168.0.111 instead of 192.168.0.107 that you said that you wanted to use. And, it appears that you have your "Primary Web Port" configured for 44 instead of 80...

Henry_________________Here's my Poop (I know that's the old Poopli, but I like it that way!)

From Henry's post: I repaired WiRNS and used 192.168.0.107 as it appears I can use that as long as I have that in my Local Area Connection TCP/IP advanced settings. Regarding TCP 44: once upon a time both WiRNS and DVArchive did work when I still had the dynamic router running. Sooooo....since DVArchive squawked when I attempted to change the port from 80 to something else...I changed WiRNS to use port44...yikes? Seems like I cannot change that now....

So, I added TCP44 to the open port list. No luck yet. After this post I will try a reboot and see if that works.

On to Frank's task:
The ReplayTV got an "invalid response from the name server" when I tried DSN1 at 192.168.0.107 (I have changed WiRNS back to that address per Henry's suggestion) and timed out with DNS1 at 192.168.0.111.

At this time I cannot rotate logs.

Also, just to make sure...all along, I have been leaving the ReplayTV unit (192.168.0.109) in the "download" state for some shows from Poopli. They have been progressing along all this time. Will that affect any of this configuration work?

The point of using multiple IP addresses is so that you can have multiple servers using port 80. The Replays communicate with each other using port 80, so if you want your Replay to "see" DVArchive, then DVArchive has to be on port 80 (not very useful when it's not on port 80). Same for WiRNS. If you only want WiRNS to get stuff from your Replay and be able to give it guide updates and such, then you could leave WiRNS on port 44. However, now that you have WiRNS on its own IP address, there isn't any reason not to configure WiRNS for port 80 so that the Replay can "see" it. If you were going to leave WiRNS on port 44, then there really wouldn't be any reason to give it a separate IP address from DVA since there would no longer be any conflict...

In addition, since nothing is going to communicate with WiRNS on port 44 (except you'd have to use that port number in your browser), there really isn't much point in opening that port number...

As far as LAN configuration, the confusion is that even though you said you wanted to use 192.168.0.107 for WiRNS, you configured WiRNS for 192.168.0.111, so all the instructions were for configuring your network for 192.168.0.111. The correct instructions are that whatever IP address that you configure WiRNS, that's what you should configure as the DNS for your Replay. So, if you change WiRNS to 192.168.0.107, then the correct DNS for your Replay is also 192.168.0.107...

In addition, make sure that DNS2 is either blank or also the WiRNS IP address...

As Frank pointed out, if you want WiRNS to load up a channel guide, you need to configure the Replay in WiRNS to have the provider that you want to use for that Replay. Then when you perform an "Update Guide" it will download the channel guide that you selected..._________________Here's my Poop (I know that's the old Poopli, but I like it that way!)

I had a VERY serious problem with my windows xp os installation! A system restore resulted in an unescapable situation ()!!!!! I had to reinstall the os and all programs. And, most likely it is a user problem !

Currently, DVArchive recognizes my living room rtv and wirns does, too, so that's good news. Certainly progress from the prior situation having WiRNS on port 44!!! once again: .

Now, onto reading how to setup WiRNS to run in conjunction with IVSMagic!

I want to thank you for your help. Utahns say: 'presh8cha! It's pretty funny to hear...

i was going over these threads and decided to try seperate ips even though all was good on my xp comp on just one. with the help of these experts and my slowly inceasing comp savoy(okay!) it only took a few minutes and a restart to get ivsm working on its new ip. thanks guys! the reason why im looking aroung is that on my w7 comp ivsm has stopped again, ill try this there and get back on those threads. ---d