MTNL Broadband: POrt forwarding

[domin8r]

OK, I've been able to setup rules now, by using the static IP as 192.168.1.3. But, still unable to add them to the filters list. I do add the port and IP as told, but the rule does'nt appear below the form, in the Filters section.

 

[baudhayan]

even i need sum help on this topic. im using winxp with norton av & norton internet security. i set up my virtual server 4 d ip 192.168.1.2 (my pc's lan ip). when i enable remote desktop sharing in netmeeting..NIS tells me 2 open sum ports which i have already done. i have also frowarded d requisite ports (1503, 1720, 1731) as told in d portforward.com website. but when i do an ip scan on my public ip from my office i always get d same o/p...even w/o any firewall s/w i get d same output. can any1 guide me with d exact settings.View attachment 296

 

[domin8r]

It seems to work for me, now. Apparently you do'nt need to add them to the filters list. Thanks to the guys here. Cheers!

 

[mk76]

By putting my machine in DMZ I'm on the 'other' side of the firewall. Which means I do not need a port forwarding setup (for any application) at the router.If the above is correct then which is the better approach

 

[max]

the better approach would definitely be using port forwarding. The reason for this is, when you put the router in a DMZ that means the computer is "unprotected" in a sense...While with port forwarding you get the protection of the firewall and at the same time you can use your app

 

[onlygodknows]

Agreed !!! However configuring PC firewall for port forwarding seems much more easier than DSL firewall !!!

 

[max]

hmm...i am sorry but i cant really compare the two. I dont understand how they can be any different?

 

[chicmagnet]

hardware firewalls are better then software firewalls.. but sometimes there are compatibility issues etc etc with hard ware firewalls..like my Asus a8n sli mobo also has a hardware firewall but it has some issues which cause the comp to crash so i dont use it...

 

[max]

yeah. but thats the hardware issue. when you use a feature of the hardware firewall (like port forwarding) you expect it to work. If it doesnt, then the software is at fault...

 

[waterloo_sunset]

Yeah, i agree with Max there. Port forwarding is a better option and easy to configure too. The only thing i haven't managed to get working is the windows time sync thing. Changed time servers and everythin. Still refuses to connect and update the time. Gives that "an error occurred while windows was synchronizing blah blah....." Using the default set-up.....not bridge-mode. Works with dial-up but not with MTNL. Any ideas?