There is a lot to do for that. Better start reading - plenty of resources on the Internet, including online classes that will help learn about this. Get your Googling or DuckDuckGo limbered up for some serious searching.

I'll give you my two cents.

1a. Can I setup my server in the same computer that I will be working on?
Yes, you can.

1b. Can I setup two servers in one PC?
Of course, you can. There's no problem with a web server and database server running in the same computer. However, scaling horizontally can be problematic if you it this way.

2. Which will be better?
Depends really on you and your use case. To help you decide, here's a list of "characteristics" of each setup.

Server in the same computer

  • Easier deployment. No need to transfer code from one machine to another. Instant results.
  • You won't really be worried much about dependencies compared to a server on a different machine.
  • You can easily ruin your website. One mistake in the code and the website can come crashing down.

Server in another PC

  • Harder to deploy compared to the previous setup. You have to transfer code from one machine to another.
  • Dependencies can be a problem. Wrong version of a library in the server machine and your website won't probably be able to run.
  • Less chances of your website going down. This is assuming that the version of the website you upload to the server machine is stable.

3. What about security? How can I make sure that my customers informations are secured?
Going for an HTTPS connection is thumbs up. However, do not forget about basic web security. Never store passwords in plainmtext. Never forget to sanitize your user input. And the list just goes on.

4. As this will be my final project, will it be better to have the servers on my PC or will it be better to use cloud server?
I would suggest going for the cloud in order for you to focus more on your code than on handling the servers. Just make sure your cloud service has at least 99.9% uptime.

I hope that helps. :)

  1. You didn't reveal much about your computer OS and such so for Windows, try a WAMP. (Windows Apache MySQL PHP). For Linux, that's a LAMP.
  2. Better can be a trap. You can always debate if option 1 is better than option 2.
  3. Since this is likely to be a school project, simple https will do. As to database security, there are tomes about it but for now, concentrate on your big project and make the connections secure.
  4. As it's your final project, you need to be bullet proof. If you went with the cloud you don't own, imagine your grade if the cloud is offlined by its owner or something. You must deliver a working system so the cloud is only an option if it's your cloud.

I will soon start my project, but before that I need to set up my server my project is shopping website so I will need web server and database server for the custoerms information. I have couple of question:
1- Can I setup my server in the same computer that I will be working on and can I setup two server in one PC
2- Which will be better
3- What about security how can I make sure that my customers informations are securied
4- as this will be my final project will it be better to have the servers on my PC or will it be better to use cloud server

Thank you

It's all about automating how switches talk to each other. I'm not personally a 'fan' of letting networks do this type of thing. I mean, letting it auto detect duplexing and speed is one thing, but letting the switches determine what ports will trunk seems kindof useless and can be a bit dangerous.

For the novice, i suppose it can help with setting up trunking.... but seriously, If you can't design and manage your inter-switch trunks, you probably shouldn't be doing this job in the 1st place.

I might be a little old-school, but I like to set my networks up manually, and turn off this extra auto discovery stuff that cisco has inplemented. I like to know exactly where my switches trunk, over what ports, what VLANS are allowed over tunks, etc...

I know what the modes are - I just don't see the point in what seems like redundancy.

o Switchport mode trunk - forces the interface to become a trunk and negotiation will occur to confirm match with the connecting device.
o Switchport mode nonegotiate - DTP is disabled on the interface. This can prevent useless network communication on access ports.
o Switchport mode dynamic desirable - asks the connecting device on the port using DTP if it wants to trunk. If it doesn't, the port becomes an access port.
o Switchport mode dynamic auto - if a device asks this port to become a trunk, it will become a trunk. It will not ask other devices to trunk and will function as an access port until asked to trunk.
o Switchport mode access - this port will never trunk. DTP will be sent out to the connecting device to make them aware of this.

If it's an access, then do switchport mode access. If it's a trunk, do switchport mode trunk. Why waste time with the other ones other than maybe switchport mode nonegotiate to shut off DTP if it's an access port?

Good Afternoon,

I've been studying communications between switches and it seems relativly easy to understand with the exception of why they have so many modes. There's trunk, nonegotiate, dynamic desirable, dynamic auto, and access. (I think that's all of them). In addition to this, some switches can choose between dot1q or ISL encapsulation. So what's the purpose of all the different modes?

If the port is a trunk, set it as a trunk. If the port is access, set it to access. Is there benefits to using dynamic desirable or dynamic auto?


What sort of restrictions you are talking about? Please ellaborate

Well I have been using Syncrify as a third party back up software along with my QNAP and it is working absolutely fine. I would say much better because the features provided by Syncrify are really useful like incremental back up which saves a lot of my time, remote access which give me a better control of my data and there are many others.

You may try Syncrify as well. It might be helpful for you as well.

What reservation length did you setup on your scope? IF you set it to never expire, then you you can be out of addresses.
For wifi, I use 8 hour to 1 day, for Ethernet based scopes, I use 7 days. But those numbers are totally up to you.

Look at your server's dhcp panel....
Is the scope active?
How many leases are currently in use?
Is DHCP services running?

I have a WIndows Server 2003 unit which runs DHCP. Lately, no one is able to connect to our WiFi access point; and even plugging an Ethernet patch cable into the wall usually results in no IP address being assigned to that no INternet.

I'm not that familiar with DHCP, but it seems like we've "run out of IP addresses."

Our network is the range. We do have a block of about 20 addresses reserved for our SIP trunk phones, and maybe 10 addresses near the bottom end reserved for servers, printers, etc...but why are the other 100+ addresses seemingly not available? How can I make them available?

Thanks in advance.