I had an XP machine using netmodem conneting to a server(SBS2000). Sometime
around installing XP service pack 2, this connection failed (I'm not
positive it's related). I've uninstalled and re-installed net modem several
times including removing all shared ports and starting over. Following the
instructions in "How to set up a Windows XP Professional client in an SBS
2000 network, article ID 316418", the network modem never shows up in device
manager so naturally it won't install in "phones and modems". Do you have
any idea what I could be missing? Thanks. Rick

Re: netmodem problem by Steve

Steve
Mon Dec 06 12:54:03 CST 2004

RickM wrote:

> I had an XP machine using netmodem conneting to a server(SBS2000).
> Sometime around installing XP service pack 2, this connection failed
> (I'm not positive it's related). I've uninstalled and re-installed
> net modem several times including removing all shared ports and
> starting over. Following the instructions in "How to set up a
> Windows XP Professional client in an SBS 2000 network, article ID
> 316418", the network modem never shows up in device manager so
> naturally it won't install in "phones and modems". Do you have any
> idea what I could be missing? Thanks. Rick

The network modem won't show in Device Manager. It's not a local device.

Open a command prompt and use the net modem command to show you the
port arrangement - if your network shared modem pool doesn't show up as
allocated to a COMx port, you won't be able to add the modem.

Also, the shared modem cannot be added using automatic detection.

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.

Re: netmodem problem by RickM

RickM
Mon Dec 06 16:22:01 CST 2004

Thank you for the reply.
Netmodem was working on an XP machine and failed sometime after the user
installed service pack 2.
In an attempt to fix the problem I'm using Article ID 316481 "How to set up
a Windows XP Professional client in an SBS 2000 network.

The following instrucitons worked fine down to "double click phones and
modems" and that's where I'm running into my road block. I've uninstalled
and re-installed the modems, even the local modem several times, and can't
get it detected or see the new port to select.
To install the Modem Sharing client, follow these steps:

1.
Right-click My Network Places, and then click Properties.

2.
Right-click Local Area Connection, and then click Properties.

3.
Click Install, and then double-click Service.

4.
Click Have Disk, click the Netsrdr.inf file in the \\server
name\ClientApps5\Modem Sharing Client\Win2K folder, and then click Open.

5.
After the path to the installation files is in the Install From Disk
dialog box, click OK.

6.
Click to select the Shared Modem Service Client check box, and then
click OK.
NOTE: If Phones and Modems is not visible in Control Panel, click to
select Switch to Classic View.

7.
After the files are copied, close LAN connection properties, and then
restart the client computer.


Configure the Modem Sharing client

To configure the Modem Sharing client, follow these steps:

1.
At a command prompt, type netmodem view \\server name, and then press
ENTER.
The response displays the modem pool on the server.

2.
Type netmodem use * \\server name\pool name, and then press ENTER. The
response confirms a successful attachment and displays a report of the local
COM port that is being used. Note the COM port number that is being used.
NOTE: This port number is increased by 1 from the last COM port that
was identified and increases by 1 each time that you run the command. On
some client computers, COM2 may be the next available COM port, but it may
not function correctly for modem sharing. You can specify the COM port to
use by substituting COMport number for the asterisk (*).
To remove an unnecessary modem pool COM port assignment, type netmodem
use comport number /d at a command prompt, and then press ENTER.
For example, if your COM port is 3, type: netmodem use COM3 /d.

3.
At the same command prompt, type net stop serrdr, and then press ENTER
to stop the serial redirector.

4.
t the same command prompt, type net start serrdr, and then press ENTER
to start the serial redirector.

5.
Close the command prompt.

Right here is where I run into problems. The modem is not showing when
I click "Add" and"click selected ports" doesn't show the new port I added.

6.
Double-click Phones and Modems in Control Panel.

7.
Click the Modems tab, and then click Add.

8.
In the Add Hardware Wizard, click Next.

9.
Click Next, and then click your type of modem. Note that in most cases
you can select a standard modem type and there is not a requirement to find
a specific driver.

10.
Select the modem, and then click Next.

11.
Click Selected Ports, and then click the port that you noted in step
two.

12.
Click Next, and then click Finish.

13.
Click the modem, and then click Properties.

14.
Click the Diagnostics tab, and then click Query Modem to provide a
response from the shared modem and verify connectivity.


IMPORTANT: The modem that is used for modem sharing should not be used by
any other program or service. Instead, it should be dedicated to modem
sharing exclusively.



--


----------------------------------------------------
This mailbox protected from junk email by MailFrontier Desktop
from MailFrontier, Inc. http://info.mailfrontier.com

"Steve Foster [SBS MVP]" <steve.foster@picamar.co.uk> wrote in message
news:xn0dqp5mp8uip2003@msnews.microsoft.com...
> RickM wrote:
>
>> I had an XP machine using netmodem conneting to a server(SBS2000).
>> Sometime around installing XP service pack 2, this connection failed
>> (I'm not positive it's related). I've uninstalled and re-installed
>> net modem several times including removing all shared ports and
>> starting over. Following the instructions in "How to set up a
>> Windows XP Professional client in an SBS 2000 network, article ID
>> 316418", the network modem never shows up in device manager so
>> naturally it won't install in "phones and modems". Do you have any
>> idea what I could be missing? Thanks. Rick
>
> The network modem won't show in Device Manager. It's not a local device.
>
> Open a command prompt and use the net modem command to show you the
> port arrangement - if your network shared modem pool doesn't show up as
> allocated to a COMx port, you won't be able to add the modem.
>
> Also, the shared modem cannot be added using automatic detection.
>
> --
> Steve Foster [SBS MVP]
> ---------------------------------------
> MVPs do not work for Microsoft. Please reply only to the newsgroups.



Re: netmodem problem by Steve

Steve
Tue Dec 07 07:49:35 CST 2004

RickM wrote:

> Thank you for the reply.
> Netmodem was working on an XP machine and failed sometime after the
> user installed service pack 2.
> In an attempt to fix the problem I'm using Article ID 316481 "How to
> set up a Windows XP Professional client in an SBS 2000 network.
>
> The following instrucitons worked fine down to "double click phones
> and modems" and that's where I'm running into my road block. I've
> uninstalled and re-installed the modems, even the local modem several
> times, and can't get it detected or see the new port to select.

Right, and what was the outcome of step 2. What COM port is the
netmodem service showing that is allocated to your shared modem pool.

"netmodem use" should show you the current assignments and COM ports.

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.

Re: netmodem problem by RickM

RickM
Tue Dec 07 11:00:26 CST 2004

Thank you for your reply
and, Step 2 worked fine, as outlined below

Z:\>netmodem view \\gahmserver
Shared pools at gahmserver
Pool name Description
Comports COM Devices
GAHM_MODEM Creative Modem Blaster V.92 PCI DI5633

Z:\>netmodem use * \\gahmserver\gahm_modem
Port COM6: is now connected to \\GAHMSERVER\GAHM_MODEM

The command completed successfully.

The instructions work fine until I go into Phones and Modems, modems tab,
add, and it doesn't detect my new modem, "gahm_modem", it only shows
standard modem. But I'm consistant. Last night I went to second XP machine
and encountered the same problem. Just a thought. Do I need to be logged
in on the local machine and not on the network? I may try that tonight
after the users go home.

Thanks
Rick
"Steve Foster [SBS MVP]" <steve.foster@picamar.co.uk> wrote in message
news:xn0dqqc6l1deqhf003@msnews.microsoft.com...
> RickM wrote:
>
>> Thank you for the reply.
>> Netmodem was working on an XP machine and failed sometime after the
>> user installed service pack 2.
>> In an attempt to fix the problem I'm using Article ID 316481 "How to
>> set up a Windows XP Professional client in an SBS 2000 network.
>>
>> The following instrucitons worked fine down to "double click phones
>> and modems" and that's where I'm running into my road block. I've
>> uninstalled and re-installed the modems, even the local modem several
>> times, and can't get it detected or see the new port to select.
>
> Right, and what was the outcome of step 2. What COM port is the
> netmodem service showing that is allocated to your shared modem pool.
>
> "netmodem use" should show you the current assignments and COM ports.
>
> --
> Steve Foster [SBS MVP]
> ---------------------------------------
> MVPs do not work for Microsoft. Please reply only to the newsgroups.



Re: netmodem problem by Steve

Steve
Tue Dec 07 16:07:40 CST 2004

RickM wrote:

> Thank you for your reply
> and, Step 2 worked fine, as outlined below
>
> Z:\>netmodem view \\gahmserver
> Shared pools at gahmserver
> Pool name Description
> Comports COM Devices
> GAHM_MODEM Creative Modem Blaster V.92 PCI DI5633
>
> Z:\>netmodem use * \\gahmserver\gahm_modem
> Port COM6: is now connected to \\GAHMSERVER\GAHM_MODEM
>
> The command completed successfully.
>
> The instructions work fine until I go into Phones and Modems, modems
> tab, add, and it doesn't detect my new modem, "gahm_modem", it only
> shows standard modem. But I'm consistant. Last night I went to
> second XP machine and encountered the same problem. Just a thought.
> Do I need to be logged in on the local machine and not on the
> network? I may try that tonight after the users go home.

It *won't* detect your modem. I told you that. You need to add it
manually, point XP to a network share with the correct modem drivers
for the physical modem type, and then make sure it picks up COM6 for
the modem.

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.