| View previous topic :: View next topic |
| Author |
Message |
tommybcool
Joined: 01 Sep 2006
Posts: 141
Location: Kansas
|
 Posted: Thu Mar 01, 2007 9:48 pm Post subject: |
 |
|
If you are using SMP. You put in the UMS's IP address (your WAN static IP), and down below, check mark the Live Source Alias, and type in the name of the alias.
If you check marked Live source IP and ID and put 127.0.0.1 in as the IP that will not work from the outside world. Just guessing since you made no mention of changing anything about the live source parameter in SMP.
So in SMP put in the WAN IP of the server, check mark Live Source Alias and type in the alias of the source and it should work I think. (if your ducks are in a row as we say in Kansas).
Also remember port 5120 needs to be forwarded to the PC's lan IP so Liveserver can listen for UMS requests. So 5119 and 5120 need to be opened and aimed at x.34. |
|
| Back to top |
|
 |
tommybcool
Joined: 01 Sep 2006
Posts: 141
Location: Kansas
|
| Posted: Thu Mar 01, 2007 10:01 pm Post subject: |
|
|
| tommybcool wrote: |
Also remember port 5120 needs to be forwarded to the PC's lan IP so Liveserver can listen for UMS requests. So 5119 and 5120 need to be opened and aimed at x.34. |
Of course you don't need the 5120 forwarding if live server is not accessed from another outside media server though. |
|
| Back to top |
|
|
DeniseDD
Joined: 10 Dec 2006
Posts: 12
|
| Posted: Thu Mar 01, 2007 11:57 pm Post subject: |
|
|
All three ports have been forwarded by NAT pointing to the current LAN IP, that has been secured in Windows. The Zyxel firewall is Off.
Maybe an easier example to tackle this networking mystery:
If I use U-Broadcast (another cam program) to broadcast on port 8080, add port 8080 to NAT and forward to LAN IP, then it doesn't work either. Not even with the software firewall off. |
|
| Back to top |
|
|
tommybcool
Joined: 01 Sep 2006
Posts: 141
Location: Kansas
|
| Posted: Fri Mar 02, 2007 1:52 am Post subject: |
|
|
| DeniseDD wrote: | All three ports have been forwarded by NAT pointing to the current LAN IP, that has been secured in Windows. The Zyxel firewall is Off.
Maybe an easier example to tackle this networking mystery:
If I use U-Broadcast (another cam program) to broadcast on port 8080, add port 8080 to NAT and forward to LAN IP, then it doesn't work either. Not even with the software firewall off. |
So the internet works, your lan works, UMS works locally but not from the outside in (which indicates there is nothing wrong with Mr and Mrs. Server), other software will not get through the router's firewall although given the port opening to do so, you've corrected the misdirected port forwarding after finding the lan IP of the server PC had changed (thought we had it there-darn!).
This is looking like there's something wrong with the Zycel maybe? I've never seen a router loose just it's port forwarding capability. http://www.hoverdesk.net/freeware.htm Try this utility HoverIP just below Regseeker which is also excellent. It's got a lot of uses, but it's also got a port scanner. Run it in a selected range like 5000 to 5200 and see if it finds open ports.
At this point it sounds like you've done all you can do to me. Maybe someone else has an idea. I would find the reset button if there is one on the modem and start fresh, but I'd call the ISP support first to make sure there are no hidden passwords that get reset on the modem. Reseting the modem/router all of the forwarding will be wiped out and you'll have to re-enter the ports (which isn't that big of a deal).
I just hope it's not something simple we are overlooking. |
|
| Back to top |
|
|
DeniseDD
Joined: 10 Dec 2006
Posts: 12
|
| Posted: Fri Mar 02, 2007 8:08 am Post subject: |
|
|
Update: I decided to reboot both Windows and the Zyxel itself, and everything works flawlessly now. Except for the modem, it still has timeouts in terms of setting it up. So the final solution to this I'll be calling:
- cmd > ipconfig /all
- use that LAN IP in Windows to prevent further switching
- use that LAN IP for the NAT forwarding
- forward 5119/5120/5130
- put the WAN IP in Mediaserver
- have a decent soft firewall
Thank you very much for your nice assistance. |
|
| Back to top |
|
|
tommybcool
Joined: 01 Sep 2006
Posts: 141
Location: Kansas
|
| Posted: Fri Mar 02, 2007 2:33 pm Post subject: |
|
|
| DeniseDD wrote: | Update: I decided to reboot both Windows and the Zyxel itself, and everything works flawlessly now. Except for the modem, it still has timeouts in terms of setting it up. So the final solution to this I'll be calling:
- cmd > ipconfig /all
- use that LAN IP in Windows to prevent further switching
- use that LAN IP for the NAT forwarding
- forward 5119/5120/5130
- put the WAN IP in Mediaserver
- have a decent soft firewall
Thank you very much for your nice assistance. |
As I said, I hope it's not something simple we are overlooking. It's a good PC adage,'when in doubt, reboot'. Sure is gratifying when things get back to normal isn't it?
When you say 'use that LAN IP in Windows to prevent further switching' I assume you mean use that IP in the static settings of the internet protocol TCP/IP properties of the network adapter. You don't have to use that one, it can be any number between 1 and 253 for the last number. Just make sure the router forwards to that same number. Also a soft firewall is not normally needed with a router, but it can't hurt. It's more for folks without a router.
It is good you have a static WAN IP or the power outage could have caused that to change also. That is why DynDNS is so valuable to folks that don't have a static IP. It works the same as. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
