XP ICS works great but...

[Guest]

I volunteer in a small non-profit office and they just got DSL in th
office

The setup

Three computer
Primary PC is connected to DSL route
Dual NIC cards on the primary P
Secondary NIC goes to 10/100 hu
Other computers go to hu
All running Windows XP Pr

Problem
There is a network copier/printer on the network. The manual says that
DHC
will mess up the printer each time it reboots. Manufacturer recommend
fixing the IP of the printer

Question

I have read that I cannot block any range of IP address from the ICS
DHC
server. What will happen when the DHCP assigns the same IP? I assume I
wil
start getting network conflicts with two devices havin the same IP or
is th
ICS thorough enough to do a ARP or RARP before assigning the new IP

If my solution is to disable the ICS, how do I do that easily and wha
series of menus do I access on each machine to set the IP address

Thanks in advance for any suggestions.

 

[allan grossman [mvp]]

Hi -

What I'd do is use the router to perform DHCP functions
on your network - then you can turn off ICS completely.
All you'd have to do then is set a static IP for the
copier that's outside the DHCP scope for your network. I
do something similar on my network but have a server with
a static IP instead of a copier ;-)

What I did was set up the server with a static IP of
192.168.1.50 - and on the router I set the DHCP scope for
workstations to 192.168.1.101 through 192.168.1.254 -
that way the router cannot assign an IP address that
conflicts with the server.

Hope this helps -

 

[Steve Winograd [MVP]]

I volunteer in a small non-profit office and they just got DSL in the
office.

The setup:

Three computers
Primary PC is connected to DSL router
Dual NIC cards on the primary PC
Secondary NIC goes to 10/100 hub
Other computers go to hub
All running Windows XP Pro

Problem:
There is a network copier/printer on the network. The manual says that
DHCP
will mess up the printer each time it reboots. Manufacturer recommends
fixing the IP of the printer.

Question:

I have read that I cannot block any range of IP address from the ICS
DHCP
server. What will happen when the DHCP assigns the same IP? I assume I
will
start getting network conflicts with two devices havin the same IP or
is the
ICS thorough enough to do a ARP or RARP before assigning the new IP.

If my solution is to disable the ICS, how do I do that easily and what
series of menus do I access on each machine to set the IP address.

Thanks in advance for any suggestions.

I agree with Allan Grossman's suggestion to connect everything to the
router and stop using ICS.

However, if you want to use ICS, there shouldn't be a problem. Assign
the printer a static IP address like 192.168.0.254. Before ICS
allocates an IP address via DHCP, it checks to make sure that the
address isn't already in use. Assuming that the printer responds
properly when ICS checks addresses, everything will work.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Jim]

Seems everyone is taking this description quite literally, I'm more
skeptical.

You mentioned a "DSL router", but are we really talking about a "router"
here, or just a DSL modem? A router is typically a separate device "to
which" you attach either a cable or dsl modem via its WAN port. The router
itself either has an integrated hub/switch to which client PCs are attached
via its LAN ports, or its a standalone router that's attached to a separate
hub/switch (and of course, client PCs are attached to the hub/switch). If
you don't have such "hard" router, but its simply a dsl modem, then you need
to continue designating a PC as a "soft" router using ICS. One NIC is
attached to the dsl modem, the other NIC to the hub. Clients are routed to
the ICS PC and dsl modem for Internet access.

Second, I'm also not sure we're talking about a "network" printer, i.e., one
w/ an installed network card. It wouldn't be unusual for someone to call a
printer attached to a PC via USB or parallel cable a "network printer". In
this context, the term is emphasizing the fact its "shared", not that it's a
standalone, network-enabled, printer. A shared printer off a Windows PC is
typically addressed by *name*, not IP (e.g., \\PC_A\Printer A ). So the
issue of the IP changing w/ DHCP is moot. It only matters if a) clients
insist on addressing via IP (not advised for this reason) or b) the printer
truly is a standalone, TCP/IP enabled printer (not attached to a PC), thus
is doesn't support a Windows share name. It's this latter case that the
manual is really warning about, the case where the printer is only
addressable by IP (e.g., \\192.168.0.100\Printer_A ).

If I'm right about these two items, then you're worrying over nothing.

HTH

Jim

 

[Guest]

You are correct on point one, but on point two it is a
true network print/copier. It does copy and also responds
as a printer. Full NIC card and all.

Thanks for everyone for the assistance. I know what I
need to do!

 

[Guest]

Thanks for the input! Really appreciate it.

-----Original Message-----
Seems everyone is taking this description quite literally, I'm more
skeptical.

You mentioned a "DSL router", but are we really talking about a "router"
here, or just a DSL modem? A router is typically a separate device "to
which" you attach either a cable or dsl modem via its WAN port. The router
itself either has an integrated hub/switch to which client PCs are attached
via its LAN ports, or its a standalone router that's attached to a separate
hub/switch (and of course, client PCs are attached to the hub/switch). If
you don't have such "hard" router, but its simply a dsl modem, then you need
to continue designating a PC as a "soft" router using ICS. One NIC is
attached to the dsl modem, the other NIC to the hub. Clients are routed to
the ICS PC and dsl modem for Internet access.

Second, I'm also not sure we're talking about a "network" printer, i.e., one
w/ an installed network card. It wouldn't be unusual for someone to call a
printer attached to a PC via USB or parallel cable a "network printer". In
this context, the term is emphasizing the fact its "shared", not that it's a
standalone, network-enabled, printer. A shared printer off a Windows PC is
typically addressed by *name*, not IP (e.g., \\PC_A\Printer A ). So the
issue of the IP changing w/ DHCP is moot. It only matters if a) clients
insist on addressing via IP (not advised for this reason) or b) the printer
truly is a standalone, TCP/IP enabled printer (not attached to a PC), thus
is doesn't support a Windows share name. It's this latter case that the
manual is really warning about, the case where the printer is only
addressable by IP (e.g., \\192.168.0.100\Printer_A ).

If I'm right about these two items, then you're worrying over nothing.

HTH

Jim





.

 

[Guest]

Thank you!

-----Original Message-----

I agree with Allan Grossman's suggestion to connect everything to the
router and stop using ICS.

However, if you want to use ICS, there shouldn't be a problem. Assign
the printer a static IP address like 192.168.0.254. Before ICS
allocates an IP address via DHCP, it checks to make sure that the
address isn't already in use. Assuming that the printer responds
properly when ICS checks addresses, everything will work.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
.