Msn Webcam Port
Nov 27th, 2004Thanks, Barry
I have seen this question posted many places, but no answers. I am running a Linksys router that uses NAT. I can use all features of MSN Messenger 6.2 with no problem, but my mic and webcam will not work. If I disconnect the router, connect my computer straight to the modem, everything works fine. What a nuisance telling my friends to wait while I change a cable over, reboot, and then I can video conf. with them, not to mention if my kids on the net on the other computer he's now out of luck. Has anyone solved this one yet, or is Microsoft still working on it?
Thanks, Barry
Hi Moghrabi
I've read the instructions you provided but not had much joy. I've a Linksys WAG54G (UK model) and a Linksys Wireless-G Internet Video Camera, given to me for services provided to Cisco! The console is different for the WAG with Port Range Forwarding hidden under the tab Gaming and Applications. I've added the details you provided there but no detection of the cam. I also tried the instructions for Yahoo provided by Linksys and had similar disappointment. These were to add a range of 5100-5100 under Port Triggering with both protocols selected.
Any help would be much appreciated!
Hi Moghrabi
Still scratching my head here! I think that where I'm going wrong is the IP settings - I'm not sure what to add. I've 5 static IPs allocated by my ISP starting at 192.168.1.50 and using I'm using DCHP. There's 2 PCs connected: a home one and a standard issue Cisco laptop (which I can VPN into work with) and then there's the cam. My home PC can see the cam on the network, the Cisco box can't see it even when I'm not on VPN. I've tried MSN and Yahoo on both.
I also followed some Linksys instructions stating that the cam needs a port specifying too at 1024 on TCP, which I've done (--). The cam is on 192.168.1.52. and I set that as per the Linksys instructions in Port Range Forwarding to this IP rather than 115 as the default.
I'm wondering what I need to set the Port Range Forwarding to for MSN, should this be 192.168.1.2 as you suggested, or to the allocated IPs from the DHCP?
As you may have guessed I'm from the non-techie part of IT...all these IPs configurations are very confusing to me