Novell Home

NSBS 5 and DSL: Giving your Small Business the Internet at Blazing Speed

Novell Cool Solutions: Feature
By Alan Reay

Rate This Page

Reader Rating  stars  from 6 ratings

Digg This - Slashdot This

Posted: 7 Apr 2000 		 

We've had many requests for information detailing how to connect an NSBS 5 network to the Internet via DSL. It seems like every day more of you are finally able to obtain DSL service for your business, and you're not wasting any time trying to hook it up. And with good reason. With DSL, your users can connect to the Internet at unbelievable speeds, and as we all know, if they've got speed, they will worship the guy who gave it to them. Which translates into job security, and possibly chocolate. Let's take a look at what it's all about, and how you can get hooked up.

What is DSL, anyway?

Digital Subscriber Line (DSL) is a modem-like technology that transmits voice, video and data over regular copper telephone lines at blistering speeds. How blistering? Well, DSL gives you dedicated bandwidth that can be up to 278 times faster than a 28.8 Kbps modem, 143 times faster than 56Kbps modem, 62 times faster than ISDN and up to 4 times faster than a T1 connection. In our book, that's blistering.

There are many good resources on the web that will help you gain a background about this technology. Here are two good places to go if you want to know more.

Once you know all about it, of course you'll want it. Everyone does. But sadly enough, the service is not available everywhere yet. The first step is to determine whether your local phone company or broadband service provider offers DSL service. If it's available in your location, check with your local reseller of data networking equipment or systems integrator to buy a DSL modem, router or bridge. (Someday soon we expect you'll be able to buy everything you need for a DSL connection at your local retail computer store. Hasten the day?)

Once you've got DSL installed, the big question for Small Biz Cool Solutions readers is: how do I hook it up so my small business can access the Internet? Since DSL is becoming more and more available, we're seeing many requests for instructions on how to make it work with NSBS 5. So grab a Coke, shut your door, and let's get started.

NSBS 5 and the Internet

Novell Small Business Suite 5 provides access to the Internet through routing software. With the minimum of a single ISP account and Internet access set up from your server to your ISP, all users can send and receive e-mail from the Internet as well. Although you can connect your network to an ISP in several ways (dial-up connection, ISDN, Frame Relay, or DSL), we're going to concentrate on DSL in this article.

Get the Worksheet

Here's a handy worksheet you should print out now. It will help you collect the information you'll need to give your ISP so they can set up Internet access. It also shows you the device information you'll need in order to complete the setup using NICE.

The Process of Connecting Using DSL

Here is the entire process of connecting your system to the Internet using DSL. (Many of the rectangles are linked to relevant sections of the article.)

#hooked #isp #config #optiona #optionb #optionc #optiond #configuring #configuring #nice #dhcp

Server Installation Recommendations

It's important to know that you cannot configure DSL during the installation of NSBS. DSL is configured after the server has been installed. If you haven't already installed NSBS, do so now. The Express Server Installation is highly recommended over the Custom Server Installation. It vastly simplifies the process of connecting to the Internet, and all of the options outlined below are going to assume that you've done an Express Server Installation.

If you are installing a second server, you must do a Custom Installation. If you decide to (or must) do a Custom Installation, you should get the updated version of NICE and DHCPCFG.NLM to help you configure your server. You can get them here on the Downloadables page.

Choose the right configuration for you

The first thing to do is decide which configuration is right for you. There are four basic configurations that most people use. Your choice of configuration will determine many of the choices you'll make as you proceed through the setup, so let's explore all your options.

Option A: PPP Mode with Server as Gateway (Recommended)

PROS:
This is the most popular configuration, and for good reason. In this configuration, the server acts as a protective barrier between you and the Internet, so it is much more secure than other options. Also, you are isolated from the modem, so the modem doesn't have to "see" every bit of traffic, resulting in much more efficient performance. Another plus is that this configuration works best with most ISP's defaults, so it is less of a problem during the ISP setup phase. It's also cheaper than other configurations, because you don't have to purchase a unique IP address; you can use an IP address dynamically assigned from your ISP.

CONS:
In this configuration, if the server goes down, your users will lose access to the Internet (and their e-mail). Also, because you're running NAT (Network Address Translator), you can't do VPN (Virtual Private Networks). If you need to access your company's Intranet from a remote office, for example, this configuration isn't right for you.

Note: Using this configuration you can still use Remote Dialup, but cannot use VPN. With Remote Dialup you access your network by dialing into a modem on the server. With VPN, you dialup to an ISP, then connect to your network over the Internet.

For the Worksheet

The numbers in the illustration above indicate information you'll need to enter when running the Internet Connection portion of NICE. Jot down the information for the following questions:

  1. ISP's DNS Address (They should have already given this to you.)
  2. Your Assigned IP Address (As diagrammed, this is 10.0.0.2.)
  3. Board Name (See Note 3)
  4. Router IP Address (As diagrammed, this is 10.0.0.1)

Notes:

  • "Dynamic Address" indicates which IP Addresses are configured through DHCP.
  • "Static Address" indicates that the IP Address is manually assigned. It does NOT indicate Routable Static IP's purchased from your ISP.

Important Notes about Option A:

  1. We strongly recommend you do an Express Server Installation if you plan to use DSL in any configuration. Custom Server Installations can cause some problems if the DNS/DHCP objects are not placed in the proper places, or if it's not installed. (DHCPCFG5, NEAT, and NICE all expect these objects to be in the same Organization as the Admin user.)
  2. Make sure that the static address of the DSL Modem is different from the static address of your second Network Board.
  3. You must have two Network Boards for this configuration. One where the DSL modem runs into the NSBS 5 server, and one where the NSBS 5 server runs out to the Hub. The Network Boards need to be installed before you run NICE (Novell Internet Connection Expert). You can install them before or after NSBS has been installed. Also, the board must be configured in INETCFG before NICE is run.
  4. You may disable DHCP on the server and have the xDSL modem provide DHCP services, but this is not recommended.

Option B: PPP Mode with Server off Hub

PROS:
Since the clients connect directly with the hub and are not filtered through the server, you will always have access to the Internet. Although this is not as secure a configuration as Option A, it may be a good choice for some businesses.

CONS:
This configuration is very insecure. Your Clients are able to communicate directly to the Internet via the hub, without any security intervention by the server. Also, since the modem has to see every bit of traffic, extra processing time is required so you may experience a performance hit in this configuration. As with Option A, because you're running NAT (Network Address Translator), you can't do VPN (Virtual Private Networks). If you need to access your company's Intranet from a remote office, for example, this configuration isn't right for you.

For the Worksheet

The numbers in the illustration indicate information you'll need to enter when running the Internet Connection portion of NICE. Jot down the information for the following questions:

  1. ISP's DNS Address (They should have already given this to you.)
  2. Your Assigned IP Address (As diagrammed, this is 192.168.0.1, the default IP address of the server.)
  3. Board Name (Use INETCFG to find the name of the indicated NIC.)
  4. Router IP Address (As diagrammed, this is 192.168.0.2)

Notes:

  • "Dynamic Address" indicates which IP Addresses are configured through DHCP.
  • "Static Address" indicates that the IP Address is manually assigned. It does NOT indicate Routable Static IP's purchased from your ISP.

Important Notes about Option B:

  1. We strongly recommend you do an Express Server Installation if you plan to use DSL in any configuration. Custom Server Installations can cause some problems if the DNS/DHCP objects are not placed in the proper places, or if it's not installed. (DHCPCFG5, NEAT, and NICE all expect these objects to be in the same Organization as the Admin user.)
  2. You only need one Network Board for this configuration.
  3. In this configuration, you must manually change the DHCP configuration on the Server. Run the DNS/DHCP Configuration tool provided with NetWare. Change the Router to 192.168.0.2
  4. It's possible to disable DHCP on the server and have the xDSL modem provide DHCP services, but this is not recommended.

Option C: Bridging Mode with Server as Gateway

PROS:
In this configuration, the server acts as a protective barrier between you and the Internet, so it is very secure. Also, you are isolated from the modem, so the modem doesn't have to "see" every bit of traffic, resulting in much more efficient performance. You will need to use this option if that is the mode your ISP uses. If you have a choice, we can't think of a reason to choose it over PPP Mode. With Bridging mode, the DSL modem is not doing any real processing, it's just passing packets from one topology (Ethernet) to another (DSL). In PPP mode, the DSL modem is actually acting as a router/gateway.

CONS:
In this configuration, if the server goes down, your users will lose access to the Internet (and their e-mail). The dynamic nature of this configuration can introduce problems during operation. Most ISPs are migrating away from Bridging Mode. So, if you choose this configuration, you may be forced to change it in the near future.

For the Worksheet

The numbers in the illustration above indicate information you'll need to enter when running the Internet Connection portion of NICE. Jot down the information for the following questions:

  1. ISP's DNS Address (They should have already given this to you.)
  2. Your Assigned IP Address (As diagrammed, this address will be assigned dynamically, so any address entered will be overwritten by DHCPCLNT.NLM. You must still enter a valid IP Address in NICE. E.g. 10.0.0.1)
  3. Board Name (See Note 3)
  4. Router IP Address (As diagrammed, this address will be assigned dynamically, so any address entered will be overwritten by DHCPCLNT.NLM. You must still enter a valid IP address in NICE. E.g. 10.0.0.2)

Notes:

  • "Dynamic Address" indicates which IP Addresses are configured through DHCP.
  • "Static Address" indicates that the IP Address is manually assigned. It does NOT indicate Routable Static IP's purchased from your ISP.

Important Notes about Option C:

  1. We strongly recommend you do an Express Server Installation if you plan to use DSL in any configuration. Custom Server Installations can cause some problems if the DNS/DHCP objects are not placed in the proper places, or if it's not installed. (DHCPCFG5, NEAT, and NICE all expect these objects to be in the same Organization as the Admin user.)
  2. In both Bridging mode configurations, you have to use DHCPCLNT.NLM or have your ISP assign you a static address. But be warned: DHCPCLNT can be tough to use. It works, but it ain't pretty. There are just so many things that can go wrong with it, we hate to recommend it to anyone. But since we DO need it in some cases, it's there to use.
  3. You must have two Network Boards for this configuration. One where the DSL modem runs into the NSBS 5 server and one where the NSBS 5 server runs out to the Hub. The Network Boards need to be installed before you run NICE. (The Internet Connection Expert). You can install the second board before or after the NSBS Server has been installed. Also, the board must be configured in INETCFG before NICE is run.

Option D: Bridging Mode with Server off Hub

PROS:
You will need to use this option if that is the mode your ISP uses. If you have a choice, we can't think of a reason to choose it over PPP Mode. With Bridging mode, the DSL modem is not doing any real processing, it's just passing packets from one topology (Ethernet) to another (DSL). In PPP mode, the DSL modem is actually acting as a router/gateway.

CONS:
This configuration is very insecure. Your Clients are able to communicate directly to the Internet via the hub, without any security intervention by the Server. Also, since the modem has to see every bit of traffic, extra processing time is required so you may experience a performance hit in this configuration. Also, the use of a switch is highly recommended in this configuration. The dynamic nature of this configuration (Dynamic Addresses are used extensively) can introduce problems during operation.

For the Worksheet

The numbers in the illustration indicate information you'll need to enter when running the Internet Connection portion of NICE. Jot down the information for the following questions:

  1. ISP's DNS Address (they should have already given this to you)
  2. Your Assigned IP Address (they should have already given this to you)
  3. Board Name (Use INETCFG to find the name of the indicated NIC)
  4. Router IP Address

Notes:

  • "Dynamic Address" indicates which IP Addresses are configured through DHCP.
  • "Static Address" indicates that the IP Address is manually assigned. It does NOT indicate Routable Static IP's purchased from your ISP.

Important Notes about Option D:

  1. We strongly recommend you do an Express Server Installation if you plan to use DSL in any configuration. Custom Server Installations can cause some problems if the DNS/DHCP objects are not placed in the proper places, or if it's not installed. (DHCPCFG5, NEAT, and NICE all expect these objects to be in the same Organization as the Admin user.)
  2. It is highly recommended that you use a switch with this configuration. Otherwise all local network traffic will also go out over your xDSL connection.
  3. It is also recommended that you NOT run DHCP or NAT on the server. You will have to turn off both of these services.
  4. This configuration only requires one Network Board.

Configuring your Network Board (aka NIC Card)

Editor's Note: Network Boards are often referred to as NIC Cards, which, since NIC is an acronym itself, is a redundant abbreviation for Network Interface Card Cards. We'll be calling them Network Boards throughout this article, as part of our never-ending effort to snuff out confusion whenever possible.

Once you've chosen your configuration, you need to configure your network board for a DSL Connection. If the configuration you've chosen calls for two Network Boards in the server, the next thing to do is install the second Network Board. Shutdown the server, power it off, and install the Network Board. Follow the card manufacturer's instructions.

  1. Install the network board in the server and connect the DSL modem to the board.
  2. Restart the server.
  3. At the server console prompt, enter INETCFG

    If you are prompted to import the drivers from the AUTOEXEC.NCF file, click Yes.
    If you are prompted to choose a Fast setup method, select No, Use the Standard Method.

  4. For a 1-NIC configuration, write down the name of the listed board. (For example: E100B)
  5. For a 2-NIC configuration, select INS.
  6. Select Boards, then press Insert.
  7. Select the appropriate board/driver.

    If your network board does not appear on the list, do the following:

    1. Press Insert.
    2. Insert the diskette into drive A: and enter the path to the driver.
  8. In the Board Name field, enter a board name such as DSLDIAL. Using DSL in the name is recommended.
  9. Enter the appropriate board configuration information (I/O Base, Interrupt, Speed Rating, and other needed information).

    If you need to find a slot number, toggle to the console screen and load the board manually. Any setting you are prompted for confirmation on should be configured in the board configuration in INETCFG.

  10. Press Esc to return to the Configured Boards screen, saving changes as prompted.
    The board status now reads Enabled.
  11. Press Esc to return to the Internetworking Configuration menu.

Caution: INETCFG must NOT be open on the server for the Internet Connection Expert (NICE) to function properly. Make sure that INETCFG is not open before continuing.

Manually Configuring Internet Access

If you're using a network board that isn't supported by NICE, you need to manually install the appropriate drivers and manually configure your Internet access. For a list of boards that are certified for use with the Novell Small Business Suite Internet access, see the Novell Labs Web site. In the Solution Category, select LAN adapters.

Configuring DHCP

Configuring DHCP with your Domain Name and your ISP's name servers requires several steps.

  • Installing the DNSDHCP Management Console
  • Loading the DNSDHCP Management Console and configuring the DHCP server options.

Installing the DNSDHCP Management Console

To install the DNSDHCP Management Console:

  1. Log in to the network as user Admin.
  2. Run NetWare Administrator one time to register any settings.
  3. Install the DNSDHCP Management Console by running SYS:PUBLIC\DNSDHCP\SETUP.EXE.
  4. When prompted, check the Copy Snap-In Files check box. The NetWare Administrator files are located in SYS:\PUBLIC\WIN32.
  5. When the installation is complete, restart the computer.

Configuring the DCHP Server Options

To continue configuring DHCP:

  1. Log in to the network as user Admin.
  2. Double-click the DNSDHCP icon on your desktop.
  3. When prompted to enter the NDStree name, accept the default.
  4. Click DHCP Service.
  5. Select 192.168.0.0 servername_subnet.
  6. Click Other DHCP Options > Modify.
  7. In the Available DHCP Options, select Domain Name Server (Code 6).
  8. Move the selected option to Selected DHCP Options by clicking Add>>.
  9. In the Selected DHCP Options, select Domain Name Server (Code 6).
  10. Click Add...
  11. Enter the DNS IP address provided by your ISP. Repeat this step until you have entered all addresses provided by your ISP.
  12. Press OK to accept the changes.

Configuring DHCP for GroupWise (Optional)

To be able to send e-mail to an Internet address:

  1. Log in to the network as user Admin.
  2. Double-click the DNSDHCP icon on your desktop.
  3. When prompted to enter the NDS tree name, accept the default.
  4. Click DHCP Service
  5. Select 192.168.0.0 servername_subnet
  6. In the Domain Name field, enter your domain name assigned by your ISP.

Initializing the Changes

To make the change effective in the server:

  1. At the console prompt, enter
    UNLOAD DHCPSRVR
    DHCPSRVR
  2. After the changes are done at the server, notify each user to shut down and restart their computer.

Setting the Foreign ID for GWIA in GroupWise

In order for GWIA in GroupWise? to accept incoming messages from the Internet:

  1. Log in to the server as user Admin.
  2. Run NetWare Administrator.
  3. Adjust the scope of the browser to the root of your NDS tree.
  4. Select GroupWise > treename_DOM > GWIA.
  5. In the Foreign ID field, enter your Domain name.
  6. Click OK.

Restarting the Server

In order for the changes to take effect, shut down and restart the server.

  1. Make sure everyone is logged out of the server.
  2. At the console prompts, enter DOWN
  3. Turn the computer off, wait about ten seconds, then turn it back on again. The computer should restart and load the server software.

Running NICE (Novell Internet Connection Expert)

After the network boards have been configured, you can run Novell Internet Connection Expert (NICE). NICE walks you through configuring Internet access for three types of connection devices, modems, ISDN, and DSL connections. NICE gathers the required information in to a script then runs that script to make the changes to the server using the INETCFG utility.

Get out the worksheet that you've so carefully filled in. Here's where it pays off...



  1. From a workstation, login to the server as admin. Run NICE using one of these two access points:
    • Start NICE by clicking the Set up Internet Access task on the Quick Setup Task screen in NEAT.
      OR
    • Click Tasks > Run Novell Internet Connection Expert on the tool bar in NEAT.
  2. Choose the server to be configured, then Next.
  3. Select DSL, then Next.
  4. Enter the ISP's DNS Address.
  5. Enter your domain name.
    (If you don't have a domain name, just enter anything you want in here. For example, Mybiz.net)
  6. Enter the appropriate IP address as indicated by the illustration for the configuration you chose.
    (If you will have a dynamic Address, you will have to run DHCPCLNT on the server.)
  7. Select Next.
  8. Enter the board name you gave the second NIC or the board name you wrote down in a 1-NIC configuration.
  9. Enter the Default Router IP Address as indicated by the configuration illustration for the option you chose.
    (If it is provided dynamically by your ISP, just enter any value here. For example, 1.2.3.4)
  10. Select Next.
  11. Verify the information is correct and select Finish.
    (Caution: be sure that INETCFG is NOT open on the server before selecting Finish. If INETCFG is open, close it before finishing.)
  12. Once the configuration is complete, restart the server.

    Notes:
    • You can shut down and restart the server at a later time when it is not in use.
    • You can restart the server while users are logged in to it; however, if users are trying to save data while the server is momentarily down, the data might be lost.
    • When you restart the server, you might see some errors indicating that certain utilities are in use. These utilities will automatically reconnect to the server when the server restart is complete.
    • If you need to change any of the information, click Back and change any information on any of the previous screens. Then click Next until you return to this screen.
    • If any of the settings are incorrect and cannot be entered in the server configuration file by NICE interacting with INETCFG on the server, the Internet configuration on the server will stop and will not proceed.
    • If you want to erase all the entries and start over, click Cancel.
    • If the Internet configuration to the server stops while processing the configuration setting specified from NICE, the server configuration will stop and an error will be returned to the server console and to the NICE interface indicating why the INETCFG configuration stopped. Run NICE again to correct the settings.

    Q&A

    Q Jenna J. wrote: Is DSL supported on NSBS 4.2 for Internet access? I know it is on NSBS 5 but we need to know if it is on NSBS 4.2? If so..is there any documentation on how to set it up? Also...the NICE helps people set up a DSL connection in NSBS 5, is there a wizard of that type available for NSBS 4.2?

    AND

    Charles S. wrote: I use NWSB 4.2. Your "Internet Connection Wizard" has choices to connect using a modem and an ISDN line but no way to connect using a DSL line. Can you assist me with this?

    A Answer updated April 18, 2000 -- If you're using NWSB 4.2, you won't be able to use the ISPWIZ.exe (aka NICE) to configure DSL. We added DSL configuration to NICE in the NSBS 5 version.

    However, you can still configure DSL on an NWSB 4.2 server, it's just a little more complicated. You just go into INETCFG and manually do the configuration for a second network card (that's essentially all DSL is to NetWare).

    (Editor's Note: This was answered incorrectly when the article was first posted. Above is the corrected answer. Please note that you cannot use any version of NICE (Internet Connection Expert, aka ISPWIZ.EXE) on a 4.2 server. It just won't work. For more information about how to configure DSL via INETCFG on a NWSB 4.2 server, check out this article.)

    Q TH wrote: I have DSL at my house with one static IP address, a 6 port hub and 3 machines to hook up. I'm putting up a server to run bordermanager with firewall and cache.

    My question is this: What's the best approach to get all the machines on the NET and still be able to use client VPN to access the corporate network? I'm not averse to buying additional IP addresses from the ISP (if they'll sell them to me) in order to avoid using NAT, but I was hoping there might be a more elegant solution?

    A You've got to buy at least one more address. VPN's don't run thru a NAT router, at least not yet.

    Q NEW: Terry R. wrote: From reading your feature article on connecting NSBS 5 to the Internet using DSL the first example shows the DSL modem obtaining a dynamic ip address from the ISP and also having a manually configured static ip address. How is it possible for the DSL modem to have both a dynamic and a static ip address?

    A The DSL modem has two interfaces. If the modem is configured as a gateway (PPP/Gateway mode) then each interface requires an IP address. It's much the same as any routing device. The external interface (to the ISP)can be either statically or dynamically assigned, the internal interface is always statically assigned. The internal interface is usually configured by connecting to the modem through a management port or a telnet session. In almost every case, the external interface connected to the ISP will be dynamically assigned. In bridging mode, the modem acts only as a bridge between two different mediums. It simply passes the packets from one interface to the other, it does no routing.

    Q NEW: Ryan M wrote: In your article, you mention some issues w/ Option A (PPP w/ Server as Gateway). Having set up a few installations such as this already, I'm going to stick my two cents in with some recommendations. I think your Option A is the best solution of the four, and with a little preparation you can overcome the significant shortcomings you mentioned.

    First: Get valid IP addresses. You only really need two.

    Second: Move the NAT off the router and onto the Server.

    Here's the advantages that I've found: Having a valid IP address on the Server allows you to use VPN, have direct e-mail thru GroupWise (I prefer not to use the PFA), and maintains security with fire-walling you can setup on the server. Plus, since ISP's usually manage the router they give you, by moving the additional services to the server it puts the control of your network back in your hands.

    In my installations I set the server up as the gateway, with a valid IP for the Public NIC (& DSL Modem) w/ Firewall & NAT, and DHCP (w/ an invalid IP) for the Private NIC. This way I have a combination of flexibility & security, and keep the responsibility of securing & managing my network in my own hands, and not my ISP's.

    A Good comments, Ryan! About getting valid IP addresses: You do only need two, but the ISP's I've seen give them in blocks of eight. Without valid IP's you can still do everything except VPN. Some things are a little more complex without the valid IP's though. For example, receiving e-mail. With valid IP's GWIA can do it, with non-routable IP's you have to use PFA.

    In Option A, NAT is actually running on the modem AND the server. Since NAT is still running on the server, and all the clients are on the private interface, VPN sorta works. I believe you will only be able to VPN into your server, not VPN out. If you have a client machine external to your network, you should be able to use VPN to connect to your network. What you can't do is use VPN to connect to a server external to your system from one of your internal clients.

    BorderManager can be installed and will provide fire-walling and security regardless of whether the IP addresses are valid ones or the default non-routable ones.

    Q NEW Terry R. wrote: I have just completed reading the feature article on connecting NSBS 5 to the internet using xDSL. We have an ADSL modem connection to the Internet and are using NSBS 5. However, unlike the modems used in the feature article our ADSL modem has only one interface whereby it receives a dynamic ip address from our ISP. Will this configuration work given that we are not able to manually configure a static IP address for the public interface in our NSBS 5 server.

    A How many plugs does your modem have? It should have at least two. One for the phone line that DSL is installed on, and a second one for a twisted-pair ethernet cable. The phone will probably be an RJ-11 (might be RJ-45) and the ethernet one will be an RJ-45. You may also have a third one that you can plug a phone into. The ethernet one might be labeled as "Computer" or "Hub".

    Do you have this on your modem? If so, the connection your DSL phone line plugs into is the interface that gets a dynamic IP from your ISP. The ethernet interface is the one you have to configure with a static IP address. (Assuming your using one of the PPP/Gateway mode configurations.) The cable you plug into this port should go directly to the second Network Board you installed in your server. (Or into the hub if you only have a one NIC configuration.) Your modem documentation should explain how to connect to the modem and configure it. If an ethernet cable was sent with your modem, more than likely it is a cross-over cable and must be used as the one between the DSL modem and your server. It won't work if you plug it into a hub.

    If your modem is something different than this, let us know.

    About the Author

    Alan is an engineer on the Small Biz team, and has been working in the computer field since 1992. He has a Bachelor Degree in Computer Science from BYU, and currently lives in Spanish Fork with his wife and son. (Another boy is on the way. He's due in May!) His hands-on DSL experience came from setting up DSL for the condominiums where he used to live. It has 24 units, and all but two are wired up and sharing the DSL connection. He enjoys spending his time with his family.

    Reader Comments

    • perfect

    Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

Novell® Making IT Work As One™

© 2009 Novell, Inc. All Rights Reserved.