You can do thisthree ways:
svcutil <assembly>
where <assembly> is the assembly that contains your service contracts.
svcutil <path>
where <path> is the path to your running service. This has nothing to do with net.tcp
://configserver. The path points to the endpoint you have exposed as a running service. If this endpoint is a virtual address exposed through config service, you use that virtual endpoint. If it is defined in a .config file, then use that address. Only you could possibly know this address.
Use the repositorycreation tool that comes with MCS. You'll notice on the service client generation tab there is an option to generate a tool via svcutil. You can follow the directions in the tutorial, but choose svcutil generated client, and point to the assemblies that contain your contracts, just like in the first option.
For further information on svcutil, look at:
http://msdn.microsoft.com/en-us/library/aa347733.aspxThanks,
Darren