JamesLevinworth
@embarqhsd.net | reply to JamesLevinworth
Re: VPN Connection
btw, after testing turn back on the windows firewalls. I'll await your results. |
|
fms007
join:2009-05-24
| Sorry to keep you waiting for such a long time....had to do it carefully
Windows firewall disabled on Client Only
69.96.3.123 (not working) Dynamic IP
69.96.3.123:54120 (not working) Dynamic IP:port
192.168.1.2:54120 (working) LAN IP:port
Windows firewall disabled on Server Only
69.96.3.123 (not working) Dynamic IP
69.96.3.123:54120 (not working) Dynamic IP:port
192.168.1.2:54120 (working) LAN IP:port
Windows firewall disabled on Server and Client both
69.96.3.123 (not working) Dynamic IP
69.96.3.123:54120 (not working) Dynamic IP:port
192.168.1.2:54120 (working) LAN IP:port |
|
fms007
join:2009-05-24 | In other words only LAN IP:Port works for all 3 cases with client firewall off only, Server firewall off only, both client and server firewall off
The WAN IP doesnt work at all...neither in 69.96.3.123 nor in 69.96.3.123:54120 |
|
fms007
join:2009-05-24
1 edit | Just wondering...could it be the router is the cause of all this....like something to do with the NAT of the router enabled status.....or the DMZ enabled status.....or DHCP server enabled status.....
Will it help if i carry out a ping test |
|
JamesLevinworth
@embarqhsd.net
| said by fms007  :Just wondering...could it be the router is the cause of all this....like something to do with the NAT of the router enabled status.....or the DMZ enabled status.....or DHCP server enabled status..... Will it help if i carry out a ping test that's why we are doing these tests (most of them) to verify what I believe should be working (and is) to narrow it down to either your router, or the routing you have going on with the bridge. We really are trying to dork this up without proper routing equipment (nudge nudge). Also some of these lower end dlinks are flaky with not allowing some services on at the same time as others, or random ports, or just random oddities.
I was going to tell you to delete that PPTP you setup previous (you can redo that later) ... and still am, but now that you say you have dmz on, YES turn that OFF. Where was it pointing to? Also, your lan is static, so no need for DHCP in the LAN. Anything else I should know? |
|
JamesLevinworth
@embarqhsd.net | When I ask anything else, I mean custom you've added or changed.
You need NAT on. |
|
JamesLevinworth
@embarqhsd.net | Could you do these commands, pls., and paste them here.
From SERVER and CLIENT both do:
pathping 69.96.3.123 >pping.txt
(and)
route print >pr.txt |
|
fms007
join:2009-05-24
| reply to JamesLevinworth
PPTP is not setup bcos i had it setup when i wrote my first post...the moment i got ur first response....i loaded my modem settings to what i had before i started port forwarding of RDP...meaning to a more pristine state before any port forwarding.... and i started everything from scratch...i even restored my windows image to a date before i started with rdp, changes of registry etc, so it was all brand new...meaning clean image
DMZ was on and pointing to 192.168.1.2....
before these posts DMZ used to be ON and pointing to 192.168.1.4 (Client Internet IP)....
I had tried to put if off before our posts but it used to give problem...meaning couldnt get Client webpages to load on....anyhow now will put it off...reboot modem and check if everything is okay.
Same goes for DHCP which knowing that i had static ip..i have tried putting off but use to get the same problems with loading of pages..and this was even for SERVER...
What i will do now is put DMZ off...reboot modem (switch off/on) and check if everything is fine than try the same for DHCP and will get back to you in a few moments
Also have a page in the modem where one has to mention the LAN Clients....here it is mentioned Static IP 192.168.1.2.....if this is not setup here in the LAN client page i cant do port forwarding for a specific IP...meaning i would not be able to do port forwarding for 192.168.1.2 for RDP
With respect to the same...do i have to add in the LAN client page the static IP 192.168.1.4 for the client? |
|
JamesLevinworth
@embarqhsd.net
| Clean is a good state... good thinking.
You definately want that DMZ turned off, especially not pointed at SERVER. Not to get off topic, but if you still are having problems loading webpages, that's more likely a dns issue. You could change your DNS servers to something else, like OpenDNS 208.67.222.222, 208.67.220.220. Just leave DMZ closed until you research what it does.
Delete the 192.168.1.2 client and then re-add it (and the port forwarding rule too) so it's clean.
Add 192.168.1.4 as a client too. You do not need to add port forward for 1.4 (You are coming from CLIENT, so you only need an open port to get in through the router (and xp firewall too) into SERVER)
Run a quick test off WAN-RDP with port from CLIENT to SERVER when you are done. Thx. |
|
fms007
join:2009-05-24
| reply to fms007
From Server....pathping 69.96.3.123 >pping.txt
Tracing route to 69.96.3.123 over a maximum of 30 hops
0 SERVER [192.168.1.2]
1 69.96.3.123
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 SERVER [192.168.1.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 69.96.3.123
Trace complete.
From Client....pathping 69.96.3.123 >pping.txt
Tracing route to 69.96.3.123 over a maximum of 30 hops
0 CLIENT [192.168.1.4]
1 69.96.3.123
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 CLIENT [192.168.1.4]
0/ 100 = 0% |
1 17ms 0/ 100 = 0% 0/ 100 = 0% 69.96.3.123
Trace complete.
From Server....route print >pr.txt
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...02 1c c0 18 bb af ...... MAC Bridge Miniport - Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.2 30
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.2 192.168.1.2 30
192.168.1.2 255.255.255.255 127.0.0.1 127.0.0.1 30
192.168.1.255 255.255.255.255 192.168.1.2 192.168.1.2 30
224.0.0.0 240.0.0.0 192.168.1.2 192.168.1.2 30
255.255.255.255 255.255.255.255 192.168.1.2 192.168.1.2 1
Default Gateway: 192.168.1.1
===========================================================================
Persistent Routes:
None
From Client....route print >pr.txt
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...02 05 5d 41 f8 94 ...... MAC Bridge Miniport - Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.4 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.4 192.168.1.4 20
192.168.1.4 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.4 192.168.1.4 20
224.0.0.0 240.0.0.0 192.168.1.4 192.168.1.4 20
255.255.255.255 255.255.255.255 192.168.1.4 192.168.1.4 1
Default Gateway: 192.168.1.1
===========================================================================
Persistent Routes:
None
Have copied and pasted in the post but it doesnt come properly...so i have added the
pathping 69.96.3.123 >pping.txt (Server and Client)
route print >pr.txt (Server and Client)
as attachments in notepads. |
|
fms007
join:2009-05-24
| reply to JamesLevinworth
quote:
You definately want that DMZ turned off, especially not pointed at SERVER. Not to get off topic, but if you still are having problems loading webpages, that's more likely a dns issue. You could change your DNS servers to something else, like OpenDNS 208.67.222.222, 208.67.220.220. Just leave DMZ closed until you research what it does.
Delete the 192.168.1.2 client and then re-add it (and the port forwarding rule too) so it's clean.
Add 192.168.1.4 as a client too. You do not need to add port forward for 1.4 (You are coming from CLIENT, so you only need an open port to get in through the router (and xp firewall too) into SERVER)
Run a quick test off WAN-RDP with port from CLIENT to SERVER when you are done. Thx.
Will carry out as you said and get back to you.thnxs |
|
fms007
join:2009-05-24
| okay
(1.)Have DMZ OFF
(2.)DHCP OFF
(3.)Deleted LAN Client 192.168.1.2
(4.)Rebooted modem...and setup LAN client 192.168.1.2
(5.)Port forwarded on router port 54120 for RDP for 192.168.1.2
(6.)Added LAN client 192.168.1.4....not forwarded any port here
Will test RDP and get back in a few moments |
|
fms007
join:2009-05-24
| reply to JamesLevinworth
hi
Ran a test on RDP and the results are the same as before
*With SERVER firewall disabled only
*With CLIENT firewall disabled only
*Both Disabled
WANIP:port.........not connecting
WANIP...............not connecting
LANIP:port.........connecting |
|
JamesLevinworth
@embarqhsd.net
| reply to fms007
said by fms007 :In other words only LAN IP:Port works for all 3 cases with client firewall off only, Server firewall off only, both client and server firewall off The WAN IP doesnt work at all...neither in 69.96.3.123 nor in 69.96.3.123:54120 Just for fyi - With this, we verified that everything (firewall, port#) is working as it should, just WANip isn't. Also, the routing between client and server is working for both sides of the bridge where RDP is concerned. |
|
JamesLevinworth
@embarqhsd.net
| reply to fms007
said by fms007 :hi Ran a test on RDP and the results are the same as before *With SERVER firewall disabled only *With CLIENT firewall disabled only *Both Disabled WANIP:port.........not connecting WANIP...............not connecting LANIP:port.........connecting Ok, you can leave the firewalls on now. They are working right. It's just getting to the WAN IP:port.
Your tests before looked normal, btw. |
|
fms007
join:2009-05-24
| reply to JamesLevinworth
quote:
When I ask anything else, I mean custom you've added or changed.
You need NAT on.
NAT is enabled.
Do you want me to attach some of the main pages of my modem settings...so you get a picture of how the modem is configured.
*In the modem the DNS server nos is set to User Defined and match with the DNS servers which i have put in the network adapter card settings.
No problem with the browsing from Server or Client.
In the modem page there is a WAN page where it is mentioned
IP Control:Dynamic (this was set from the beginning i think...bcos i dont remember changing this) |
|
JamesLevinworth
@embarqhsd.net
| said by fms007 : Do you want me to attach some of the main pages of my modem settings...so you get a picture of how the modem is configured. yes, good idea.
said by fms007 : In the modem page there is a WAN page where it is mentioned IP Control:Dynamic (this was set from the beginning i think...bcos i dont remember changing this) This is fine. This tells the router how to get your dynamic WAN IP assigned from the ISP.
While we are talking about sw firewalls... Can you verify outpost firewall is definitely off? Sometimes these firewalls continue to run in the background from a service even when you disable things. Check administrative tools-> services and see if it runs as a service, and it's in started state. Just checking, just in case. It's dumb stuff like this that always happens and easily missed via posting online like this... |
|
fms007
join:2009-05-24
| quote:
While we are talking about sw firewalls... Can you verify outpost firewall is definitely off? Sometimes these firewalls continue to run in the background from a service even when you disable things. Check administrative tools-> services and see if it runs as a service, and it's in started state.
Yes the outpost firewall is off..checked it thru services.msc
I have Avast Antivirus Pro installed..but had put this off also when i started with the rdp project....it doesnt start when windows starts, but some of the processes of avast are running in the background..this i have noticed in the taskbar manager....thru services.msc i tried to disable avast completely but it is not possible to disable as access is denied....the only way is to uninstall it.
Will try to take snapshots of modem page and attach it here. |
|
fms007
join:2009-05-24
| reply to JamesLevinworth
Have been trying to load the modem settings page on the webrowser for the past 15-20mins but it doesnt open....even have switched off/on modem a couple of times....the login page opens....can put username and password....opens the Home (initial page) but beyond that it will not open....if i click on any of the tabs in the home page it will not open(load).....will keep tryg though |
|
JamesLevinworth
@embarqhsd.net
| said by fms007 :Have been trying to load the modem settings page on the webrowser for the past 15-20mins but it doesnt open....even have switched off/on modem a couple of times....the login page opens....can put username and password....opens the Home (initial page) but beyond that it will not open....if i click on any of the tabs in the home page it will not open(load).....will keep tryg though Hmmm. sounds as tired as we both probably are.
When it isn't loading, try pinging the router 192.168.1.1 and see if it's being flaky. Also, try clearning your browser cache and/or rebooting. |
|
