Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
This is my setup:
My ISP assigns me a static IP and that goes to my speedtouch 510 routermodem. Router/modem has DHCP/DNS servers running and assigns my network IP’s (10.0.0.X) one of which my Server is on, getting IP from the Router. This way all pc’s can independently connect to the internet. And my server has no hand in that, which is fine with me.
Now I have this server up to host websites and FTP, it is running Windows server 2003, IIS6 I have no domain name I just use a no-ip.info name. So its shemonixfix.no-ip.info for the internet to see port 80. Well that is all working fine, but I cannot get to that sight from within my network other than using my local IP, the 10.0.0.X number, Localhost won’t work, I think my DNS is a bit messed up with that. Nor the http://shemonixfix.no-ip.info since I cannot connect to my remote IP that way. I would like to setup multiple websites using my single IP number.
This brings me to my main question:
Should I setup my Server to be the DHCP/DNS server or leave that to my router since its doing a nice job? I would really like to be able to go to my site using its shemonixfix.no-ip.info address. Can that be setup in the DNS? Although that would mean a whole lot of editing configurations and scripts to change out a new Local IP number.
If I had more knowledge with setting up the dns on my windows server 2003 I would rather do that, for more control.
And after that’s resolved,
How do I go about setting up multiple websites using one IP on IIS6 and can I still use http://www.no-ip.com to manage my IP?
I know it’s a lot in one shot but, its something that I’m going to have to deal with.
Thanks,
Ed.
The first thing you should do is set the server with a static IP. Then I would set up the server to run the DNS and the DHCP and not the router. I think that will solve alot of your problems. I don't know about multiple site hosting from one IP. Someone else can take a crack at that.
0 
Thank you for your response.
I will give it a try although, i'm not too sure how to setup the DNS and DHCP on the server. will that change things with my current website?
0
Moving DNS and DHCP services to the server will not affect your website, nor will it solve your problem, but it makes much more sense to use your server for those services than the router. You will have more control, better reporting, event logging, etc.
Neither is difficult to set up. Neither will hose your system if done incorrectly. In a worst case, if you really screw up, you can remove and reinstall the service without fear (I can't guarantee it, of course). There are lots of primers on the 'net and the Windows help system on both, but your best bet is a book from MS press or written by Mark Minasi
Typically you cannot access the WAN from the LAN across a router, so what is happening is expected behavior. This is to avoid IP spoofing. Your LAN users have to use the LAN address, or get them a separate internet connection (and router of course).
Ah, just thinking about this, I haven't tested it, but perhaps a manually edited hosts file would allow the LAN users to access the sites by the DDNS name.
0
Thaks for your reply,
I tried to move my DHCP/DNS servers to my Server I first turned off DHCP in my rounter, then set the network card for an IP of 192.168.0.1 then I lost my remote desktop access :( so went to the server and setup a DHCP service from there, I setup an IP scope, of 192.168.0.20 - 80 I wasnt sure what to set the Default Gateway and DNS Server to so I set it to 192.168.0.1 for both.. I cant connect to the internet, no network, and on my server cant even get my default web site to come up without a SQL Database error. and the website is offline. I guess I just dont know what to do, it doesnt seem to work.
0
well my server has been down more than a half a day now, and not only that I cant even get into mysql admin, or myphpadmin, nor can I connect to the mapped network drives.. I have everything back to the original settins.. but it is not working. I should have left the DHCP server up to the router.
0
No you shouldn't have left it on the router, you should study up instead of just jumping in.
However, you can easily turn off or even delete the DHCP service on the server if you want. Then go to the workstations, open a command prompt and type ipconfig /release <CR> then ipconfig /renew <CR>. If the DHCP service is running on the router, the host will pick up an IP from it.
0
Sounds like you need to do some home work, especially if you are trying to run a production server.
0
well I do know a few things ;) I have no problems on the "workstations" the 5 PC's for my daughters, they all have internet, thats not my problem. I can remotely access the server with remote desktop and FTP but not networking, I was thinking that I for somereason dont have the permissions after the Server IP change, but in the permissions it does list my computer as a domain controller, and I set it for all the permissions on the Server Drives. I know how to turn on/off DHCP services and renew ip's I just dont understand why the server cant see my network any more and theres no connection there. And why my web server is not working since I did chage the web service to the correct IP in the IIS and edited one php config for the sql data base to the correct ip's so i'm pretty stumped why my web service is no longer visible to the internet. This is just a hobby for me I have been busy 2.5 weeks with, before that I had no idea what a server was, so i'm learning every day, thats why I use these forums, thanks alot. So why is is important for me to use my server for the DHCP service? I dont need to manage any workstations just get my website out and eventually host for friends.
0
It is important that you clients receive proper TCP/IP settings so that your network clients can find the domain controllers. If you are using a router's DHCP service then you are not receiving the proper DNS configuration.
So, when you setup your DHCP server, the Default Gateway should be that of your router and the DNS server should be your local domain controller. When this is properly configured your clients will use your domain controller as the primary DNS server.
On your DNS server configure your ISP's DNS servers as forwards for Internet name resolution. Also, don't forget to assign your server with static IP configuration, and yes, assign the DNS server setting to that of the local host. Now you should be good to go. This is why it is important to run your own DHCP. If not, you can always assign static TCP/IP settings.
In reading your explanation, it appears to me that your errors are the result of DNS/network issues.
Once you have forwarded port:80 at the router from the external to the internal IP address hosting the IIS server you should have a Web presence. Post back if you need more help.
0
Thank you people for your help.
I am still checking up here. I have it at the moment back to my original settings, it works. I'm a bit aprehensive to do that again unless I have, some kind of network tech sitting here. Not saying I am giving up. I will do it but I'm going to do my homework.
0
I really cannot find anything about my problems. I've searched the net everywhere.
Before, my configuration was Internet > Cable Modem > D-Link wireless router > client computers (on a workgroup)
I now have a server (actual server hardware) and I, obviously, want to integrate it, making it the backbone of the entire network. I purchased a domain name, xaelophone.net in anticipation of the project at hand.
I want something like this: Internet > Cable Modem > router > server > client computers but that doesn't make sense because I would have to have a million network cards in my server for each computer I want connected. So I thought I might try Internet > CM > server > router > clients.
I am so confused about what to do. Every client workstation on the network is running Windows XP Professional, and the server is running Windows Server 2003.
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
