|
Do the IP addresses have to be available in that drop-down list? (The one that also has the option "All Unassigned") Do I have to get the DHCP server to assign extra addresses to the IIS box? There seems to be an option on our router's web server to assign extra IP addresses but it wants a MAC address too, when I try to add an IP address, but I wouldn't have the faintest idea what a MAC address is, why I have to specify it, and how I know what to type in...
NATHAN RIDLEY
Web Application Developer
generalgherkin@yahoo.com
|
|
|
|
|
A MAC address is the globally unique identifier assigned by the manufacturer to the Network Interface Card (NIC). Windows 2000 allows you to assign multiple IP addresses to a single NIC, though I've never had reason to do this and don't know how off hand. You do not want to have DHCP assign IP addresses to a server; these should be statically addressed. Spend some time at the Microsoft Technet site and review the Resource Kit documentation - it actually has some useful information in it.
"Some people are like Slinkies... not really good for anything,
but you still can't help but smile when you see one
tumble down the stairs."
|
|
|
|
|
Ok, thanks for the info.
NATHAN RIDLEY
Web Application Developer
generalgherkin@yahoo.com
|
|
|
|
|
Ok, have done some more investigation on this. Is it possible to, instead of mapping a name to a single IP address, instead map multiple names to the same IP address, but on different ports?
NATHAN RIDLEY
Web Application Developer
generalgherkin@yahoo.com
|
|
|
|
|
Probably, but I doubt that you'd want to. Your users' browsers will default to port 80 for http requests, and in order for them to reach the different sites you'll have to provide them with links that override the default port. Instead, you could create each site in a different virtual directory and access them through a URL such as www.mydomain.com/site1/ www.mydomain.com/site2 etc.
"Some people are like Slinkies... not really good for anything,
but you still can't help but smile when you see one
tumble down the stairs."
|
|
|
|
|
I must be doing it wrong, or maybe doing something in the wrong order because I can't seem to get it to work...
NATHAN RIDLEY
Web Application Developer
generalgherkin@yahoo.com
|
|
|
|
|
Sorry, looking at this confusing thread, I'll elaborate. I have set up static IPs for each website and they work fine now. Last hurdle is trying to assign a name to each website so I don't have to use the IP address to get there. Haven't had much luck making it work yet though...
NATHAN RIDLEY
Web Application Developer
generalgherkin@yahoo.com
|
|
|
|
|
Try setting up each website in its own virtual directory. Visual InterDev does this each time you create a new web on the server, and the sites are accessed by the URL www.mydomain.com/sitename/.
"Some people are like Slinkies... not really good for anything,
but you still can't help but smile when you see one
tumble down the stairs."
|
|
|
|
|
The problem is that some of the sites require a reference to the root as part of their code. I'm using win2k advanced server, so I have just used "New -> Website" to add websites. Although.. as I think about it... if I am assigning an IP address to a virtual directory, that would work pretty much the same way, wouldn't it? What's the advantage of using one method over another? i.e. virtual directory vs standalone website. Oh, also, I don't have Visual Interdev, because I use Dreamweaver MX for my coding environment
NATHAN RIDLEY
Web Application Developer
generalgherkin@yahoo.com
|
|
|
|
|
I just went spelunking in ISM and realized that assigning a separate IP to a virtual directory isn't an option - I must have been thing of the new site wizard. Sorry about that... I use the www.mydomain.com/sitename method for hosting multiple sites for development. That requires just one IP address and port 80 for all of them, and gives them all access to root functions as needed. It's easier for users to understand than the separate port option, too. When I have a site ready for production I can simply ftp the entire directory containing the code to the server used for hosting with a couple of clicks.
BTW - How do you like Dreamweaver? I've read great reviews and terrible, and I know from experience that Visual InterDev sucks. I wonder which one sucks less...
"Some people are like Slinkies... not really good for anything,
but you still can't help but smile when you see one
tumble down the stairs."
|
|
|
|
|
I find Dreamweaver MX quite good, however the ftp upload function seems to be unstable, and you can't perform simply ftp functions such as CHMOD.. I use Dreamweaver to code, and WS-FTP to upload ...
|
|
|
|
|
For the little bit I used it, I hated InterDev. DW on the other hand seems very nice to me (I'm currently using MX), but as Baldcat said, I also use a separate FTP client.
Paul 
That demands capital punishment!! Death by a herd of marauding Bobs! - Ryan Binns
modified 18-Jul-18 11:59am.
|
|
|
|
|
With HTTP 1.0, all sites need an individual IP address/port combination.
HTTP 1.1 adds the 'Host' header, which permits the client to tell the server which name it thinks it's talking to.
It looks like you can configure this by going to the web site's properties in the Internet Information Services Admin Tool, then on the Web Site tab, hit Advanced next to IP Address. Under 'Multiple identities for this Web Site', highlight 'Default' and hit Edit. Under Host Header Name, enter the name of the site. Repeat for each website, making sure they're all on port 80 (since the port is encoded in the URL, defaulting to 80).
You then need to add each name to your DNS either as an A record pointing to the server's IP address, or, preferably, a CNAME record pointing to the server's canonical name.
You'll need to check that all your clients are using HTTP 1.1 before doing this, but all new browsers are 1.1 capable.
If you need to support 1.0, you'll need to add some IP addresses. In Network Connections, go to Properties for your Local Area Connection. Highlight 'Internet Protocol (TCP/IP)' in the list, then click Properties. Hit Advanced, then under IP Addresses, hit Add to add a new address.
Add your new IP addresses to DNS, then set your websites up as appropriate.
The 1.0 solution is very wasteful of addresses and resources, so the Host header is preferable.
|
|
|
|
|
quick question regarding your use of cmsdev as a server name .... are you in charlotte ??
|
|
|
|
|
no, australia
NATHAN RIDLEY
Web Application Developer
generalgherkin@yahoo.com
|
|
|
|
|
Okay, cause I work for a company here in charlotte and we have a cmsdev. Anyway .....
- Sage
|
|
|
|
|
But there must be thousands of companies developing content management systems! cmsdev = "content management system development". Surely you don't think your company was the only one?
NATHAN RIDLEY
Web Application Developer
generalgherkin@yahoo.com
|
|
|
|
|
please.. I am not that naive..
the company I contract for is the Charlotte Mecklenburg Schools (CMS)
it was just an inquiry either way.
|
|
|
|
|
ah, fair enough 
NATHAN RIDLEY
Web Application Developer
generalgherkin@yahoo.com
|
|
|
|
|
IN MS-OPERATING SYSTEM,
"A FILE CANNOT BE RENAMED (OR) NAMED AS 'CON'(WITHOUT SINGLE QUOTES)".WHY IS IT SO????
PLEASE CLEAR MY DOUBT.
|
|
|
|
|
CON is a reserved device in all DOS-based systems. It refers to the console device; for input, the keyboard, and the monitor for output. You cannot create a file using a reserved device name, else the system will have no idea which object you want to operate on.
"Some people are like Slinkies... not really good for anything,
but you still can't help but smile when you see one
tumble down the stairs."
|
|
|
|
|
The "Fountain of Knowledge" speaks. 
I want you on my "Trivial Pursuit" team.
The kindest thing you can do for a stupid person, and for the gene pool, is to let him expire of his own dumb choices.
[Roger Wright on stupid people]
We're like private member functions
[John Theal on R&D]
|
|
|
|
|
A quibble, not just DOS based systems. The NT kernel family kept this convention despite having no DOS lineage.
For bonus points, there are other reserved device names that most people have forgotten:
AUX - The auxilary device, usually mapped to com1, kernel debugging goes here.
PRN - The default printer, usually mapped to lpt1.
NUL - The null device, anything written here is throw away.
These, plus CON, and the better known COM[1-9] and LPT[1-9] devices are all invalid filenames still today. More amusing, they are invalid even in combination with any file extension, i.e. naming a file aux.txt is an error as well.
Anyone been around long enough to remember ox.sys or winaux.sys?
--
-Blake (com/bcdev/blake)
|
|
|
|
|
At least it's consistent.
Blake Coverett wrote:
Anyone been around long enough to remember ox.sys or winaux.sys?
I've been around long enough, I'm sure, but I don't remember hearing of them before. What were they used for?
"Your village called -
They're missing their idiot."
|
|
|
|
|
They were little DOS device drivers used in Win16 coding days to hook the AUX output and write it to the block of memory at 0xB000 that represented a mono monitor. All serious Win16 programming setups had both a VGA monitor and a mono monitor attached, so your debug output and the old CodeView debugger could run on the mono monitor.
--
-Blake (com/bcdev/blake)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
