VPN Suddenly Stopped Working

I support a small nonprofit with a small network. They have an office
computer running Win XP (patch level unknown), which uses Windows Firewall;
this machine supports the Access database that contains business and
membership records.

The officers use a VPN to connect to the office computer, since they keep
local copies of the database which they update and sync. They don't use VPN
clients; they just configure network connections on their laptops, following
instructions which I wrote. Recently the VPN stopped working for no visible
reason; I'm hoping someone can suggest something to try.

The VPN is supported by a LinkSys BEFSX41 ver2 router, 4 Ethernet ports.
The firewall is enabled; ports 1723, 47, and 1701 are forwarded to the office
computer at its static IP 192.168.23.101., which is configured on the LAN
connection. IPSec passthrough is enabled. Other items plugged into the
LinkSys are a LinkSys VoIP router and a NetGear 8 port Ethernet switch. The
office computer is plugged into the NetGear switch, as are Ethernet cables
for use by wandering volunteers' laptops.

The internal router IP is 192.168.23.1, and it also serves DHCP for 50
addresses starting at .150. The subnet mask is 255.255.255.0. The Internet
connection is PPoE and the IP is not static, so we use DynDNS, which the
router supports, to provide a stable host name for the VPN connection.

The router seems to be working; full Internet access is available. But
attempts to open the VPN get 1 of 2 errors depending on the source: my Vista
laptop gets RRAS error 800; my XP desktop gets RRAS error 678. Attempts to
telnet to port 1732 at the DynDNS hostname (or its fronted IP, I've tried
both) produce a time-out, as did DynDNS's Open Port tool.

I'm almost positive, having read the online materials about VPNs, that the
router setup is correct; but we rebuilt the configuration Saturday, and I'm
wondering if there was some other configuration that I didn't have documented.

I tried (shame on me!) turning off the Windows firewall on the office
computer briefly, and I still couldn't connect to the VPN; but I'm not sure
if I should have expected to, because I was connected by Ethernet to the
local LAN, same network as the office server. I didn't have another network
with Internet access available to try from.

So: is the Windows firewall configuration a possible culprit? Or was my
failure to connect because I wasn't on the "outside" of the router? If the
firewall isn't a possible culprit, what other configurations might be the
problem? Any suggestions most gratefully accepted. We tried rebooting
everything again, and we tried taking the NetGear switch and the VoIP router
out of the connection and plugging the office computer directly into the
LinkSys - didn't help, still no response on the port.

--
hedera

Nature bats last.

"hedera" <(E-Mail Removed)> wrote in message
news:1D1AC933-C41C-49A4-99F1-(E-Mail Removed)...
>I support a small nonprofit with a small network. They have an office
> computer running Win XP (patch level unknown), which uses Windows
> Firewall;
> this machine supports the Access database that contains business and
> membership records.
>
> The officers use a VPN to connect to the office computer, since they keep
> local copies of the database which they update and sync. They don't use
> VPN
> clients; they just configure network connections on their laptops,
> following
> instructions which I wrote. Recently the VPN stopped working for no
> visible
> reason; I'm hoping someone can suggest something to try.
>
> The VPN is supported by a LinkSys BEFSX41 ver2 router, 4 Ethernet ports.
> The firewall is enabled; ports 1723, 47, and 1701 are forwarded to the
> office
> computer at its static IP 192.168.23.101., which is configured on the LAN
> connection. IPSec passthrough is enabled. Other items plugged into the
> LinkSys are a LinkSys VoIP router and a NetGear 8 port Ethernet switch.
> The
> office computer is plugged into the NetGear switch, as are Ethernet cables
> for use by wandering volunteers' laptops.
>
> The internal router IP is 192.168.23.1, and it also serves DHCP for 50
> addresses starting at .150. The subnet mask is 255.255.255.0. The
> Internet
> connection is PPoE and the IP is not static, so we use DynDNS, which the
> router supports, to provide a stable host name for the VPN connection.
>
> The router seems to be working; full Internet access is available. But
> attempts to open the VPN get 1 of 2 errors depending on the source: my
> Vista
> laptop gets RRAS error 800; my XP desktop gets RRAS error 678. Attempts
> to
> telnet to port 1732 at the DynDNS hostname (or its fronted IP, I've tried
> both) produce a time-out, as did DynDNS's Open Port tool.
>
> I'm almost positive, having read the online materials about VPNs, that the
> router setup is correct; but we rebuilt the configuration Saturday, and
> I'm
> wondering if there was some other configuration that I didn't have
> documented.
>
> I tried (shame on me!) turning off the Windows firewall on the office
> computer briefly, and I still couldn't connect to the VPN; but I'm not
> sure
> if I should have expected to, because I was connected by Ethernet to the
> local LAN, same network as the office server. I didn't have another
> network
> with Internet access available to try from.
>
> So: is the Windows firewall configuration a possible culprit? Or was my
> failure to connect because I wasn't on the "outside" of the router? If
> the
> firewall isn't a possible culprit, what other configurations might be the
> problem? Any suggestions most gratefully accepted. We tried rebooting
> everything again, and we tried taking the NetGear switch and the VoIP
> router
> out of the connection and plugging the office computer directly into the
> LinkSys - didn't help, still no response on the port.
>
> --

Hello Hedera,

Essentially using the Windows built-in networking VPN, is a VPN client
that's built in to the operating system.

Are you saying the XP machine is the VPN server?

Assuming the XP machine is accepting VPN connections, then you would be
using PPTP VPN, and not L2TP IPSec VPN, so then port 1701 is not needed.

You'll need port 1723, which you've already configured, but you will also
need GRE, also called Protocol ID #47 (this is not Port 47) to be opened. I
believe to do that, you just need to enable PPTP checkbox. You'll need to
double check the Linksys docs on this.

As for the error messages, they are saying that the VPN connection cannot be
established because something is either blocking it or not configured. My
feeling is GRE is not configured correctly to go inbound to the XP machine.
Click on the following link, then click on your error number:
http://www.chicagotech.net/raserrors.htm

You said you had this working before and it stopped suddenly. Did something
change, such as an update, or someone install any software on the XP box?

Testing this internally trying to connect through the router won't do the
trick, because it doesn't support 'U-Turns' You can, however, test it
internally by connecting directly to the XP machine.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum to benefit from collaboration
among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer
(E-Mail Removed)
http://twitter.com/acefekay

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Ace,
Thanks for the quick reply. I'm a little confused about the VPN server; I
thought that the LinkSys router was the VPN server. It is, however,
forwarding the ports through to the XP box, which then allows the connector
to log in to the XP box using a userid and password configured for the
purpose. (A shared userid and password, tsk; security by obscurity.) So I
guess in that sense, the XP server is the VPN server. PPTP passthrough is
definitely enabled on the LinkSys router.

It's nice to know we don't need port 1701, I'll document that, thanks.
Thanks also for confirming that my firewall test wasn't valid, I'll make a
note. I'm obviously going to have to go back in and peer at the XP
configuration. I don't know what changes or updates may have been made to
the machine, I'm not even sure of the patch level. I need to write all that
down.

If GRE isn't correctly configured on the XP box, where would I look, and
what should I see?

Thank you again for your help, this is seriously impacting the nonprofit's
ability to do business.
---
hedera

Nature bats last.


"Ace Fekay [MCT]" wrote:

> "hedera" <(E-Mail Removed)> wrote in message
> news:1D1AC933-C41C-49A4-99F1-(E-Mail Removed)...
> >I support a small nonprofit with a small network. They have an office
> > computer running Win XP (patch level unknown), which uses Windows
> > Firewall;
> > this machine supports the Access database that contains business and
> > membership records.
> >
> > The officers use a VPN to connect to the office computer, since they keep
> > local copies of the database which they update and sync. They don't use
> > VPN
> > clients; they just configure network connections on their laptops,
> > following
> > instructions which I wrote. Recently the VPN stopped working for no
> > visible
> > reason; I'm hoping someone can suggest something to try.
> >
> > The VPN is supported by a LinkSys BEFSX41 ver2 router, 4 Ethernet ports.
> > The firewall is enabled; ports 1723, 47, and 1701 are forwarded to the
> > office
> > computer at its static IP 192.168.23.101., which is configured on the LAN
> > connection. IPSec passthrough is enabled. Other items plugged into the
> > LinkSys are a LinkSys VoIP router and a NetGear 8 port Ethernet switch.
> > The
> > office computer is plugged into the NetGear switch, as are Ethernet cables
> > for use by wandering volunteers' laptops.
> >
> > The internal router IP is 192.168.23.1, and it also serves DHCP for 50
> > addresses starting at .150. The subnet mask is 255.255.255.0. The
> > Internet
> > connection is PPoE and the IP is not static, so we use DynDNS, which the
> > router supports, to provide a stable host name for the VPN connection.
> >
> > The router seems to be working; full Internet access is available. But
> > attempts to open the VPN get 1 of 2 errors depending on the source: my
> > Vista
> > laptop gets RRAS error 800; my XP desktop gets RRAS error 678. Attempts
> > to
> > telnet to port 1732 at the DynDNS hostname (or its fronted IP, I've tried
> > both) produce a time-out, as did DynDNS's Open Port tool.
> >
> > I'm almost positive, having read the online materials about VPNs, that the
> > router setup is correct; but we rebuilt the configuration Saturday, and
> > I'm
> > wondering if there was some other configuration that I didn't have
> > documented.
> >
> > I tried (shame on me!) turning off the Windows firewall on the office
> > computer briefly, and I still couldn't connect to the VPN; but I'm not
> > sure
> > if I should have expected to, because I was connected by Ethernet to the
> > local LAN, same network as the office server. I didn't have another
> > network
> > with Internet access available to try from.
> >
> > So: is the Windows firewall configuration a possible culprit? Or was my
> > failure to connect because I wasn't on the "outside" of the router? If
> > the
> > firewall isn't a possible culprit, what other configurations might be the
> > problem? Any suggestions most gratefully accepted. We tried rebooting
> > everything again, and we tried taking the NetGear switch and the VoIP
> > router
> > out of the connection and plugging the office computer directly into the
> > LinkSys - didn't help, still no response on the port.
> >
> > --
>
> Hello Hedera,
>
> Essentially using the Windows built-in networking VPN, is a VPN client
> that's built in to the operating system.
>
> Are you saying the XP machine is the VPN server?
>
> Assuming the XP machine is accepting VPN connections, then you would be
> using PPTP VPN, and not L2TP IPSec VPN, so then port 1701 is not needed.
>
> You'll need port 1723, which you've already configured, but you will also
> need GRE, also called Protocol ID #47 (this is not Port 47) to be opened. I
> believe to do that, you just need to enable PPTP checkbox. You'll need to
> double check the Linksys docs on this.
>
> As for the error messages, they are saying that the VPN connection cannot be
> established because something is either blocking it or not configured. My
> feeling is GRE is not configured correctly to go inbound to the XP machine.
> Click on the following link, then click on your error number:
> http://www.chicagotech.net/raserrors.htm
>
> You said you had this working before and it stopped suddenly. Did something
> change, such as an update, or someone install any software on the XP box?
>
> Testing this internally trying to connect through the router won't do the
> trick, because it doesn't support 'U-Turns' You can, however, test it
> internally by connecting directly to the XP machine.
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum to benefit from collaboration
> among responding engineers, and to help others benefit from your resolution.
>
> Ace Fekay, MCT, MCSE, MCSA 2003 & 2000, MCSA Messaging
> Microsoft Certified Trainer
> (E-Mail Removed)
> http://twitter.com/acefekay
>
> For urgent issues, you may want to contact Microsoft PSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
>
>
>
>
>
>
>

"hedera" <(E-Mail Removed)> wrote in message
news:1C081234-1C68-48C8-B18D-(E-Mail Removed)...
> Ace,
> Thanks for the quick reply. I'm a little confused about the VPN server; I
> thought that the LinkSys router was the VPN server. It is, however,
> forwarding the ports through to the XP box, which then allows the
> connector
> to log in to the XP box using a userid and password configured for the
> purpose. (A shared userid and password, tsk; security by obscurity.) So
> I
> guess in that sense, the XP server is the VPN server. PPTP passthrough is
> definitely enabled on the LinkSys router.
>
> It's nice to know we don't need port 1701, I'll document that, thanks.
> Thanks also for confirming that my firewall test wasn't valid, I'll make a
> note. I'm obviously going to have to go back in and peer at the XP
> configuration. I don't know what changes or updates may have been made to
> the machine, I'm not even sure of the patch level. I need to write all
> that
> down.
>
> If GRE isn't correctly configured on the XP box, where would I look, and
> what should I see?
>
> Thank you again for your help, this is seriously impacting the nonprofit's
> ability to do business.
> ---
> hedera

As you've found, there are many little things that need to be configured
properly for VPN requests to be port re-mapped to an internal machine.

As for GRE on the XP box, it's not a matter of whether it is configured on
the XP box or not, but rather if the router is configured to port remap it
to the XP box, that is provided the XP box is configured properly to accept
VPN connections. I assume that you haven't tested it internally yet. You can
simply setup a VPN connection from one machine to the XP box internally by
simply supplying it's internal IP address.

To find out XP's SP level, simply right click My Computer, choose
properties, General tab.

As for hotfixes, one simple way is to look in Add/Remove Programs:
1.Access the Control Panel from the Start menu and open the Add Or Remove
Programs tool.
2.Select the Show Updates check box at the top of the Add Or Remove Programs
interface.
3.Scroll down to the Windows XP - Software Updates section.
4.Select a Hotfix entry that interests you. When the Hotfix entry expands,
choose the Click Here For Support Information link.
5.When you see the Support Info dialog box, click the link adjacent to the
Support Information entry.

You can also run the following command:
wmic qfe get Hotfixid

If you want it to send the list to a text file, run it wtih the following
additional command and then look in C: drive for HotfixList.txt.
wmic qfe get Hotfixid > c:\HotfixList.txt

More info on the WMIC QFE command, if you're intersted:

Get Hotfix Information Quickly with WMIC
http://windowsitpro.com/article/arti...with-wmic.html

Ace

I now must report that the VPN has suddenly begun working again. As far as I
know, no one has done anything to the computer since Monday when I poked at
it. I would very much like to know what happened but may never... if I do
get an answer I'll report it. Craziness.
--
hedera

Nature bats last.


"Ace Fekay [MCT]" wrote:

> "hedera" <(E-Mail Removed)> wrote in message
> news:1C081234-1C68-48C8-B18D-(E-Mail Removed)...
> > Ace,
> > Thanks for the quick reply. I'm a little confused about the VPN server; I
> > thought that the LinkSys router was the VPN server. It is, however,
> > forwarding the ports through to the XP box, which then allows the
> > connector
> > to log in to the XP box using a userid and password configured for the
> > purpose. (A shared userid and password, tsk; security by obscurity.) So
> > I
> > guess in that sense, the XP server is the VPN server. PPTP passthrough is
> > definitely enabled on the LinkSys router.
> >
> > It's nice to know we don't need port 1701, I'll document that, thanks.
> > Thanks also for confirming that my firewall test wasn't valid, I'll make a
> > note. I'm obviously going to have to go back in and peer at the XP
> > configuration. I don't know what changes or updates may have been made to
> > the machine, I'm not even sure of the patch level. I need to write all
> > that
> > down.
> >
> > If GRE isn't correctly configured on the XP box, where would I look, and
> > what should I see?
> >
> > Thank you again for your help, this is seriously impacting the nonprofit's
> > ability to do business.
> > ---
> > hedera
>
> As you've found, there are many little things that need to be configured
> properly for VPN requests to be port re-mapped to an internal machine.
>
> As for GRE on the XP box, it's not a matter of whether it is configured on
> the XP box or not, but rather if the router is configured to port remap it
> to the XP box, that is provided the XP box is configured properly to accept
> VPN connections. I assume that you haven't tested it internally yet. You can
> simply setup a VPN connection from one machine to the XP box internally by
> simply supplying it's internal IP address.
>
> To find out XP's SP level, simply right click My Computer, choose
> properties, General tab.
>
> As for hotfixes, one simple way is to look in Add/Remove Programs:
> 1.Access the Control Panel from the Start menu and open the Add Or Remove
> Programs tool.
> 2.Select the Show Updates check box at the top of the Add Or Remove Programs
> interface.
> 3.Scroll down to the Windows XP - Software Updates section.
> 4.Select a Hotfix entry that interests you. When the Hotfix entry expands,
> choose the Click Here For Support Information link.
> 5.When you see the Support Info dialog box, click the link adjacent to the
> Support Information entry.
>
> You can also run the following command:
> wmic qfe get Hotfixid
>
> If you want it to send the list to a text file, run it wtih the following
> additional command and then look in C: drive for HotfixList.txt.
> wmic qfe get Hotfixid > c:\HotfixList.txt
>
> More info on the WMIC QFE command, if you're intersted:
>
> Get Hotfix Information Quickly with WMIC
> http://windowsitpro.com/article/arti...with-wmic.html
>
> Ace
>
>

