Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I'm trying to make this baby work with Windows XP 2600 and 3Com ADSL PCI Homeconnect 3CP3617.
My ISP uses only PPP over ATM or PPPoA. If anyone has any sugestion, I'd be gald to hear from you.
Thanks!
kibe@gamescorner.com.br

hello there
I am using that model dsl modem card with windows xp rc 2526. Bellsouth is my ISP. I had to load windows 2000 on my harddrive clean, then install bellsouth PPPoE software. After I made sure that my dsl card worked perfectly, I upgraded to windows xp. Now here's the trick: after finishing the upgrade, do not shut down or hibernate your pc. Your 3com dsl modem should work as long as you never shut down your pc. It seems that the networking protocols in windows xp are completely different than on previous versions of windows, so forcing windows xp to use windows 2000 or 98 software can cause a conflict. Wait until more applications are released for windows xp and then you can really upgrade to it.

Thanks for your hints.
I got the modem to work by instaling the Win 2k drivers. Then I used a file that was in my Win 2k direcotory, atmlane.sys and overwrote the file in WINDOWS/SYSTEM32/DRIVERS and the other in WINDOWS/SYSTEM32/DLLCACHE.
It worked perfectly. I had the system to reboor twice and when I was using Media Player, the system crashed. I had to press the reset switch to make it work again.
As soon the system started again, I gad those 721 errors again. I have no idea what to do next... :-(

I have BellSouth as my ISP also. And I'm using the 3Com ADSL PCI Homeconnect 3CP3617. Before I even attempted to install XP I called and was told that BellSouth won't support XP till October. But I installed it anyway just to see if there wasn't a setting to play with only to uninstall it because my DSL didn't work.
So I've decide to wait till BellSouth has support for XP available

Hola, engo un router 3com 812 con conexión ADSL y no hay manera de que me funcione el sistema FTP.
Comentado con el ISP, no encuentran la solución.
Si soys tan amables y me podéis ayudar,
os quedaré agradecidos,
Felipe Ortega.

Took a while and a lot of twiddling but got my 3com internal pci working with xp. Download speed of 916.4 kilobits per second.
RASPPPOE is the ticket.

Hello, my name is Leonardo and I read your post about getting 3Com's HommeConnect PCI ADSL modem to work with XP, using RASPPPOE. I have literally been trying to get ADSL to work with XP, in vain, for weeks and have also tried a few times with RASPPPOE. I have also seen several people on the Net with the same problem. I was wondering if you could please give me a more detailed explanation of how to do it. That way, not only would I be able to get it to work, but I would also post your solution, if you don't mind, to other places to help out other people as well. :)
Thank you very much,
...LEo

Hello everybody! I upgraded from ME to XP and my internal pci dsl modem's (3CP3617)driver didn't work, I checked on the device manager and there was the error. I tried installing the driver for W2000 and the driver worked but the qick view still was red. I Called bellsouth and they said that there's not and won't be a driver and that I had to buy an ethernet card: 160$ !!! no way! somebody help me!!! thanx!

Problem solved and you dont need any 3rd party software. I got this off a newgroup. I tried it. It works. I had to reinstall Win XP first because I had screwed up the settings so bad. Anyway....
_____________Hello all,
I have been fighting with WinXP and the 3Com 3CP3617 internal PCI Modem most
of the week and finally got it to work. The mistake I made was going by the
Bellsouth manual and installing "PPP Over ATM(LLC)" when installing the
Bellsouth software.
The best I could do was get a green "line is up" icon but never connect.
Once I uninstalled the Bellsouth software and installed it again selecting
the " Ethernet(Bridge/PPP Over Ethernet" option I got it to work.
I let WinXP search the CD for the driver and installed the 3 Com Adsl
LAN/RFC1483(Win 2000) and then set up a Network Connection using these
instruction Bob Carrick posted here the other day (Thanks Bob)1) Create a new connection
2) Choose Connect to Internet
3) Create Manually (option 2)
4) Connect Using Broadband Connection that requires a username and password
5) Give it a name (IE: DSL)
6) Put in your name and password (Don't forget to add your ISP's domain as
part of your userid, IE: for Verizon it is userid@verizon.net)
7) Right click and choose properties for that new connection
8) Empty entry in Service name to let it use Wan PPPoE
9) Go to Networking Folder, choose Internet Protocol TCP/IP
10) Choose Properties - Make sure everything is auto assignedThis connected right away and works great, faster than Win98SE
connection...hope this helps someone

I've the same problem: with the 3CP3617 (3Com Pci Adsl Modem) I can't use the PPPoATM protocol with W2k drivers on XP!
I continue get the 721 error....
--Simon

People,
I contacted 3Com about the 3CP3617. An attendent told me that 3COM has discontinued the ADSL production line.
But in the site, there is an information that the company has to support the product until August 2002.
So, we need to send e-mails and fill the forms in the 3Com site to get the drivers to Windows XP.
I don't have doubts that the Windows XP is better for all.
Thanks.

Hey, guys!
We really should unite for this. We should send emails by the tonnes and fill out & send every driver request form we come across, like Rodrigo said above. Where should we send e-mail to, and what's the URL for that form?Thanks,
Leo.

Hey guys,
We should send email to 3Com by this address:
http://csoweb4.3com.com/dsl/3cp3617b/contactus/
... and the 3CP3617 page is:
http://www.3com.com/products/en_US/detail.jsp?tab=support&pathtype=support&sku=3CP3617B
We have to get this driver for Windows XP!
Thanks.
Rodrigo.

Hey guys,
This is the email address to contact 3COM ADSL support:
clientadsl@3com.com
Let's send emails to them!
Thanks.
Rodrigo

I just sent an email to them asking them to provide WinXP drivers, everyone else should do the same!

this post is in response to Blackstrat regarding his post on Oct. 27 ........i tried the simple steps outlined in your post and i'm pretty sure that it would work....BUT.....the main problem that i think most of us r running into is that to this date (Nov. 7) there are no XP drivers for this particular 3com internal modem.........if u have this internal modem...........i'm VERY curious as to what driver set u r using

Hi guys,
I've sent the mail, but the 3com support center said that they haven't planned to do drivers for XP or give support for this or future operating systems.Someone have a good news for a 3rd party release of this drivers?
Bye Giorgio.

Here's the official response that I received from 3Com regarding the possible release of XP drivers for the PCI ADSL modem:
"There are no Windows XP drivers available for the PCI ADSL Modem. The ADSL product line
was discontinued in May 2001. 3Com will not be providing driver updates for future operating systems. 3Com is still providing support for this modem in the Operating Systems it was designed to work in. These OS's include Windows 98, ME ,NT 4.0 (service pack 3 and above) and Windows 2000. We are also still honoring the five year hardware warranty these cards have."Tough luck...
...LEo

I just want to echo what this guy said..........cuz.......this s--- worked.......i did it in a somewhat different way......but it works.........i've restarted several times and had no trouble.......here's what i did differently.......on my crappy dialup connection that i have on a seperate computer.......i went to ftp.bellsouth.net........username:software .......and password:download ..........then i went to the drivers folder....i downloaded several of these but the only one that works for the internal pci in xp is the 3rd download from the left on the top row "3com_pci_v10017d_win200.exe" download it......once downloaded ....unzip the files to any folder that you'll remember....now go to system properties and you'll notice that xp is currently seeing you're dsl as "atm network controller" double click on it and reinstall driver......direct the utilty to look for the driver in the directory that you unzipped the files into(......LAN/RFC1483)......follow the prompts to a happy driver set......now just do what this guy says in the steps outlined below........i will tell u that i'm using xp pro corporate and i don't have an analog modem installed in my system .....i've run into problems having both dsl and anolog in the same box.....i don't know if any of this makes a differnce but that 200 driver works HERE!!!!
Problem solved and you dont need any 3rd party software. I got this off a newgroup. I tried it. It works. I had to reinstall Win XP first because I had screwed up the settings so bad. Anyway....
_____________
Hello all,
I have been fighting with WinXP and the 3Com 3CP3617 internal PCI Modem most
of the week and finally got it to work. The mistake I made was going by the
Bellsouth manual and installing "PPP Over ATM(LLC)" when installing the
Bellsouth software.
The best I could do was get a green "line is up" icon but never connect.
Once I uninstalled the Bellsouth software and installed it again selecting
the " Ethernet(Bridge/PPP Over Ethernet" option I got it to work.
I let WinXP search the CD for the driver and installed the 3 Com Adsl
LAN/RFC1483(Win 2000) and then set up a Network Connection using these
instruction Bob Carrick posted here the other day (Thanks Bob)1) Create a new connection
2) Choose Connect to Internet
3) Create Manually (option 2)
4) Connect Using Broadband Connection that requires a username and password
5) Give it a name (IE: DSL)
6) Put in your name and password (Don't forget to add your ISP's domain as
part of your userid, IE: for Verizon it is userid@verizon.net)
7) Right click and choose properties for that new connection
8) Empty entry in Service name to let it use Wan PPPoE
9) Go to Networking Folder, choose Internet Protocol TCP/IP
10) Choose Properties - Make sure everything is auto assignedThis connected right away and works great, faster than Win98SE
connection...hope this helps someone

GULUM,I LOVE YOU MAN!!!!!!!!!!!....that plan using the PPPOE instead of the PPPOA worked like a charm with bellsouth and windows xp 2600!...This is frikken' great plus I've noticed a speed improvment too...man this is awesome,thanks a billion!If ya ever need anything...ms xp PLUS! whatever hit me up at lilgreg70@hotmail.com !! thanks again!

alright......it does work...but only about 43% of the time.......... and then you'll see the mighty giant XP PRO fall to it's knees.......i mean i even had task manager lock up on task manager........has anybody gotten this to work .........oh well...if anybody can find a way to get it to work 100% of the time.....please let me know

Hello all,
here's what i did differently.......on my crappy dialup connection that i have on a seperate computer.......i went to ftp.bellsouth.net........username:software .......and password:download ..........then i went to the drivers folder....i downloaded several of these but the only one that works for the internal pci in xp is the 3rd download from the left on the top row "3com_pci_v10017d_win200.exe" download it......once downloaded ....unzip the files to any folder that you'll remember....now go to system properties and you'll notice that xp is currently seeing you're dsl as "atm network controller" double click on it and reinstall driver......direct the utilty to look for the driver in the directory that you unzipped the files into(......LAN/RFC1483)......follow the prompts to a happy driver set......now just do what this guy says in the steps outlined below........i will tell u that i'm using xp pro corporate and i don't have an analog modem installed in my system .....i've run into problems having both dsl and anolog in the same box.....i don't know if any of this makes a differnce but that 200 driver works HERE!!!!
1) Create a new connection
2) Choose Connect to Internet
3) Create Manually (option 2)
4) Connect Using Broadband Connection that requires a username and password
5) Give it a name (IE: DSL)
6) Put in your name and password (Don't forget to add your ISP's domain as
part of your userid, IE: for Verizon it is userid@verizon.net)
7) Right click and choose properties for that new connection
8) Empty entry in Service name to let it use Wan PPPoE
9) Go to Networking Folder, choose Internet Protocol TCP/IP
10) Choose Properties - Make sure everything is auto assignedalright......it does work...but only about 43% of the time.......... and then you'll see the mighty giant XP PRO fall to it's knees.......i mean i even had task manager lock up on task manager........has anybody gotten this to work .........oh well...if anybody can find a way to get it to work 100% of the time.....please let me know
-----!!!!!DOES ANYBODY HAVE A FIX THAT WORKS AT LEAST 97% OF THE TIME................ONLY SAY YES IF YOU'VE TESTED THIS CONNECTION CONSTANTLY FOR A WEEK OR SO---------!!!!!!

Look at my posting here:
http://www.computing.net/windowsxp/wwwboard/forum/2227.html
the last one, you should find the solution you need ... hope it help

Hey I got on her and tried all the steps listed in the above. I was sending packets @ 128k but could not authenticate. I use citlink (citizens communications) They don't support PPPoE. They only support PPPoATM. So I am still stuck.
Thanks

I tried everything posted here and nothing has worked 4 me...
I think 3com is responsible for providing the drivers even if the product is discontinued...lets email them!!!

I have also tried installing it to use it as an Ethernet modem. But when you go to connect, it sits on the screen trying to connect through the "WAN miniport PPPoE" window. If anyone has a similar problem and has overcome it, please post your findings. Any other information would be greatly appreciated.

I don't know if this is of any use to you, but I have a 3com Dual Link ADSL *external* modem (usb/ethernet), and I found that I was able to get it working under XP by doing the following:
Install the Windows 2000 drivers, but not the application software which came with the modem. Download RASPPPoE from
http://user.cs.tu-berlin.de/~normanb/
but ensure you also download the 3com patch to go with it. It appears that the dialup software that 3com provides is not compatible with XP but RASPPPoE is.Having said all this, it might not work with the internal modems, but you may as well try it out!

Matt, did yours work? I have an external too but it keeps telling 678: Remote computer did not respond. How's is yours connected? by network card or usb?

This solved my problems with the 3Com ADSL internal modem and XP
http://computing.net/windowsxp/wwwboard/forum/5632.html

To answer Gulum (better late than never... I stopped looking in here once It started working for me.)
The post I wrote back in November works for me 97% or more of the time (I'd call it 100% but every OS glitches now and then) and have been using it steadily since then. I use the win2k drivers right off of the ftp site from Bellsouth.

Ok.... I am going to break it down because i don't want to type all that much.. for the 3 com modems....they aren't going to shiping them out any more.. they don't even make those modem's anymore... they didn't want to come out with xp drivers... there are bata drivers for xp... they can be found on bellsouth's ftp site... you may have to take your 3 com from your pci slot restart ...make sure that no softare is on you machine.. connect with 56K.. go to this site and download the drivers for the 3 com.... ftp://software:download@ftp.bellsouth.net/fastaccess/readme.html
it will tell you that there are no drivers for it but will give you some more info
Computer tech
this info is correct and very much so used...
read and find out for yourself

Connection working only for some minutes... I had that prob on my 3Com HomeConnect under win98SE. I solved it by setting a fix IP address to TCP/IP settings, something like 192.168.0.1 (not sure of this number exactly).

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |