JohnEsmay said:
Thanks Lem,
We sign onto the Remote Payroll service locally, and then enter the data. A
scan from the remote payroll service detects something it does not like and
crashes the program. Their guess was our small network. We also do remote
backup. "Payroll" may be seeing that program.
Lem, your suggestion for more information is helpful.
Jacks suggestion of another router may help.
Could I accomplish goal by assigning the payroll computer to a differant
workgroup. Would that keep the other computers off the payroll computer but
still let everyone connect to the internet?
Thanks All
John Esmay
No, a different workgroup wouldn't help. Workgroups are merely a
mechanism used by "Network Neighborhood." One can easily access files
between workgroups unless there is some other mechanism preventing that
access.
Jack's suggestion of a segregated network is an effective way to
accomplish what you want. All computers can access the Internet but the
computers on the two separate networks won't be able to communicate with
each other. Whether that configuration would satisfy the "scan" done by
your remote payroll service is another story. I suggest that you test
your payroll service's "guess" by disconnecting the network cables of
all the *other* computers on your network and see if the scan still crashes.
In terms of Jack's example, you would put your payroll computer on what
Jack calls the "segregated network" with an IP address of 192.168.2.x
and your other 2 computers on the "front network" with IP addresses of
192.168.1.x. Note that although Jack's example shows the "front
network" as wireless and the segregated network as wired, the connection
method is not important. If you don't need wireless capability, neither
router need have wireless capability.
--
Lem -- MS-MVP
To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm