[<<]Message[>>] [<<]Author[>>] [<<]Subject[>>] [<<]Thread[>>]
Number : 128 Date : 2001-06-01 Author : Kan Yabumoto Subject : Re: ip address range Size(KB) : 5
Ann: Let me try to rephrase what you are saying to make sure I understand you correctly. The list of the 500 computers that are connected to your computer via the network can be listed by simply typing the following at the command prmopt: net view Is that correct? Under MS Windows peer to peer (workgroup) networking scheme, the remote computers (workstations and servers) attached via the network should be visible that way. I'm not familiar with the DHCP parsing stuff except that our networking in our labs are hooked up by DHCP server for the sake of Microsoft's ICS (Internet Connection Sharing). I have never tried to make a listing using perl script. Can you show me the section of your perl script which is relevant to this operation? I assume that your question was too see if we can add a functionality in XXCOPY which allows you to even use a wildcard in the server name in the source/destination specifier. Currently, XXCOPY has no feature to allow you to use a wildcard in the remote resource. That is, when you use a UNC, the servername and the resource name (the first two items in the path_specifier with UNC) xxcopy \\myserver\drive\*abc*\... /L /S Where the first two levels in the above command must be supplied to XXCOPY. That is, the standard File I/O in Win32 API does not provide functions to enumerate either the list of servers or the resource in a server; the third level (which acts as the "Root" of the resource is the first place where XXCOPY can add a wildcard to determine what's out there (as opposed to access a pre-determined name specified by the user). ------------ end of my digestion of what Ann posted ----------- OK, let me start with our frustration in within a local machine. Unlike the Unix/Linux scheme where there is no such thing as the drive letter, but a pure Root where everything begins, MS operating system has always had the drive letter. While many users claim the dubious virtues of the drive letter (to help organize???), it is a pain in the neck for programmers. We tried to even come up with a few schemes in notation to "unify" the various drives under a single ROOT. At least, by convention, once a networked host (either a workstation or a server) is accessed, you may say \\myserver\c\windows\... \\myserver\d\temp\... Here, a "volume" within a system becomes just like a subdirectory (albeit under the varying resource name representing the drive). We wish there is an established notational convention to bundle and refer to the volumes on the local storage. I guess what Ann is referring is also in the same spirit that if we can use a notation to bundle multiple hosts (workstations/servers) in one stroke, that would be super. In the case of the UNC pathname scheme, we don't need much imagination; we can just allow the usual wildcard characters (* and ?) even in the first and the second levels. Of course, this is not the common XCOPY-compatible convention, but it is already within the scope of XXCOPY's "Wild-Wild-Source" feature (where wildcards are allowed anywhere, any number). Of course, implementing that is another issue and I don't have foggiest idea on this (anyone with the programming technique -- in C, please teach us how in Win32's programming context). The perl script is a good starting point on this. One last thing with regard to Ann's question: her posting's title mentions the "ip address range" which I did not touch basis. Ann, are you suggesting an iteration within an IP address numeric range (possibly using some subnet mask)? Then, we are now talking about TCP/IP stuff. Wow!!! I heard some other user once mentioned to the use of XXCOPY to transfer files across the Internet. That's a whole new ball game --- basically the FTP features to be added to XXCOPY. But, if someone write a nifty driver who assigns a UNC entry to an IP address and can make FTP operations transparent as if it is a "virtual file system", then, XXCOPY would be able to talk to it (I can see that could be pretty useful but I'm not sure if we have resource to do so). Of course, if you believe in XXCOPY's boundless extension motto, that's not totally out of line, I guess. Frankly, we at Pixelab need a lot of homework to do. When we go beyond the familiar DOS and Win32 turfs, we are pretty much fish without water ... (If someone gives us well-written C programs for this, that will be a good starting point in our research.) Anyway, before going after the TCP/IP or even remote host enumeration, we much prefer to handle the local case first. One convention which come to my mind is using a new convention with a "grand prefix" such as "\\My Computers\" since that's how Windows' applications (notably, Windows Explorer) unifies the various drive letters. The only reservation here is that the word "My Computer" is not conforming to the 8.3 format (at least \\localhost\ does not have an embedded space but has 9 characters). At least using such a prefix in conjunction with the "Wild-wild-source" scheme would allow XXCOPY to handle multiple-volume statement which opens up a new ways to write backup scripts. Sorry, again, I'm badly digressing... Kan Yabumoto ===================================================================== At 2001-05-31 11:35, Ann Stanaway wrote: >I use xxcopy to manage workstations and servers on my network. Although I >do currently have a list of the network names of all 500 computers I want to >manage, it would be easier to manage the batch file if I could use the DHCP >range to parse through the network connections. I can set up PERL to run >this, but was hoping that somebody had tried this function in xxcopy. > > > >Ann L. Stanaway
This message if part of XXCOPY's message Archive. The archive contains all the messages posted at Yahoo!Groups: XXCOPY.