me and two friends have linksys routers. So i put myself on port forwaring one port, and set that as the file transfer port on Aol instant messager. So my other friends do the same and it doesnt work . Now we can send to other people who aren't on routers. And normally we cant. So then we put ourselves all as the DMZ hosts, and it works fine even linksys router to linksys router. So for some reason i think that we cant send to people on routers with just port forwarding, and need to use DMZ (we all had linksys, but i figure some network thing would prevent us from sending to netgear, and other brands) Can anyone explain why? AIM's help files say the default file transfer port is 5190 , but we changed it to the port being forwarded btw.
what is the diffference between DMZ and port forwarding.... concerning linksys routers
- Thread starter hans007
- Start date
DZM host stands for 'dematerialized zone host' in layman's terms this means that whatever computer that you set for the DZM is going to get all of the trafic to whatever your IP address is. It would be just like if you computer was hooked up to the cable modem/dsl directly. Port forwarding only forwards the certain ports that you specify. I think that the reason that It doesnt work would be that the port 5190 might be the port to send stuff, but there is probably a port to receive files and if this isn't open, you cant receive files. The reason that DZM made this work, is because DZM basicly opened all the ports.
Post if you need any more help, I'd be happy to answer them as I'm sure most of the board would be too.
Hope this helps,
Mike
Post if you need any more help, I'd be happy to answer them as I'm sure most of the board would be too.
Hope this helps,
Mike
- Oct 25, 1999
- 29,527
- 415
- 126
Port number is port number, it does not make a difference which Router is used.
The difference between Routers is in the amount of Ports that they let you open.
Usually when the Router manufacture upgrades the firmware, they add ports.
E.g. the last upgrade of The SMC Barricade brings the port count to 30.
For list of Ports, look here:
Special Application Port List
The difference between Routers is in the amount of Ports that they let you open.
Usually when the Router manufacture upgrades the firmware, they add ports.
E.g. the last upgrade of The SMC Barricade brings the port count to 30.
For list of Ports, look here:
Special Application Port List
<< DZM host stands for 'dematerialized zone host' >>
Close but its DMZ and it actually stands for Demilitarized Zone. The DMZ sits between the Internet and an internal network's line of defense. So by puting your computer in the DMZ you are puting it in front of your router and its firewall protection.
Port forwarding allows you to leave your computer(s) behind the router and open up only the ports you want accessible from the internet. Your router will forward the information coming in to the computer you designated to receive the info.
If you are trying to ftp try forwarding two ports such as 20 & 21 for send and receive.
Can't resist....It's DMZ not DZM, and it stands for DeMilitarized Zone (from Korea) formerly known as the "No-Mans Land" between two entrenched armies (WWI).
In this case, it refers to the area of the Internet that is (physically) on your network, yet it is outside your firewalls.
--Woodie
In this case, it refers to the area of the Internet that is (physically) on your network, yet it is outside your firewalls.
--Woodie
Generally a DMZ does NOT bypass firewall rules and does NOT allow all packets to get to it. Typical design is to have a DMZ with true public IP addresses protected by a firewall. This firewall says what can come in and what can go out, drop/reject all else. Firewall also permits special applications from an internal network but not from an external. Hence the term DMZ.
Now the above is for devices called firewalls. What you have is a NAT device and by placing a host in the "DMZ" you are saying "send all packets not associated with an existing NAT coversation to this host" effectively bypassing any security you may have.
A lot of applications like instant messengers, FTP, H.323, and SQLnet negotiate port numbers during the session setup at layers 5/7 and don't work behind NAT unless the NAT device can inspect these higher layer protocols and make the necessary adjustments. By setting your router to place this host in the "DMZ" you don't need to worry about the NAT problems because the router blindly forwards the frames to the host irregardless or any negotiated port numbers.
In networking terms what you are really doing is called a "static NAT". Forward all frames to 24.24.24.24 to 192.168.0.1. This is by definition a NAT and really isn't a DMZ.
longwinded, but hope this helps clear up some of the misconceptions of DMZ.
Now the above is for devices called firewalls. What you have is a NAT device and by placing a host in the "DMZ" you are saying "send all packets not associated with an existing NAT coversation to this host" effectively bypassing any security you may have.
A lot of applications like instant messengers, FTP, H.323, and SQLnet negotiate port numbers during the session setup at layers 5/7 and don't work behind NAT unless the NAT device can inspect these higher layer protocols and make the necessary adjustments. By setting your router to place this host in the "DMZ" you don't need to worry about the NAT problems because the router blindly forwards the frames to the host irregardless or any negotiated port numbers.
In networking terms what you are really doing is called a "static NAT". Forward all frames to 24.24.24.24 to 192.168.0.1. This is by definition a NAT and really isn't a DMZ.
longwinded, but hope this helps clear up some of the misconceptions of DMZ.
well, I got the dematerialized part right.
And I explained it right, for the most part. Hey 2 for 3 ain't bad
And I explained it right, for the most part. Hey 2 for 3 ain't bad
Strych9 types faster than me
To expand on spidey's comments: A DMZ is generally defined by two firewalls--one on the Internet side (front-end), which only allows certain stuff through, and one on the private network side (back-end), which only allows certain different stuff through.
In the home router situation, (as spidey explained) the DMZ is created by a single device, by logically putting the single device in front of the NAT FW, rather than behind it, thus you lose all FW-type protection for that device, since the NATing stuff no longer applies.
I won't get into the FW vs. NAT discussion.
--Woodie
To expand on spidey's comments: A DMZ is generally defined by two firewalls--one on the Internet side (front-end), which only allows certain stuff through, and one on the private network side (back-end), which only allows certain different stuff through.
In the home router situation, (as spidey explained) the DMZ is created by a single device, by logically putting the single device in front of the NAT FW, rather than behind it, thus you lose all FW-type protection for that device, since the NATing stuff no longer applies.
I won't get into the FW vs. NAT discussion.
--Woodie
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 24K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 19K
-
-
-
Facebook
Twitter