DHCP went out, RRAS acting weird

So I finally got my RRAS up acting as my home router and it worked
great for a few days. I came home last night and turned on my laptop
and it wouldnt connect to the wireless access point. So I went to the
cmd and tried the ipconfig /release and /renew. It still said I had
limited or no connectivity. So I went into DHCP and deleted the lease
I had. Still couldnt get a new one. I plugged into the LAN. Still
no IP. DHCP woulndt issue any. So I attemtped deleting the scope and
tried recreating. Still nothing. So I uninstalled DHCP and
reinstalled it, reauthorized it and set the scope back up. Still
nothing. I noticed for some reason the servers name in DHCP was
listed as <myservername>.mshome.net instead of at my domain name. The
sever itself was a DC for the domain so I dont understand that. I
installed DHCP on another server and it started handing out IPs right
away. So that was one problem. Secondly RRAS stopped working or
something. I plugged in the cable modem to one NIC and it got an auto
IP from my ISP. I could browse the internet on the server just fine.
The instant I plug in the LAN line to hook the RRAS server to the LAN
switch the internet stops working.

Any ideas at all?

thanks - jon

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> tried recreating. Still nothing. So I uninstalled DHCP and
> reinstalled it, reauthorized it and set the scope back up. Still
> nothing. I noticed for some reason the servers name in DHCP was
> listed as <myservername>.mshome.net instead of at my domain name. The

It is supposed to be the Active Directory Domain Name,...not any Public
registered Domain Name you might have.

> away. So that was one problem. Secondly RRAS stopped working or
> something. I plugged in the cable modem to one NIC and it got an auto
> IP from my ISP. I could browse the internet on the server just fine.
> The instant I plug in the LAN line to hook the RRAS server to the LAN
> switch the internet stops working.

Not sure here. Maybe others will have ideas,...but,....here are some things that
need to be looked at.

1. On the Internet facing Nic of the RRAS box:
A. Unbind everything from the nic except TCP/IP. Uncheck Client for
MS Network, File&Print Sharing, Qos, etc. Only keep TCP/IP.
B. In the Advanced Properties of the TCP/IP section of the nic, under DNS,
do *not* have it register with DNS.

2. On the RRAS box in general:
A. Properties of Net Places,..Advanced from Top Menu,...Advanced from
dropdown menu,...in the upper box use the side arrow to move the LAN
Facing Nic to the top of the list
B. In the TCP/IP specs of the nic (either nic or both nics, doesn't matter)
the
only DNS that should be listed is the internal Active Directory DNS,..do
not
use the ISP's DNS. The ISP's DNS should *only* be found on the
Forwarders List within the Config of the DNS services on the AD/DNS
machine (the DC).

It is possible that those things all by themselves may fix the RRAS issue,...but
even if they don't,...they still need to be set as I described.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed (as annoying as they are, and as stupid as they sound), are
my own and not those of my employer, or Microsoft, or anyone else associated
with me, including my cats.
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/downlo...7/ts_rules.doc

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------