Re: Remote Site, DHCP Scope Issue
- From: "bkbgc1@xxxxxxxxx" <bkbgc1@xxxxxxxxx>
- Date: 1 Oct 2006 16:40:57 -0700
Lanwench,
Thank you for the input and for the timely response, I know Microsoft
doesn't staff the groups on the weekend. Again - thanks. I have enabled
the changes on the router. I am out of town right now, so a user is
going to call me tomorrow after they turn on the computers.
I will be sure to report on my efforts.
Lanwench [MVP - Exchange] wrote:
In news:1159726311.917790.176990@xxxxxxxxxxxxxxxxxxxxxxxxxxx,
bkbgc1@xxxxxxxxx <bkbgc1@xxxxxxxxx> typed:
Hello All,
I've got a SBS 2003 on one end of a VPN Tunnel (2 Linksys BEFVP41
Routers). On the other end, just computers plugged directly into the
VPN router. VPN is successfully connected - or so it says. Side note:
I was on the phone with linksys, they assure me the 2 routers are
configured correctly and the tunnel is active.
Problem:
When DHCP is disabled at the remote office, the remote office
computers are not able to get IP Addresses from the SBS.
But they wouldn't be able to do that, tho - not across that connection. Set
up their Linksys DHCP scope to dish out *only* the appropriate DNS server
(your SBS server's LAN IP) if they don't have their own DC - if you do have
more than a handful of users there, tho, you might consider putting a
Win2003 DC (running AD-integrated DNS) in that location. Whatever you do,
they need their own DHCP server to give them:
* LAN IP on their remote subnet
* Default gateway of their Linksys LAN IP
* WINS server IP of your SBS box
* DNS suffix (yourdomain.local)
* DNS server (SBS LAN IP)
When DHCP is enabled at the remote office, i can ping the SBS but full
connectivity is not happenning. Example: When domain users login to
the computers, the computer says 'You could not logon because the
domain BGCSM is unavailable'.
DNS problems - see above.
Only way to get domain users in, is by
using 'Logon using dial-up connection', then selecting a VPN
Connection. (By the way - this is how I joined the computers to the
domain: VPN Client, Manual add to domain, then add domain user as a
local admin, then restart, then login with dial-up).
Why? You shouldn't have had to - if the tunnel was set up, working, and DNS
was being handed out appropriately by their hardware.....
More info:
I setup a scope for the second office with the subnet (see network
topology at bottom):
172.2.6.x
255.255.255.0
With DHCP disabled, I set one client at the remote office to a static
IP within the remote office scope, and had the same connectivity
problems.
My Question:
Do the computers need to get their ip from the server for full
connectivity? If so, when all of my routers have DHCP disabled why
can't my computers get IP addresses & contact the domain controller.
Any help is much appreciated. Thank you in advance!
Main Office Topology:
=====================
[DSL Modem] Static IP 207.114.12.154
[Linksys BEFVP41 v2] WAN IP 207.114.12.154
[SBS 2003] LAN IP 172.2.5.56LAN IP 172.2.5.50
DHCP Disabled
[Dell Switch]DHCP Enabled / Domain Controller
[Client Computers] 172.2.5.x
Remote Office Topology:
=======================
[Cable Modem] Dynamic IP
[Linksys BEFV41 v2] LAN IP: 172.2.6.1DynDNS: bgcsmltc.dyndns.org
[Client Computers] 172.2.6.x
All that is fine - just check out the advice above re DNS.
.
- Follow-Ups:
- Re: Remote Site, DHCP Scope Issue
- From: Lanwench [MVP - Exchange]
- Re: Remote Site, DHCP Scope Issue
- References:
- Remote Site, DHCP Scope Issue
- From: bkbgc1@xxxxxxxxx
- Re: Remote Site, DHCP Scope Issue
- From: Lanwench [MVP - Exchange]
- Remote Site, DHCP Scope Issue
- Prev by Date: Re: Exchange setting preventing emails from being sent
- Next by Date: Re: Exchange setting preventing emails from being sent
- Previous by thread: Re: Remote Site, DHCP Scope Issue
- Next by thread: Re: Remote Site, DHCP Scope Issue
- Index(es):
Relevant Pages
|
Loading