02-04-2010 06:44 PM
Hello - I have recently had a WRVS4400N installed between my home network and Comcast modem as a requirement for a home control system. I have used many modems and routers in the past, and never had trouble configuring it to allow remote desktop access to and from the local PC. Nothing I do with this router, though, seems to work. Even simple things do not work. I can use the router's Diagnostic page to ping common sites (like Google) and it works fine. Trying the same from the command prompt on the local PC receives no response. Tried shutting off the firewall in the router and no help. Running W7 with McAfee, and turning off the PC firewall in McAfee also does not help. Have reviewed the manual extensively and have also come up with a blank. Can someone tell me what I am missing? Thanks in advance.
02-04-2010 10:08 PM
Hi dschanin1
1. The easiest thing to first check is that you are at the current software level. If you have a hardware version 2 WRVS4400N, the software version you should verify you have or install version 2.0.0.8 of the wireless routers firmware. You will find mention of the version of hardware on a label underneath the WRVS4400N.
2. Personally, I feel like I would like to reset the router to factory defaults and try web access again.
Then rebuild the customized options you want such as the remote desktop connection
3. I'm also guess for remote desktop support you are forwarding TCP port 3389 to the appropriate LAN IP address ?
regards Dave
02-05-2010 08:58 AM
Thanks for the reply. The router was at 2.0.0.7 so I upgraded to .8 with no change in behavior. Why would I not be able to ping from behind the router, yet the Diagnostic page ping works? This is the case even if I turn off all the firewall and blocking mechanisms in both the router and the PC. Thanks.
02-05-2010 09:35 AM
Hi dschanin1
Go back to the most current code version on the router and then reset the WRVS4400N to factory defaults.
I'm guessing that DHCP is working in your PC and you get all the IP information your PC needs to get onto the internet.
step 1 Maybe paste the results for the following command done via the command line, "ipconfig /all"
step 2. OK turn off or diable your wireless NIC on your PC
step 3. from the command line on your PC ping the router LAN IP address (192.168.1.1), from your PC ?
step 4. from the command line on your PC can you ping 4.2.2.1 ?
step 5 from the command line on your PC can you "ping www.msn.com"
Manually configure the copper Ethernet interface on your Win 7 PC.
Doing this for diagnostic reasons, maybe statically define your;
1. IP address, maybe 192.168.1.111
2. subnet mask, 255.255.255.0
3. gateway address and 192.168.1.1
4. DNS information on your PC. you have to figure this one out, but 4.2.2.1 may work for you
let us know what happens to this point.
regards Dave
02-05-2010 04:32 PM
Thanks again for the response. Here are the results of the tests you asked me to run:
STEP 1:
This is the result of the command line entry:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Windows IP Configuration
Host Name . . . . . . . . . . . . : DavidsPC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.co.comcast.net.
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Win32 Adapter V9
Physical Address. . . . . . . . . : 00-FF-66-F6-1D-67
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Local Area Connection:
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controller
Physical Address. . . . . . . . . : 00-1E-C9-52-12-A5
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::8164:bd05:7e30:23d0%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.109(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, February 05, 2010 10:31:47 AM
Lease Expires . . . . . . . . . . : Saturday, February 06, 2010 10:31:47 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 234888905
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-A7-77-5F-00-1E-C9-52-12-A5
68.87.69.150
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.hsd1.co.comcast.net.:
Connection-specific DNS Suffix . : hsd1.co.comcast.net.
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 9:
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e74:14fc:3013:3f57:fe92(Preferred)
Link-local IPv6 Address . . . . . : fe80::14fc:3013:3f57:fe92%13(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.{66F61D67-763A-4901-9B63-839CCB5702B6}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
02-06-2010 10:20 AM
Can you try changing the your router default ip address to something other than 192.168.1.x and do these test again and let me know how this works. i have had similar issue's and changing default ip address worked.
Thanks,
Jason
02-06-2010 11:25 AM
Hi dschanin1
Does a XP computer or an older computer work on that network, I would think the answer yes. try it.
Interesting task that was posed to you by Jason.
Does altering the LAN IP address of the WRVS4400N from 192.168.1.X to another value fix the problem ?
If that fixes your problem great..problem solved :) , do not bother read on
I think if your XP does work on this network, there is no reason for the WIN7 box not to work. Unless some other than some service restriction application is on the Win7 machine.
Obviously the proof would be to capture the Ethernet frame interaction from the WIN7 PC and the WRVS4400N, as the WIN 7 PC tries to access the Internet.
It would be most interesting to monitor the Ethernet traffic via a free downloadable application called 'wireshark'.
There is also a most useful option on the WRVS4400N via the tab L2 Switch > port mirroring to copy or mirror the traffic going to and from the WIN7 PC to another PC.
Port mirroring can be used in this exact situation to monitor traffic coming and and out of the Win7 PC.
If you have the patience, and it is a interesting task to try, and skill to learn;
1. Would you please setup the port mirroring to copy or mirror Ethernet frames from the WIN7 PC to a XP PC ( running wireshark).
2 figure out how to use wireshark to capture traffic
and capture some pings from the WIN7 PC to the Internet.Post the capture.
But, if you wish to go through problem determination with our Small Business TAC folks, you could call the support folks on North America: 1 866 606 1866.
regards Dave
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide