I'm running a Windows 2000 server with an internal dsl modem (isdn - Efficient networks 2060 vpi 0,8 dsl adapter). After I installed Netbeui, File sharing, microsoft networking and enabled my network (shared folders were visible between server and win98 client!), the win2000 server started crashing but only when my dsl internet connection was on. The "Stop Error" message was "...Driver_IRQL_NOT_Less_or_equal ..ptserial.sys" ptserial.sys is a modem driver. So it's obvious that the modem drivers are imcompatible with the network drivers. I uninstalled Netbeui, File sharing, microsft networking and disabled my network card. This fixed the problem. Now my question is - what do I do next? I mean I bought a new pc (came with Win98) and want to connect it to the win2000 server for file and internet sharing.

You need to get the correct drivers. I have had several win2k boxes and servers take a dive with DSL Modems. However, getting the correct driver resolved all issues as it is the only choice. You might want to take a look at getting Direct TV DSL which uses a Gateway and NO internal modem. Regards, Charles www.sigfl.net

Do yourself a favor and get an external DSL/Cable Modem. The externals are way easier and you don't have to deal with all the garbage from DSL providers. It makes it easier to use a Linksys NAT box (Yes I know there are others too) and have your sever fully firewalled as opposed to half and half and server having to run NAT and server apps while also being exposed by default. Internal DSL is one of the worst things a DSL provider can give you .. however it is the cheapest thing.

I don't think it's the dsl modem anymore, except for the ptserial.sys stop error message. My win2000 server crashes even when the dsl is disconnected, when trying to move files from one machine to the other (I am able to see the 2 pcs in network neighborhood). I even thought it might be the cable, but I did buy an x-over cable, unless they send me the wrong one (how could I know?) I am clueless, as it is right now it could be many things: the NIC, the cable, protocols, drivers.. don't know. My first home network: what a pain!