Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1709
  • Last Modified:

WinXP to Linksys BEFVP41 V 2 Connection

Hello!  Please help me, oh wise experts!

I am trying to set up a simple VPN from my home computer, connected directly to the modem (Cebridge cable) and my office router – a Linksys BEFVP41 v. 2.  This should be fairly straightforward, but so far, I keep getting:

“Error 800: Unable to establish the VPN connection.  The VPN server may be unreachable, or security parameters may not be configured for this connection.”

I have forwarded Ports 1723, 500, 50, 47, and 49 to a fixed IP address I have on the Windows Server 2003 computer (standard late model computer).

The IP address on the work router is static – provided by the ISP (Sprint DSL).  I suppose that I could have an incorrect login, but the connection does not even seem to get that far.

I have changed local security parameters in accordance with Linksys guidelines, but I wonder if that’s even necessary for a simple WinXP to BEFVP41 connection.

I am using the Windows Connection Wizard to create the VPN connection.

If anyone wants they can log into my router and check configuration.  Please let me know.  Thanks!

Best Regards,
Ixman
0
ixmaninc
Asked:
ixmaninc
  • 20
  • 20
  • 6
  • +1
1 Solution
 
Jay_Jay70Commented:
Hi ixmaninc,

You might also need to configure your router for PPTP Passthrough.   does your linksys book talk about passthrough?

Cheers!
0
 
dlonganCommented:
ixmaninc

are you using rrras on the 2003 server?  or are you trying to use ipsec to the linksys?
0
 
DawilliamsCommented:
If you are trying to use a pptp tunnel to another machine ie 2003 server the linksys will not do that you need to terminate the tunnel at the router ports 47-49 wont do anything for you , I think you may be confusing them with the protocol gre. I would check the log to see where the tunnel fails. report back your findings and we can go from there.
0
Who's Defending Your Organization from Threats?

Protecting against advanced threats requires an IT dream team – a well-oiled machine of people and solutions working together to defend your organization. Download our resource kit today to learn more about the tools you need to build you IT Dream Team!

 
DawilliamsCommented:
Also you will need to use the vpn client that came with the router an xp vpn connection to the router wont work because there two very different levels of security.
0
 
ixmanincAuthor Commented:
Thanks, all!

1) Right now, my router is configured for Static IP, and as such I do not think I can set it to PPTP?  Or, is that a different issue?

2 + 3) Right now I am trying to use a simple connection from WinXP, in the VPN connection wizard, to the router, with a fixed IP address, and its ports forwarded.  Ironically, this worked fine with my previous router - a WRT54G.  I guess things are a little more sophisticated with the BEFVP41 v. 2?

Thanks
ixmaninc
0
 
dlonganCommented:
The linksys supports pptp passthrough (but there is some known issues with early models, have had to downgrade firmware to get pptp to work), there is no reason why you can't use  pptp with 2003.  I have set this up many times.

The following is from Linksys:

You’ll need to setup Port Forwarding to set up a PPtP tunnel behind a Linksys router.  Please follow these instructions to setup the router to forwarding incoming PPtP traffic to your PPtP server:

Getting Started
1.      You must set a static IP address on the server.  If you're unsure of how to do this please go to our Answer ID 534 for information on setting a static IP address in Windows.

2.      Once the static IP address has been assigned please go to your desktop and double click on Internet Explorer (Located on the Start Menu in Windows XP)

3.       Once "Internet Explorer" opens, please type http://192.168.1.1into the "Address Bar" and click GO

4.      The "Enter Network Password" window will appear.  Skip user name and type admin (admin is the default password) as the password, and click OK.

5.      This will bring up the routers "Setup" section.  Look under "Domain Name" and check what version of the firmware you're using.

6.      You will need to click on the Advanced tab to the very right.  Once the "Advanced" tab comes up please go to the Forwarding tab.

Firmware prior to 1.32
This will not work with firmware prior to 1.32

Firmware between 1.32 and 1.36
Service Port Range
47 ~ 47

1723 ~ 1723
 IP Address
192.168.1.3

192.168.1.3
 
Firmware after 1.36 up to 1.40m
Service Port Range
47 ~ 47

1723 ~ 1723
 Protocol
Both

Both
 IP Address
192.168.1.3

192.168.1.3
 
Firmware after 1.40m
Customized Application
VPN

VPN
 Service Port Range
47 ~ 47

1723 ~ 1723
 Protocol
Both

Both
 IP Address
192.168.1.3

192.168.1.3

Finishing up
Click Apply, then Continue.
0
 
dlonganCommented:
You will want the router to have a static IP, PPTP is a tunneling protocol used to create the "virtual private network"
0
 
ixmanincAuthor Commented:
Damn!  You guys are fast.  I'll get to work....
0
 
DawilliamsCommented:
dlongan:  my mistake I misunderstood his intented setup
0
 
ixmanincAuthor Commented:
00:00:00 [192.168.1.1] : System is ready
00:00:00 System is warm start
00:00:00 00xx@sys Firmware Version : 1.01.04, Jan 18 2005
00:00:00 Internet(static) IP is 67.76.236.71
00:00:00 UDP from 192.168.1.107:5061 to 69.59.240.83:5061
2006-04-05 07:10:13 Get current time from NTP server : Apr. 05 2006 Wed. 7:10:13
2006-04-05 07:10:13 TCP from 192.168.1.113:1032 to 66.161.11.28:13
2006-04-05 07:10:14 TCP from 65.54.194.118:80 to 67.76.236.71:1199
2006-04-05 07:10:14 TCP from 65.54.194.118:80 to 67.76.236.71:1198
2006-04-05 07:10:15 TCP from 192.168.1.103:3505 to 207.46.4.122:1863
2006-04-05 07:10:24 TCP from 192.168.1.105:3526 to 207.46.5.4:80
2006-04-05 07:10:26 TCP from 207.68.178.16:80 to 67.76.236.71:3513
2006-04-05 07:10:26 TCP from 207.68.178.16:80 to 67.76.236.71:3512
2006-04-05 07:10:27 TCP from 192.168.1.113:1187 to 207.46.4.49:1863
2006-04-05 07:10:27 TCP from 192.168.1.105:3526 to 207.46.5.4(207.46.5.4):80
2006-04-05 07:10:27 TCP from 192.168.1.113:1187 to 207.46.4.49(207.46.4.49):1863
2006-04-05 07:10:30 TCP from 192.168.1.103:3505 to 207.46.4.122(207.46.4.122):1863
2006-04-05 07:10:31 TCP from 24.206.149.31:1976 to 192.168.1.102:1723
2006-04-05 07:10:31 TCP from 192.168.1.102:1723 to 24.206.149.31:1976
2006-04-05 07:10:31 TCP from 192.168.1.103:3528 to 65.110.50.55:80
2006-04-05 07:10:31 TCP from 192.168.1.105:3526 to 207.46.5.4(207.46.5.4):80
2006-04-05 07:10:35 TCP from 192.168.1.113:1187 to 207.46.4.49(207.46.4.49):1863
2006-04-05 07:10:39 TCP from 192.168.1.105:3526 to 207.46.5.4(207.46.5.4):80
2006-04-05 07:10:42 TCP from 192.168.1.113:1187 to 207.46.4.49(207.46.4.49):1863
2006-04-05 07:10:50 TCP from 192.168.1.103:3512 to 207.68.178.16:80
2006-04-05 07:10:50 TCP from 192.168.1.103:3509 to 63.218.23.142:80
2006-04-05 07:10:53 TCP from 192.168.1.113:1222 to 161.153.139.60:402
2006-04-05 07:10:55 TCP from 192.168.1.105:3526 to 207.46.5.4(207.46.5.4):80
2006-04-05 07:10:58 TCP from 192.168.1.103:3529 to 65.54.239.140:1863
2006-04-05 07:10:59 TCP from 192.168.1.103:3530 to 207.46.4.45:1863
2006-04-05 07:10:59 TCP from 192.168.1.103:3531 to 65.54.183.192:443
2006-04-05 07:11:00 TCP from 207.46.4.122:1863 to 67.76.236.71:3505
2006-04-05 07:11:00 TCP from 192.168.1.103:3532 to 207.46.216.61:80
2006-04-05 07:11:00 TCP from 207.46.4.49:1863 to 67.76.236.71:1187
2006-04-05 07:11:01 UDP from 192.168.1.103:3533 to 64.4.12.200:7001
2006-04-05 07:11:01 TCP from 192.168.1.103:3536 to 63.218.23.142(63.218.23.142):80
2006-04-05 07:11:01 TCP from 192.168.1.103:3538 to 207.68.178.16(207.68.178.16):80
2006-04-05 07:11:02 TCP from 192.168.1.103:3540 to 63.218.23.142(63.218.23.142):80
2006-04-05 07:11:04 UDP from 192.168.1.103:3534 to 64.4.12.201:9
2006-04-05 07:11:04 TCP from 192.168.1.103:3541 to 63.218.23.137:80
2006-04-05 07:11:04 TCP from 192.168.1.103:3542 to 63.218.23.134:80
2006-04-05 07:11:18 TCP from 192.168.1.113:1224 to messenger.hotmail.com(65.54.239.140):1863
2006-04-05 07:11:19 TCP from 192.168.1.113:1225 to 207.46.4.25:1863
2006-04-05 07:11:19 TCP from 192.168.1.113:1226 to loginnet.passport.com(65.54.179.192):443
2006-04-05 07:11:19 TCP from 192.168.1.113:1205 to 63.218.23.134(63.218.23.134):80
2006-04-05 07:11:19 TCP from 192.168.1.113:1203 to 63.218.23.137(63.218.23.137):80
2006-04-05 07:11:19 TCP from 192.168.1.113:1200 to 63.218.23.142(63.218.23.142):80
2006-04-05 07:11:19 TCP from 192.168.1.113:1198 to 65.54.194.118:80
2006-04-05 07:11:19 TCP from 192.168.1.113:1193 to 63.218.23.142(63.218.23.142):80
2006-04-05 07:11:20 TCP from 192.168.1.113:1227 to 207.46.216.61(207.46.216.61):80
2006-04-05 07:11:20 TCP from 192.168.1.113:1228 to 63.218.23.142(63.218.23.142):80
2006-04-05 07:11:20 TCP from 192.168.1.113:1230 to 65.54.194.118(65.54.194.118):80
2006-04-05 07:11:20 UDP from 192.168.1.113:1232 to 64.4.12.200(64.4.12.200):7001
2006-04-05 07:11:20 TCP from 192.168.1.113:1234 to 63.218.23.142(63.218.23.142):80
2006-04-05 07:11:23 UDP from 192.168.1.113:1233 to 64.4.12.201(64.4.12.201):9
2006-04-05 07:11:23 TCP from 192.168.1.113:1236 to 63.218.23.137(63.218.23.137):80
2006-04-05 07:11:23 TCP from 192.168.1.113:1237 to 63.218.23.134(63.218.23.134):80
2006-04-05 07:11:27 TCP from 192.168.1.105:3538 to 207.46.5.4(207.46.5.4):80
2006-04-05 07:11:30 TCP from 192.168.1.105:2978 to 63.218.23.134(63.218.23.134):80
2006-04-05 07:11:33 TCP from 207.46.5.4:80 to 67.76.236.71:3526
2006-04-05 07:13:03 TCP from 63.218.23.142:80 to 67.76.236.71:3509
2006-04-05 07:13:03 TCP from 63.218.23.142:80 to 67.76.236.71:3508
2006-04-05 07:13:42 Web login successfully from 202.164.174.43
2006-04-05 07:14:02 TCP from 192.168.1.113:1243 to 70.86.15.26:110
2006-04-05 07:14:03 TCP from 192.168.1.113:1244 to 66.235.200.169:110
2006-04-05 07:17:48 TCP from 192.168.1.104:3211 to 65.110.50.55(65.110.50.55):80
2006-04-05 07:18:01 TCP from 67.76.229.135:4302 to 67.76.236.71:445
2006-04-05 07:18:22 TCP from 192.168.1.105:3539 to 64.15.139.81:443
2006-04-05 07:18:33 UDP from 192.168.1.105:123 to 192.43.244.18:123
2006-04-05 07:19:05 TCP from 192.168.1.113:1245 to 70.86.15.26(70.86.15.26):110
2006-04-05 07:19:06 TCP from 192.168.1.113:1246 to 66.235.200.169(66.235.200.169):110
2006-04-05 07:20:36 TCP from 24.206.149.31:2143 to 192.168.1.102:1723
2006-04-05 07:20:36 TCP from 192.168.1.102:1723 to 24.206.149.31(24.206.149.31):2143
2006-04-05 07:20:44 TCP from 222.216.88.118:4634 to 67.76.236.71:139
2006-04-05 07:21:05 TCP from 222.216.88.118:2456 to 67.76.236.71:445
2006-04-05 07:22:13 UDP from 192.168.1.107:5061 to 69.59.240.83(69.59.240.83):5061
2006-04-05 07:22:36 UDP from 192.168.1.107:1281 to mot.vonage.net(216.115.30.200):21
2006-04-05 07:23:40 UDP from 192.168.1.113:2967 to 161.153.139.25:2967
2006-04-05 07:23:59 UDP from 192.168.1.113:1028 to 10.84.28.32:161
2006-04-05 07:24:07 TCP from 192.168.1.113:1248 to 70.86.15.26(70.86.15.26):110
2006-04-05 07:24:08 TCP from 192.168.1.113:1249 to 66.235.200.169(66.235.200.169):110
2006-04-05 07:26:16 TCP from 192.168.1.113:1250 to 161.153.139.60(161.153.139.60):402
2006-04-05 07:27:13 TCP from 192.168.1.103:3552 to 65.110.50.55(65.110.50.55):80
2006-04-05 07:28:46 TCP from 192.168.1.105:3550 to 64.15.139.81(64.15.139.81):443
2006-04-05 07:29:10 TCP from 192.168.1.113:1254 to 70.86.15.26(70.86.15.26):110
2006-04-05 07:29:10 TCP from 192.168.1.113:1255 to 66.235.200.169(66.235.200.169):110
2006-04-05 07:29:23 TCP from 192.168.1.113:1257 to qb13bgpatch.quickbooks.com(65.197.238.102):80
2006-04-05 07:29:24 TCP from 192.168.1.113:1259 to tcontent.quickbooks.com(208.240.243.36):80
2006-04-05 07:29:25 TCP from 192.168.1.113:1260 to qb13bgpatch.quickbooks.com(65.197.238.102):80
2006-04-05 07:29:45 TCP from 216.54.61.10:3781 to 67.76.236.71:1433
2006-04-05 07:29:53 TCP from 67.76.229.135:4273 to 67.76.236.71:445
2006-04-05 07:30:23 UDP from 201.254.69.194:1025 to 67.76.236.71:137
2006-04-05 07:31:17 TCP from 24.206.149.31:2264 to 192.168.1.102:1723
2006-04-05 07:31:17 TCP from 192.168.1.102:1723 to 24.206.149.31(24.206.149.31):2264
2006-04-05 07:34:12 TCP from 192.168.1.113:1263 to 70.86.15.26(70.86.15.26):110
2006-04-05 07:34:13 TCP from 192.168.1.113:1264 to 66.235.200.169(66.235.200.169):110
2006-04-05 07:34:16 UDP from 192.168.1.107:5061 to 69.59.240.83(69.59.240.83):5061
2006-04-05 07:34:31 TCP from 192.168.1.104:3223 to 65.110.50.55(65.110.50.55):80
2006-04-05 07:38:59 TCP from 192.168.1.105:3561 to 64.15.139.81(64.15.139.81):443
2006-04-05 07:39:14 TCP from 192.168.1.113:1265 to 70.86.15.26(70.86.15.26):110
0
 
DawilliamsCommented:
what is your internal ip scheme at home ? it cannot be the same as the internal ip scheme at work.
0
 
ixmanincAuthor Commented:
Thanks!  IP at home = 192.168.2.X
IP at work = 192.168.1.x

0
 
DawilliamsCommented:
just to clarify your trying to pass a pptp vpn throught the router to the 2003 server correct.
0
 
ixmanincAuthor Commented:
Yes.  I can post screen pics of anything you'd like to see.  Thanks a bunch.

ixmaninc
0
 
dlonganCommented:
What type of router is on the remote site (home)?
0
 
ixmanincAuthor Commented:
Currently, there is no router.  I have plugged the computer directly in to the modem to eliminate the variable of the home router causing the problem.
0
 
dlonganCommented:
You state your using XP?  Have you disabled windows firewall or any other software firewall?
0
 
ixmanincAuthor Commented:
Yes.  All firewalls disabled.
0
 
dlonganCommented:
Have you ensured that PPTP Passthrough was enabled on the linksys?

On the server side,  ensure your user account your using has the rights to dial-in(active directory users & computers), and that you have enabled RRAS to accept inbound connections (Routing and Remote Access).

0
 
ixmanincAuthor Commented:
http://www.houstoncommercialcapital.com/images/VPN.jpg

On the Linksys: I think that I have.  Please have a look at the above.

Confirming the server side now...

0
 
dlonganCommented:
Ok, it appears you have PPTP enabled.

I also noticed you have defined/Enabled a IPSEC VPN connection on the router.  If you don't need it PLEASE disable it as the preshared key is viewable with the pix you posted.
0
 
DawilliamsCommented:
ixmaninc:
again ,I could be wrong but from the research i've done on that router it will not pass pptp from the outside to the inside there is also no setting to enable the gre protocol
the pass-through radio buttons you see in the console are for allowing ipsec, pppoe, and pptp to traverse from the inside of the router to the outside
I will stick with what i said earlier and say you will have to use an ipsec based vpn client
Good luck
0
 
dlonganCommented:
Dawilliams - the "PPTP passthrough" is essentially how you allow the GRE packets through.  I have setup many BEFXXX linksys routers using PPTP to NT/2000/2003 RRAS servers.  As I posted earlier, the early version of the BEFSR41 v1 routers have issues if you are using 1.4X firmware.  I have had to downgrade them to earlier version to get PPTP to work.

This is a statement from Linksys:

"Microsoft uses IP Protocol 47 [GRE] for this secure tunnel.  Provided that the PPTP Pass Through is set to Enable on the Router's Filters page and port 1723 is forwarded to the VPN Server, the Router will allow authentication and remote access into your network.

The router will also allow you access remote PPtP networks from behind the router providing the PPtP Passthrough is enabled on the router."
0
 
ixmanincAuthor Commented:
Argh...

I have enabled the server machine to accept inbound connections, but now the server cannot see ANYTHING - internet or other computers.  I must have screwed up one setting or another.  The other computers on the domain see cannot get into the server either.

I will enact these steps as soon as I unscramble the current predicament.

Sometimes it sucks being the owner of a small business.  I had to get the cheapest IT guy I could find - ME!

0
 
dlonganCommented:
Oh man, I hate when that happens...

When you get it cleared up let us know - or if you have any questions don't hesistate.
0
 
dlonganCommented:
ixmaninc,

Here are screenshots of a 2003 server RRAS configuration:

http://www.metrocs.com/rras.htm

Hope this helps out.
0
 
ixmanincAuthor Commented:
OK!

All I could do is remove the VPN Role from the server, and I got the internet and the domain visibility back.

I suppose I should configure this role - carefully?

Does anybody have any idea what the VPN server role in Windows Server 2003 can do to disable the internet?  It was strange, because the TCP/IP stuff in the "Connections" area was fine.  But, no pinging, no internet, no nothing.  Weird.

Please, if any of your august group knows: is there list or instruction sheet on how to configure the VPN role in Server 2003?  The MS onboard how-to, uh, sucks.

Cheers all,
ixmaninc
0
 
dlonganCommented:
check out the screen shots I posted http://www.metrocs.com/rras.htm

0
 
ixmanincAuthor Commented:
Ah-Ha!  That's beautiful, dlongan.  Now, I will painstakingly pour over those pictures and see if I can proceed without Deep-sixing my internet!  Excellent!
0
 
ixmanincAuthor Commented:
Strange, but now my server can see the internet, but not the computers around it.  Does anyone know what can cause this?

ixmaninc
0
 
dlonganCommented:
ixmaninc,

how about detailing how your tcp/ip is setup on the server - address/mask/DG/DNS
lan ip of router
is the server providing DHCP for your lan - how is this setup?
do you have 2 nics on the server?
0
 
dlonganCommented:
do you have them setup as a "gateway" or "router"
0
 
dlonganCommented:
ixmaninc - sorry the last post was for another forum.
0
 
ixmanincAuthor Commented:
Well (phew!),

I have re-installed Windows Server 2003 and recreated the domain.

The system sees everything, and all is right with the planet.  Now I am back to where I started, and I shall proceed, uh, carefully.

I am thus far letting the router handle the DHCP.



0
 
ixmanincAuthor Commented:
I guess this is now a more difficult question, as I must connect 2 computers to this network and join them to the domain via VPN.

Salient points:

1) The 2 external computers are connected to a WRT54G Linksys Wireless Router (HOME LAN).  Cebridge cable.
2) The server is a standard Compaq computer running Windows Server 2003 Enterprise Edition (OFFICE LAN) connected via ethernet switch to a Linksys BEFVP41 v. 2.  Sprint DSL.  
3) There is a static IP on the router.
4) I have not installed the VPN role on the server yet.  The server is currently a file server, domain controller, and DNS server.
5) For now, I will let the router handle DHCP.  I have assigned a fixed IP for the server, however.

The goal: carefully set up VPN from those two external computers without wiping out the DNS, DHCP, and any other important acronym.

Thanks in advance for any sage advice.
ixmaninc
0
 
dlonganCommented:
ixmaninc

It's pretty much how we have been trying to get it setup in our previous posts.  Once you get RRAS setup on the server in the office, port forward 1723 to the static IP of your server in the office (not the router).  Ensure PPTP "passthrough" is enabled on both routers (remote and local).

I will add screenshots of a linksys router setup, tcp/ip settings on the RRAS server on my website for you to review.

One thing I would change is install DHCP on the server, disable DHCP on the office router. You have much better control of all the dynamic attributes for your network.

Create a pool of IP addresses outside of the DHCP scope to be used just for VPN connections.  This is done from within RRAS.

Once you get all the office setups complete, creating the VPN connection on the remote computers is a snap.

Here is brief task list:

1.  Install DHCP on server and configure
2.  Disable DHCP on office router
3.  Install and configure RRAS on server
4.  Port forwarding and PPTP passthrough on office router
5.  Grant dial-in permissions on user accounts
0
 
dlonganCommented:
ixmaninc - I have updated the RRAS screenshots - please review and let me know if you have any questions:

http://www.metrocs.com/rras.htm
0
 
ixmanincAuthor Commented:
Thank you very very much dlongon.  I'll get to work.  The whole RRAS scares me given what I just did, but your steps look comprehensive.

Wish me luck!  HA!

Best Regards,
ixmaninc
0
 
ixmanincAuthor Commented:
dlongon,

If I set all of the computers in the office to a fixed ip, how does that impact this evolution?

ixmaninc
0
 
ixmanincAuthor Commented:
I have enabled RRAS, correctlly I think, and once again the server has no internet connection or LAN connection.

I suspect its just a setting somewhere.

ixmaninc
0
 
dlonganCommented:
You can have static IP's for everything - but it is a pain to administrate.

