Yes I know how to do port forwarding, I use ssh and vnc on a daily bases. Lets just get that straight. So I set up a hack box for myself running server 2003, no service packs and no firewall. I NMap it from another computer on the lan I'm planning on using msrpc exploit. So I assure my self port 135 is open by nmaping the computer. nmap -p135 -sS -P0 192.168.2.6 135/tcp open msrpc I'm setting up a perfect network and unrealistic one lol but perfect. So I forward port 135 on my router UDP and TCP. Yet when I run nmap from my work computer I get. nmap -p135 -sS -P0 24.151.115.x 135/tcp filtered msrpc Does anyone have any ideas? I rebooted the router also just to be on the safe side lol.
Well In researching this some guy wanted to use this technique to authenticate users at a satellite office using port 135 for active directory. Port 135 will only respond if you are on the same subnet. So I plugged it straight into my modem got an ip off. 24.151.10.x 255.255.248.0 Went to my friends house his IP was in the same subnet and I was able to nmap the port and it was open. My next question requires a little of a setup. the server is 192.168.2.3 and the router is 192.168.2.1. So if you forward the port and try to connect to it wont the request look like it is coming from 192.168.2.1? Which is on the same subnet. Last question is on my logs for my router at work I see port scan attempts from 192.168.x.x and our range is 10.10.10.x. How do people spoof internal IP's to do an attack?
Try to use linux with port forwarding, Ubuntu will work best. Just install webmin and then there you go, configure it and presto!
