Windows Server 2003 killing adsl router on startup



  • 1. RRAS VPN wont allow access to LAN
    Hi Guys, I have a Windows 2003 server behind a firewall and I am allowing PPTP VPN to pass through the firewall to terminate on the sinlge NIC on the server. I have setup RRAS to terminate the VPN and it connects successfully and I can ping and access resources on the Server. However, I cannot ping or access any other devices on the LAN, any attempt to ping just times out. The device connecting to the VPN is given an IP address on the LAN's Subnet from DHCP (I have also tried assigning a static range). I have tried disabling and reinstalling RRAS multiple times with different settings, from VPN and dial up to VPN and NAT with Basic firewall. I have attempted static routes but still can't communicate with any devices outside of the RRAS server. Can anyone suggest anything I can try to get this resolved? Any help would be greatly appreciated.
  • 2. VPN Windows 2003 error 800
    Hola atodos. Me ocurre algo extra. Tengo configurado vpn en el servidor y 3 clientes windows. Uno de ellos es vista. Puedo conectar con el vista y con un xp desde el exterior de mi red y desde el interior., pero con un xp me es imposible desde el exterior. Siempre me muestra error 800. El caso es que todo debe estar bien configurado porque si con los dos va bien, porque no con el otro ? Mi router adsl es un comtrend 5361 con esta version del software A101-220TLF-C44 de telefonica. Alguna idea ? Hello. I have configured vpn in windows 2003 and i can to connect from my home to my office with several computers (one win xp and another with vista). But i have another computer with win xp configured as others and always a get error 800. If two of them works fine i don`t know what happen. At office we use modem-router adsl comtrend ct-5361 with firmware version a101-220tlf-c44 Any idea ? Thanks.

Windows Server 2003 killing adsl router on startup

Postby DrewM » Tue, 02 Mar 2004 07:07:11 GMT

I've just reinstalled my 2003 server after yet another AD corruption. 
Booting the fresh install was fine. I performed a Windows Update, 
rebooted, installed AD and rebooted again.

Now, every time my server starts up, it causes my adsl router to stop 
responding to any network requests. Can't even ping it. If I shut the 
server down and power-cycle the router, all is fine again, and will 
remain so until I start the server up again.

The only things different about this install to the last are:

- using different FQDN
- using 2000 mixed mode instead of 2003 native, to ease SAMBA issues

The router is set as the server's default gateway.

Things I've tried so far are:

- verified that they're both using valid, distinct IP addresses
- confirmed that DHCP server isn't running, to avoid IP# conflicts
- rebooted in Safe Mode with Networking, problem still occurs

I'm about to try in Safe Mode (no networking) to see if that causes the 
problem too. As it kills my internet connection, I wanted to post this 
first ;)

Any ideas what I'm doing wrong? I can't think of any legitimate network 
operation that causes complete death to another device.

Many thanks,


Re: Windows Server 2003 killing adsl router on startup

Postby Kristofer Gafvert » Tue, 02 Mar 2004 07:11:21 GMT


Is it possible that you are infected by a virus that floods the network?

Kristofer Gafvert - IIS MVP
Reply to newsgroup only. Remove NEWS if you must reply by email, but please
do not. - FAQ and Tutorials for Windows Server 2003

Re: Windows Server 2003 killing adsl router on startup

Postby DrewM » Tue, 02 Mar 2004 07:17:30 GMT

I certainly couldn't rule that out 100%. Although I'd class it as 
unlikely. I'll run a scan.

Booting into Safe Mode with no networking doesn't cause a problem (as 

Re: Windows Server 2003 killing adsl router on startup

Postby DrewM » Tue, 02 Mar 2004 07:33:54 GMT

After running some tests, I can't find anything to support that hypothesis.

Any other suggestions?

Re: Windows Server 2003 killing adsl router on startup

Postby Gino » Tue, 02 Mar 2004 15:02:13 GMT

I would boot the server up with the Ethrnet cable disconnected, connect it
and then monitor the Nic status that shows sent and received packets. If
your server starts sending out high volums of traffic for no reason you are
infected. Just because a scan comes up neg dosn't mean that your server
CAN'T be infected. If you just rebuilt your server and connected to the
internet to apply the patches, you'll never make it. Your server will become
infected before you get the patches applied. And once infected the patches
don't do anything.

Re: Windows Server 2003 killing adsl router on startup

Postby DrewM » Tue, 02 Mar 2004 20:33:00 GMT

I tried monitoring this from the router, and could see no unusual 
increase in traffic before the router died.

Other than the test described, is there a reliable way to detect whether 
the machine is infected?

This may sound stupid, but how can I patch the server without going to 
get the patches? The only approach I can think of is to install linux on 
the server first, download the patches somehow, burn them onto a CD, 
reinstall with Windows and install the patches. Not ideal.

Also, whatever it is that is infecting the machine would have to get 
through a hardwire filewall (on total lock-down) and router, and be 
totally dependent on Active Directory. When I uninstall AD, the problem 


Re: Windows Server 2003 killing adsl router on startup

Postby Michael Holzemer » Wed, 03 Mar 2004 00:14:32 GMT

In item <%23gg3zD4$ XXXX@XXXXX.COM >,
DrewM says...

Does the router have logging? Also is your FQDN the same as a registered one on
the internet? Is you AD server also the DNS server for itself?
The router log should show you the traffic attempting to pass through it. You
said you only have the issue when you install AD. Just for clairity are you
using a FQDN like mydomain.domain or something someone else may own like Is your DNS server for the domain external to you? If so you will
have issues with srv records AD needs.


Michael Holzemer
No email replies please - reply in newsgroup

Learn script faster by searching here

Re: Windows Server 2003 killing adsl router on startup

Postby DrewM » Wed, 03 Mar 2004 01:22:13 GMT

Unfortunately, no.

Yes, I'm using, where is registered and 
under my control at our ISP. I've set up an A record for 'office' within 
that zone to point to the IP address our adsl uses

Yes. With forwarders to our ISPs DNS servers., registered to us.

Yup, it's at our ISP, on the other side of a locked-down firewall, and 
is running linux.

... so, how *should* I do this? To be honest, I'd be happy using an old 
NT4 style single word domain name, but the installer gives dire warnings 
against this. I assume it should be possible to run as without needing to host our own public DNS servers.

thanks for your time.


Re: Windows Server 2003 killing adsl router on startup

Postby Phillip Windell » Wed, 03 Mar 2004 02:46:03 GMT

I think it is the combination of patches installed via Windows Update.  It
wouldn't be the first time I have seen a combination of patches{*filter*}things
up,...for that matter I have seen plenty screwed up by just one patch, let
alone a combination of them. Those fairly recent RPC patches for example
stop the older MS Proxy2 dead in its tracks, the solution is to not install
those patches and to take other measures to protect the machine from the RPC

I never use Windows Update, I don't trust dumping all those patches on a
machine. I always have the SPs and patches that I have "hand picked" burned
onto a CD, then when I build the machine I apply the patches from a the CD
before I expose the machine to the Internet.  After that I apply only
patches that I trust and feel that they are "must-haves" and I don't worry
about the rest, is better to wait until a full Service Pack comes out.

If you read the "mitigating circumstances" listed for the different
vulnerabilities you will find that the situation doesn't apply to most
machines on a private network behind a firewall or proxy that isn't exposed
directly to the Internet.  You just have to decide which applies to your

Phillip Windell [MCP, MVP, CCNA]

it. You

Re: Windows Server 2003 killing adsl router on startup

Postby sharad » Thu, 04 Mar 2004 11:19:49 GMT

ello Drew:
You can't use the external DNS linux based for your AD, especially behing
firewall / routers. And there is
no need either!!!
I would suggest the first thing you do is change the
FQDN from to something else
it must not be a single label domain name doesn't mean that it must be a
registered domain name.
You can for example chose FQDN as : office.loc
(.loc indicating local server.) or mycomany.comp
(comp indicating comany)
You can chose anything except the Registred Domain name (and make sure that
the one you chose will not be
a regitered domain of someone else. So best is choose
comany.loc of office.loc)
Once you decide the FQDN as above, do as follows.
1. Run DCPROMO to uninstall the AD and then reboot. (During AD uninstall
process chose this is the
last DC in the domain, to make it a stand alone server.)
2. Un install DNS server, and reboot.
3. After reboot on the NIC TCP/IP properties make sure that primary DNS
points to itself.
then run dcpromo again to install AD. Give FQDN company.loc etc. as
chosen by you.
4. First it will give you error no DNS server available etc. and will give
you options
'I have correct problem Retry' and 'Install DNS'. Chose "Install DNS option"
and it will install DNS also nicely.
5. After dcpromo is completed and machine rebooted, point the default
gateway to the
router, enter the forwarders in the DNS maager. Do not try internet yet.
6. Since your win 2003 server is behing router and firewall, you will have
to disable
EDNS0 Probes of win 20003 DNS (which are enabled by default.) to do this:
first you must install Support Tools from Win 2003 CD on the
Inster win 2003 CD, browse the CD, go to
\Support\Tools folder and double click on 'suptools.msi '
After support tools are installed REBOOT the server.
After rebooting, go to command prompt and type (or copy and paste) following
dnscmd /Config /EnableEDnsProbes 0
7.Client machines must join the domain? then on each client machine
the primay DNS server must be set to server IP address and Default
Gate Way can be set to the Router IP address.

8. Also remove the A record "Office" wich you have set up on ISP's DNS.


"DrewM" < XXXX@XXXXX.COM > wrote in message
news:%23Tcqal6$ XXXX@XXXXX.COM ...
it. You

Re: Windows Server 2003 killing adsl router on startup

Postby DrewM » Thu, 04 Mar 2004 19:36:00 GMT

<snip detailed instructions>

Sharad - thanks ever so much. That's going to be really helpful.


Similar Threads:

1.Windows Server 2003 killing adsl router on startup

2.(router + adsl modem) versus (router with built in adsl modem)

I have an Alcatel ADSL modem provided free by Pipex.  I want to set up
a wireless network but I'm not sure whether to just buy a router or a
router with a built in modem (and therefore not use the Alacatel any

What are the benefits of having my router and modem in one box?


3.Windows 2003 Killing My Router

Dear Anyone,

I've recently migrated a peer to peer network to a Win 2003 Domain
controlled environment.  Before the change Internet Access via a
broadband connection was working perfectly.

Since the first day of introducing the server I'm now experiencing
problems accessing, not only the router itself, but also the
Internet/email/outside world.

Ping packets are simply being dropped or just taking thousands of mili
seconds to respond.  I've examined the possibilty of it being Virus
related but firmly believe this not to be the case.  The problem
occurs at random intervals and requires a physical reboot of the
router for it to come back to life.  It seems as if the router gets
tied up in some task that takes up 100% of it's time and dis-regards
everything else.  When the problem does occur I've even disconnected
the router from the network and connected it to a single PC to see if
it recovers itself, only to find the problem still persists and only a
power cycle fixes it.  Is Win 2003 creating particular network traffic
that causes routers to crash?  I can't say I've ever experienced this
before.  The router in question is a Turbocomm EA110.

Any ideas or solutions would be greatly appreciated.



4.Windows 2003 Server SP1 Woes, Windows File Protection is Killing M

After installing SP1 for Windows 2003 I rebooted and every single service 
failed to start. SP1 would not even uninstall. I then used the "R"epair 
option to recopy the original installation files and rebooted. I then started 
getting thousands of popups for:
Windows File Protection 
"Files that are required for Windows to run properly have been replaced by 
unrecognized versions. To maintain...", Insert your Windows 2003 Standard 
Edition CD-ROM now.. 

I insert the CD and it does not find the setup directory or something. I 
just keep getting the dialog over again. I re-applied SP1 (It worked this 
time around though SQL server won't start on the machine now but one problem 
at a time). I keep getting the messages. And of course there is no browse 
button on the dialog so I can choose a directory to locate the OS files. Is 
there anyway short of re-installing the whole OS and everything else to 

Can I somehow tell Windows File Protection to search for the files in a 

Extremely Frustrated and thanks for any help,

5.TCP/IP Stack Improvements in Windows Server 2003 and Windows Server 2003 Service Pack 1

6. Windows Server 2003 and DLink router as DHCP server

7. COnfused if ADSL router will not allow me to use WIn 2003 NAT

8. Multiple VPN Tunnels Through ADSL Router to SBS 2003 RRAS



Who is online

Users browsing this forum: No registered users and 3 guest