Can you provide the results of a "route print" from the server before and during the lost to the internet:

go to the command prompt and type "route print"

You can redirect the output to a text file by using "route print > route.txt"

Change the text file name for each occurance or you will over right the last one.
0
 
ixmanincAuthor Commented:
Interestingly enough, I de-installed the RRAS role, and the server could see the net and the computers around it (and they it) again.

To follow is the current route print, though I'm not sure that helps.  I'll install the role again tonight after no one here needs the server data.  Then I'll run another.

Incidently, I did not make the server a DHCP yet - that is sill being handled by the router.  Is that a criticle item to installing RRAS?

Cheers,
ixmaninc


IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 15 f2 a4 cb 27 ...... Realtek RTL8139 Family PCI Fast Ethernet NIC
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1    192.168.1.106     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.106    192.168.1.106     20
    192.168.1.106  255.255.255.255        127.0.0.1        127.0.0.1     20
    192.168.1.255  255.255.255.255    192.168.1.106    192.168.1.106     20
        224.0.0.0        240.0.0.0    192.168.1.106    192.168.1.106     20
  255.255.255.255  255.255.255.255    192.168.1.106    192.168.1.106      1
Default Gateway:       192.168.1.1
===========================================================================
Persistent Routes:
  None
0
 
dlonganCommented:
No the router can provide DHCP, but when you create the pool of IP address that RRAS can use, you need to make sure there isn't any overlap with any addresses given out by the router to other clients.
0
 
ixmanincAuthor Commented:
dlongon,

Hmmmmm.  The server cannot see the other computers around it again.  I checked the DNS server log and got this, as a warning:


Event Type:      Warning
Event Source:      DNS
Event Category:      None
Event ID:      414
Date:            4/7/2006
Time:            1:23:52 PM
User:            N/A
Computer:      SERVER
Description:
The DNS server machine currently has no DNS domain name.  Its DNS name is a single label hostname with no domain (example:  "host" rather than "host.microsoft.com").
 
You might have forgotten to configure a primary DNS domain for the server computer. For more information, see either "DNS server log reference" or "To configure the primary DNS suffix for a client computer" in the online Help.
 
While the DNS server has only a single label name, all zones created will have default records (SOA and NS) created using only this single label name for the server's hostname.  This can lead to incorrect and failed referrals when clients and other DNS servers use these records to locate this server by name.
 
To correct this problem:
  1) open Control Panel
  2) open System applet
  3) select Computer Name tab
  4) click the "Change" button and join the computer to a domain or workgroup; this name will be used as your DNS domain name
  5) reboot to initialize with new domain name
 
After reboot, the DNS server will attempt to fix up default records, substituting new DNS name of this server, for old single label name.  However, you should review to make sure zone's SOA and NS records now properly use correct domain name of this server.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Now, I do show a domain name - ix.com, with the server being server.IX.com.  I'm not sure why this is happening....

0
 
dlonganCommented:
Well lets look at that after we get rras working.  Did you happen to capture a "route print" during the outage?
0
 
ixmanincAuthor Commented:
dlongon,

Interestingly enough, I could connect all computers when I set the DNS server on the router to the IP of the server.  I then released/renewed IPs on all client computers, then manually connected them (using "run" and then \\client name).

The server computer still will not navigate to the other client computers, but I can connect to the using "run..."

So, I guess we're back up for now.  As for the VPN, I think that I am going to get  another Linksys BEFVP41 and put it at the remote LAN.  It's my understanding that this is the most reliable way to have VPN - router to router?
0
 
dlonganCommented:
ixmanic - How goes everything - did you install another linksys for the vpn?
Apprecate if you could close the question and honor the points accordingly.
0

Featured Post

Who's Defending Your Organization from Threats?

Protecting against advanced threats requires an IT dream team – a well-oiled machine of people and solutions working together to defend your organization. Download our resource kit today to learn more about the tools you need to build you IT Dream Team!

  • 20
  • 20
  • 6
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now