Jump to content
|Topic||Stats||Last action by|
|PlayStation Plus Instant Game Collection: May 2014||
|5 stages of a malware attack||
|The Big Wrestling Thread!||
|New PS4 update to add SHARE enhancements and HDCP Off||
Posted 04 January 2013 - 05:31
Posted 04 January 2013 - 13:10
Posted 04 January 2013 - 16:54
What is the device in front of your new router? You sure its not doing NAT?
Sorry if i dont understand but out setup is modem->ebr-2310->dell gigabit switch. I have setup the uplink from router to switch but all computers are plugged into the gigabitswitch
Might of worked before because the IP address of the other routers wan was placed into the dmz? Maybe it was setup static - and this new one you just plugged it in, etc. I dont understand the first part about being placed into the dmz? Before it was not setup static as sometimes i would need to relogin to the router and change the ip of the computer that the ports were forwarded for, i think thats what you were asking.
Verify that your new router actually has a PUBLIC IP on its wan (internet) interface -- something other than 10.x.x.x, 192.168.x.x, 172.16-31.x.x and then give the details of what your doing with screen shots and your host listing on the port.. You being able to connect to said port from other local devices, no firewall setup on the device your trying to forward too, etc. Forgive my ignorance how would i go about checking this?
Posted 04 January 2013 - 20:03
Posted 04 January 2013 - 20:22
Posted 04 January 2013 - 21:03
C:\>netstat -an | findstr 42312 TCP 0.0.0.0:42312 0.0.0.0:0 LISTENING TCP 192.168.1.8:42312 xx:1526 TIME_WAIT TCP 192.168.1.8:42312 xx:13288 TIME_WAIT TCP 192.168.1.8:42312 xx:57388 TIME_WAIT TCP 192.168.1.8:42312 xx:57759 TIME_WAIT <snipped out all the other listed time_waits> TCP [::]:42312 [::]:0 LISTENING UDP 0.0.0.0:42312 *:* UDP [::]:42312 *:*
Posted 04 January 2013 - 22:31