Configuring The MSN Arescom NetDSL 800

There has been a few threads discussing the configuration of the Arescom NetDSL 800 DSL modem. However, I believe that there needs to be a distinction made between those using a 'standard' NetDSL 800 and those using the NetDSL from MSN. This thread is for those who have received the NetDSL from MSN.

I just received my NetDSL 800 from MSN last week. I have been wanting to reconfigure it because I want to change the LAN's IP addressing scheme (IP address range and netmask). However, I have not been able to do so. Here are the details of what I have found while attempting to do so.

MSN has configured the NetDSL to use a base IP address scheme of 192.168.1.x with a netmask of 255.255.255.252. This configuration only allows two IP addresses, 192.168.1.1 and 192.168.1.2. The router takes the first address while the device (PC or router) takes the second. If you have a router, which I do, this does not pose a problem. However, if anyone was planning to hookup a hub or switch to the NetDSL so multiple PC's could access it, they are in for a surprise.

MSN has also configured two specific services on the NetDSL: 20 (FTP) and 80 (HTTP). When accessing the ports from the PPP interface, the NetDSL forwards both ports to the device (PC or router) attached, which allows for someone to setup FTP or HTTP services on a PC. When accessing the ports from the LAN interface, you get the NetDSL status page (port 80) but you get a connection refused when accessing FTP (port 20).

I did a port scan on both the PPP and LAN interfaces and no other ports are open (I did a range of 1-65535 on the port scan).

I have attempted to use the NetDSL 800 Manager software to configure the NetDSL 800. However, it never finds the modem. I believe this is a result of the telent service (port 23) not being active on the NetDSL. Using telent, I can access a PC that is behind the NetDSL from a PC on the Internet. Therefore, we can assume that the NetDSL is not blocking the port for normal access.

I also attempted to accessing the configuration by using FTP with PASV using ports 20 and 80 but to no avail.

In a last ditch effort to find out how I could get access to the NetDSL configuration, I called MSN support and requested they help me through a configuration change. The reason I submitted was that my work VPN service also used the 192.168.1.x IP space and I was having problems accessing network resources with both the VPN and NetDSL using the same address space. The level 1 tech support person I talked to said that he thought I could use the Arescom software (NetDSL Manager) to do so. I asked about the 'password' and he said that the default one had not been changed. Since it was clear that he had not dealt with configuring the NetDSL before, I played dumb and said thanks, I will look into it.

Considering all of the findings listed above, I am not sure that the NetDSL sent out by MSN can be re-configured. The only thought I have left would be a special FTP login sequence on either the PPP or LAN interfaces but I am not familiar enough with FTP to be sure.

If anyone has any thoughts, I would appreciate it. Also, I hope the above info can be of use to those trying to do the same thing I am.

First, the handiest version of the NetDSL manager is probably 5.2.1 »bespin.org/~merwin/arescom/NetDS ··· ager.exeThe MSN version has this first image for its LAN configurationThe Arescom 5.2.1 version has the extra DHCP and other features available.

The one thing the MSN version of manager has is a tab to turn on multi user mode... it can be done via telnet with

set multi_user on

This is my modem's configuration file that supports multiple local IPs.(password and modem names replaced by @@@@s, these are configured via the Manager itselfThe VPI and VCI are set for my ameritech account )

Ok, I tried the 'MSN' version of the NetDSL Manager and it did not locate the modem. In reviewing the network traffic, I saw that the manager was doing a broadcast on port 9833 in an attempt to locate the modem. However, the modem did not respond.

I am going to try to force the manager to use port 20 instead of using port 9833 and see what happens.

Ok, I tried the 'MSN' version of the NetDSL Manager and it did not locate the modem. In reviewing the network traffic, I saw that the manager was doing a broadcast on port 9833 in an attempt to locate the modem. However, the modem did not respond.

I am going to try to force the manager to use port 20 instead of using port 9833 and see what happens.

I attempted to try and use a different port with the NetDSL manager but there are no configuration files or registry settings that can be changed. I also tried to pass the port in on the startup to no avail.

I called Arescom to see if they knew of a way to change the port used by the manager software and they said that it could not be changed.

The question remains, how is MSN configuring the modem? My best guess right now is that they have a modified version of the manager software which uses a different port than 9833.

It looks as if I will need to call MSN back and see if they will be willing to assist. I doubt it though.

What are the Firmware Versions on your MSN Modem? Mine Says 5.4.0 VUE_MSN with a date of July 11th 2001. I have been experiencing the same problems. Can't seem to get into the modem at all. That is, during the 5% of the time it does work.

I would be willing to bet that is the reason. I am not sure if it is just smoke, but a couple of the techs I have talked to said that the modem is configured, then the "key" is locked inside. If there is a problem they won't reconfigure, they will just send a new modem configured differently.

slightly OT, but the first quote I got after posting to this site was "There is always free cheese in a mouse trap." Now I can't get that out of my head every time I have to call MSN tech support.

The reason I chose the MSN/Qwest setup was for the learning experience. I have Cox@Home cable service and I wanted to see DSL and cable side by side. The experience has been worth it.

I called MSN today and canceled my service. When asked why, I explained the fact that I have a home alarm system which is interfering with the DSL service and that the person who took my order (Qwest Rep) never mentioned this as an issue. They understood.

I will be writing this experience up as an ISP post over the next few days.

Why get involved with the MSN product? I just Got my Qwest DSL installed on 9/11 with Blarg as ISP. Qwest sent me a Cisco 678 and I'm up and running. The cheese wasn't free. But i'm only paying a few $ a month more than I would be for MSN..

I just got my Arescom 800 from MSN this week, and I am having the same problem. I can't connect to the darn thing with telnet etc. I can bring up the web page, but there is no way to reconfigure. I have tried the netdsl 800 manager and it doesn't detect the router. Is there any way to change the firmware perhaps? Or does anyone know how to access this things configuration. My firmware version is 5.4.0-VUE-MSN... This sucks.

On these Arescoms, you have to make sure your IP address for your NIC is 192.168.1.xxx but make sure the last number is not 1. The IP of the modem is usually 192.168.1.1. you should be able to telnet into the modem..

It may be configured from the dark side.»cpeconfig.dsl.msn.com/englishcpecfg.exe and cpecfg.ini are in the root of the MSN cd.I cannot get DCC send to work in mIRC, a windows client for Internet Relay Chat. MSN, the f*#$ers, said to contact the mIRC client for assistance. I told them I am an expert on configuring the client and have done so, with other ISP's. MSN also referred me to Arescom for help for MSN's proprietary hardware, arrgg. I avoided asking about NAT information, possibly avoiding a heart attack of a unqualified technician. Sniffing revealed little. »192.168.1.1/msninfo.htm returns17269338@msndsl.netUpUp

My neighbor got his Arescom from MSN/Qwest this past week. Over the weekend we tried everything mentioned in the above posts with NO SUCCESS. Well, if we configure his PC as 192.168.1.2, then it works, but he has two more computers to get up and going.

HTTP to 192.168.1.1 displays a page with all the settings, but no way to change them. This was using the browser manager referenced above.

Telnet to 192.168.1.1 is refused.

Only one positive note: With the single PC hooked up to the Arescom, we got 538kb/sec download speed from DSLReports speed test.

Apparently, the newest batch of Arescoms being sent out are locked down.

MSN broadband is using a whats called a "walled garden" aproach to new subscribers. The Qwest migration customers will retain their old method of connection and are not withing the walled garden. The Arescom new customers are recieving is not actually and arescom 800, they are an arescom 860. The 860 is specially made for MSN and is not configuable by the user. About the only thing you can do with it is reset it to the factory defaults by going to 192.168.1.1/reset.html

One more thing, because of the "walled garden," the arescom 860 is the only DSL modem that you will be able to use with new MSN DSL service. If you have any more questions about the arescom, post them up. I've found out quite a bit about it and I'll see what I can do for answers.

The arescom 860 is not designed for the high end user who likes to tinker with settings. The built in firewall on the 860's has already been disabled. Anyone that has signed up for MSNDSL powered by qwest (Not including cusotmers that had previous DSL servive with qwest and migrated to MSN)will be contained within the walled garden. The walled garden will act as a firewall, but I'm not exactly sure how it will be set up.

Unfortunately like mr whipples was saying, the new msn arescom dsl modem is an arescom 860 not 800, and neither the netdsl manager nor telnet are able to connect to the modem. I am really annoyed with this thing.. and am seriously considering finding a different isp becuase this modem sucks so bad.

dwhit, make sure to leave the Arescom hooked up and trained all the time. As long as the lights on the Arescom look good, there isn't much more that you can do. I'm asuming that your probably getting the "modem not plugged in correctly" error when your trying to install the software (I very common, missleading, and anoying error message). Basically, the server needs to be reconfigured before you'll be able to connect. You'll want to try and re-install the software periodically. Once the problem has been taken care of, the install should got through ok.