"hedera" <(E-Mail Removed)> wrote in message
news:0CC311B4-A415-48E7-BC9D-(E-Mail Removed)...
>I now must report that the VPN has suddenly begun working again. As far as
>I
> know, no one has done anything to the computer since Monday when I poked
> at
> it. I would very much like to know what happened but may never... if I
> do
> get an answer I'll report it. Craziness.
> --
> hedera
>

I actually performed a magic spell for you to get it working... Abbra
Cadabera! Zam! It works... see, how's that for magic?

Just kidding. Glad it's working for you now. Keep an eye on it and post back
if you have any other problems.

Cheers!

Ace

Sorry for extending this long thread, but there have been developments.
First, the old LinkSys router died hard the other week (to the point that the
local LAN was unavailable). We spent a week trying to get the VPN
passthrough to work on the existing VoIP router (LinkSys RT31P2), could NOT
get it going (everything else worked). We finally bought a a D-Link DIR-628
Rangebooster, I set it up last Friday, and the VPN worked as tested from a
remote client! Whee. Except that yesterday, my clients said, the VPN has
stopped working. I tested it with DynDNS's Open Port tool, and got this
error on port 1723:

An attempted connection to 70.231.230.210:1723 was refused. This typically
indicates that there are no services available on that port, but that it is
NOT being blocked by a firewall or your ISP.

I went into the office last night, and the router was up, the XP box was up,
I tested with Open Port and it said the port was open for business. I set up
a test connection using a laptop on the LAN and the internal IP, as you
suggested, and it worked. Today - it doesn't work, and I'm getting the
"refused" message from port 1723 again. This may be a router problem, as I
set the router up for remote management on port 4223, but every time this
happens, I can't open the admin console remotely; I'll take that up with
D-Link.

I've done a lot of reading on XP VPN servers and I'm now quite sure my XP
VPN server is correctly configured. WHAT could be going on?? Any
suggestions?? Why would it only work when someone is in the office?
--
hedera

Nature bats last.


"Ace Fekay [MCT]" wrote:

> "hedera" <(E-Mail Removed)> wrote in message
> news:0CC311B4-A415-48E7-BC9D-(E-Mail Removed)...
> >I now must report that the VPN has suddenly begun working again. As far as
> >I
> > know, no one has done anything to the computer since Monday when I poked
> > at
> > it. I would very much like to know what happened but may never... if I
> > do
> > get an answer I'll report it. Craziness.
> > --
> > hedera
> >
>
> I actually performed a magic spell for you to get it working... Abbra
> Cadabera! Zam! It works... see, how's that for magic?
>
> Just kidding. Glad it's working for you now. Keep an eye on it and post back
> if you have any other problems.
>
> Cheers!
>
> Ace
>
>
>
>

Never mind. I did some remote troubleshooting over the phone, and we
established that DynDNS wasn't correctly reflecting the IP address - which
led us to check the configuration and discover that DDNS wasn't configured on
the router! We configured it, and the VPN immediately worked.

Apart from the fact that I swear on my mother's grave that I personally
configured that router with DDNS working, I now know why it wasn't working
yesterday, and why my test in the office yesterday did work despite that. I
don't know how DDNS got unconfigured; but that's a different issue... My
client says gremlins, and he may be right.
--
hedera

Nature bats last.


"hedera" wrote:

> Sorry for extending this long thread, but there have been developments.
> First, the old LinkSys router died hard the other week (to the point that the
> local LAN was unavailable). We spent a week trying to get the VPN
> passthrough to work on the existing VoIP router (LinkSys RT31P2), could NOT
> get it going (everything else worked). We finally bought a a D-Link DIR-628
> Rangebooster, I set it up last Friday, and the VPN worked as tested from a
> remote client! Whee. Except that yesterday, my clients said, the VPN has
> stopped working. I tested it with DynDNS's Open Port tool, and got this
> error on port 1723:
>
> An attempted connection to 70.231.230.210:1723 was refused. This typically
> indicates that there are no services available on that port, but that it is
> NOT being blocked by a firewall or your ISP.
>
> I went into the office last night, and the router was up, the XP box was up,
> I tested with Open Port and it said the port was open for business. I set up
> a test connection using a laptop on the LAN and the internal IP, as you
> suggested, and it worked. Today - it doesn't work, and I'm getting the
> "refused" message from port 1723 again. This may be a router problem, as I
> set the router up for remote management on port 4223, but every time this
> happens, I can't open the admin console remotely; I'll take that up with
> D-Link.
>
> I've done a lot of reading on XP VPN servers and I'm now quite sure my XP
> VPN server is correctly configured. WHAT could be going on?? Any
> suggestions?? Why would it only work when someone is in the office?
> --
> hedera
>
> Nature bats last.
>
>
> "Ace Fekay [MCT]" wrote:
>
> > "hedera" <(E-Mail Removed)> wrote in message
> > news:0CC311B4-A415-48E7-BC9D-(E-Mail Removed)...
> > >I now must report that the VPN has suddenly begun working again. As far as
> > >I
> > > know, no one has done anything to the computer since Monday when I poked
> > > at
> > > it. I would very much like to know what happened but may never... if I
> > > do
> > > get an answer I'll report it. Craziness.
> > > --
> > > hedera
> > >
> >
> > I actually performed a magic spell for you to get it working... Abbra
> > Cadabera! Zam! It works... see, how's that for magic?
> >
> > Just kidding. Glad it's working for you now. Keep an eye on it and post back
> > if you have any other problems.
> >
> > Cheers!
> >
> > Ace
> >
> >
> >
> >

"hedera" <(E-Mail Removed)> wrote in message
news:9DD7EE87-7276-4E1B-993D-(E-Mail Removed)...
> Never mind. I did some remote troubleshooting over the phone, and we
> established that DynDNS wasn't correctly reflecting the IP address - which
> led us to check the configuration and discover that DDNS wasn't configured
> on
> the router! We configured it, and the VPN immediately worked.
>
> Apart from the fact that I swear on my mother's grave that I personally
> configured that router with DDNS working, I now know why it wasn't working
> yesterday, and why my test in the office yesterday did work despite that.
> I
> don't know how DDNS got unconfigured; but that's a different issue... My
> client says gremlins, and he may be right.
> --
> hedera
>

Maybe it was Stripes! (From the movie, Gremlins)!

Make sure you backup the DLink config to a file, now that it's configure
correctly.

And I'm happy to hear that it's now working. Thanks for the update!!

Ace

I wish that had been the last update. The unspeakable thing went up and down
for the next 2 days. It seemed that it would only work when someone was
actually in the office. Finally on the 30th, one of the officers went into
the office and replaced - are you ready for this? - the telephone cords, and
the DSL filter. And it all came up, and it's been running like a clock
since. Gah.
--
hedera

Nature bats last.


"Ace Fekay [MCT]" wrote:

> "hedera" <(E-Mail Removed)> wrote in message
> news:9DD7EE87-7276-4E1B-993D-(E-Mail Removed)...
> > Never mind. I did some remote troubleshooting over the phone, and we
> > established that DynDNS wasn't correctly reflecting the IP address - which
> > led us to check the configuration and discover that DDNS wasn't configured
> > on
> > the router! We configured it, and the VPN immediately worked.
> >
> > Apart from the fact that I swear on my mother's grave that I personally
> > configured that router with DDNS working, I now know why it wasn't working
> > yesterday, and why my test in the office yesterday did work despite that.
> > I
> > don't know how DDNS got unconfigured; but that's a different issue... My
> > client says gremlins, and he may be right.
> > --
> > hedera
> >
>
> Maybe it was Stripes! (From the movie, Gremlins)!
>
> Make sure you backup the DLink config to a file, now that it's configure
> correctly.
>
> And I'm happy to hear that it's now working. Thanks for the update!!
>
> Ace
>
>