Re: Huge problem; new to this job
- From: "James McIllece [MS]" <jamesmci@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 14 Aug 2007 13:51:33 -0700
plaidapplered <plaidapplered.2v6nnd@xxxxxxxxxxxxx> wrote in
news:plaidapplered.2v6nnd@xxxxxxxxxxxxx:
I'm new to these forums and I am starting off with a huge problem. The
network I run at work (I'm very new to this) was configured years ago
and is run very haphazardly. Right now, nothing is working. Here's what
happened:
I took a vacation day on Friday and someone came by to test out our T1
lines because they'd been running slow. From what I've been told by the
office manager, he couldn't test them out so he "did something to the
server" so he could access our lines. Once he completed his testing,
our entire network went down. We have 2 offices and 1 server. Computers
in the office where the server is can print to our local printers and
get to our shared network drive, but there's no internet. Our remote
office can get to the internet only.
Here's the little bit of info I was able to gather earlier today:
1. System Event Viewer is showing error 20192. Remote Access. A
certificate could not be found. Connections that use the L2TP protocol
over IPSec require the installation of a machine certificate, also
known as a computer certificate. No L2TP calls will be accepted.
2. Ipconfig brings up Autoconfiguration IP Address: 169.254.228.227,
which from what I can find means APIPA is being used rather than DHCP.
But I don't know how to fix that.
3. Ipconfig /renew brings up this message: The following error occurred
when renewing adapter Local Area Connection: DHCP Server unreachable
4. Ipconfig /release brings up this message: All adapters bound to DHCP
do not have DHCP addresses. The addresses were automatically configured
and can not be released.
I don't know how to fix all of this and I'm supposed to be getting all
new printers and copiers installed first thing Monday morning, and
right now I don't have a working network to install them onto. Please
help!!
It sounds like your branch office is using a site-to-site L2TP/IPsec VPN
connection to provide connectivity between the two offices (across the
Internet) and that the connection is down for some reason. Perhaps someone
deleted the certificate used for these connections.
It also sounds like the DHCP server is on the local LAN, so the local LAN
is receiving IP address leases, but because the VPN link is down, the
branch office computers are not able to contact the DHCP server.
So you should focus your energy on fixing the VPN connection. Routing and
Remote Access service is where you configure VPN. For L2TP/IPsec, both VPN
servers need a server certificate -- so you should also have Certificate
Services installed, and the CA should have been used to issue certificates
to the VPN servers.
Either that, or the certificates were purchased from a third party CA like
Verisign.
So that is the first step -- figure out if Certificate Services is
installed. If it is, then you need to either request or reissue a cert,
read the Certificate Services Help and/or see the info at this site for
assistance:
http://www.microsoft.com/windowsserver2003/technologies/pki/default.mspx
--
James McIllece, Microsoft
Please do not send email directly to this alias. This is my online account
name for newsgroup participation only.
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- References:
- Huge problem; new to this job
- From: plaidapplered
- Huge problem; new to this job
- Prev by Date: Re: DHCP Lease expiration questions
- Next by Date: Re: Running out of IP's...what to do?
- Previous by thread: Re: Huge problem; new to this job
- Next by thread: Event Viewer Networking Connectivity
- Index(es):
Relevant Pages
|
