AcidBurn73
join:2007-08-10
Kathleen, GA
1 edit | VPN & Remote Desktop Through A Speedstream 5200
Hello again everyone. It has been a while since I posted here. For the record, my speed problems with Windstream have not gotten much better, but I am at least a little faster speed-wise than I use to be.
My question today actually doesn't involve anything to do with Windstream itself, but the DSL modems that come with the service. When I first got the service, I received a Speedstream 5200 modem to use to connect the DSL. When I first set up the modem, it was a "dummy" modem and did not have the firmware installed on it to allow it to create its own PPPoE connection. Instead, my Linksys router kept my login information in it to create the persistent DSL connection through the "dummy" modem.
During this time without the firmware update, I was able to connect from my home computer to my network at work and use remote desktop to access my work PC. We use the SonicWall SSL-VPN Netextender connection for the VPN connection. Everything worked perfectly.
Back in August, I posted here about the problems I was having with my DSL speeds from Windstream, and I ended up upgrading the firmware on the Speedstream 5200. I now have my Speedstream setup to handle my network DHCP and use the Linksys router as a simple Wireless access point (it does nothing with the DHCP or the DSL connection).
I haven't had to do much remote desktop connecting to my work computer over the last few months, but in the past week or two, the need has come up a few times. Now, when I try to connect through VPN and use remote desktop, the VPN seems to connect fine (I get an IP address and it says I am apart of the domain), but I can't see any computers using their host name or IP. Remote Desktop also no longer works and says that it can not resolve the host name.
Is there something I am missing in setting up the Speedstream router that is blocking VPN, or something I need to check to get it to work?
Thank you in advance for you time and help on this. |
|
evilghost
Premium
join:2003-11-22
Springville, AL
 ·Windstream
| Sounds like you either have a split-tunnel issue or you're local LAN has the same IANA addressing space as your work. I run a 5200 with the current firmware and have never had an issue with IPSEC or PPTP VPN connections. Once you've established the tunnel the tunneled traffic would have no bearing on the type of modem you're using (IE, RDP). |
|
AnonymousOne3
Former Broadband Rep
join:2007-08-04
Salina, KS
| Check the firewall on the 5200, go to 192.168.254.254 and type in admin for both the uname and pass, click on the Setup link on the left side and then click the Firewall link that drops down and then the Level link that drops down. If its on at all, turn it off and then save those settings and try your VPN again. |
|
AcidBurn73
join:2007-08-10
Kathleen, GA
| reply to AcidBurn73
Thanks everyone. I looked at the firewall settings, and the firewall is already turned off. On a hunch, I went to visit some family last night and try to remote on their computer to rule out that it might not be my network at all. When I tried from their house, I got the same error as I did from home (they are on Cox cable modem service). So, it looks like something on the company side that is causing it. |
|
bsc
Premium
join:2003-03-11
Lexington, KY
| I think KJ4AUR might be right. If your VPN is assigning addresses from a network block that is the same as your home DHCP you will have routing problems since your computer will not know which network devices are on.
Is that the case? With a 255.255.255.0 subnet mask, the first three octets of both networks would have to be the same to cause this issue. (I.E. both 192.168.1.x) |
|
AcidBurn73
join:2007-08-10
Kathleen, GA | reply to AcidBurn73
My home network is setup with 192.168.254 for the first three octets. When I connect to VPN, the IP I am issued upon connection uses 192.168.23 for the first three octets. |
|
evilghost
Premium
join:2003-11-22
Springville, AL | reply to AcidBurn73
Could be a WINS/DNS issue, have you tried a PING to the RDP destination host using the IP Address? |
|
AcidBurn73
join:2007-08-10
Kathleen, GA | reply to AcidBurn73
Yep. I first tried to ping the host with the computer name, it came back saying it could not find the host name. I then tried pinging it with the IP address and it said it could not find the host with that IP address. |
|
