ICTCity

yep for each domain / IP. It's not a good thing you login via HTTP, try to set the HTTPS at least. Anyway, you should implement a maximum attempt (let's say 3) and then block for a while (10-20 mins) the account. I don't know if this can be made by phpmyadmin, just google a bit :)

You must configure a SCOPE on your DHCP for option 6 and 15 this will give yours clients DNS config and (with option 15) domain name. Let me know.

Everything works fine right now. For your internal problem follow this simple step: (on your DNS config): replace 192.168.0.2 with 122.61.186.232 Let me know.

Hi, there's a log located here: C:\WINDOWS\system32\Logfiles You must right click your FTP site > properties > select ENABLE LOGGING then you should select W3C format.

It can't work, if you put the same ip of your router (10.0.0.1) your network simply doesn't work. The problem is that you CANNOT surf (actually exit) from your LAN (10.0.0.0) also with others computers. It looks like there are 2 same IPs. Maybe you have mis configured a static or DHCP IP somewhere. Is it possible?

Hyper v has an address of 10.0.0.0 and the other interface (LAN) is on the same network (10.0.0.0)

Wait, if you have the 3rd Nic with the same IP class of your LAN 10.0.0.0 you must do the same work you do for the other interface, so routing will be made correctly.

Hi, first of all write in english. Regarding your problem, you can deploy a windows installation on a different hardware BUT pay attention to the following things: If you have static IP and you power up both servers, you will have a conflict. The same for the computer name. There are tools made for this task, for example Acronis True Image Universal Restore. The most important part are drivers, which may be different.

You can use an easier way: go to C:\windows\system32\drivers\etc\ and open the file HOSTS. Add the following line at the end: IP_DOMAIN_CONTROLLER YOUR.DOMAIN.WHATEVER Retry :)

Be sure that RRAS doesn't use that interface to do something.

The first one works like a charm. The second points to 403 (forbidden). You have two chances: Implement a redirect: http://www.webconfs.com/how-to-redirect-a-webpage.php Or implement a redirect everytime the 403 error appears. This can be made by the IIS manager console.

That's ok, install DHCP and nothing else. Tell me if after a reboot something changes.

I can't understand what is happening. Here's my though: if your traceroute stops to your "router", it means your router doesn't know where to send packets. But this is something which should apply to all devices on the 10.0.0.0 network and cannot be resolved with a fresh install. After a fresh install, everything works fine, but IN WHICH WAY your server can change the routing of your router? The only thing I can think is that your server is starting to be a router and "spoof" the IP 10.0.0.1 in some way. This theory can be correct because the problem starts when you RESTART your computer (so the routing service is started). Can you reinstall the server without any roles?

Ok, now try to reconfigure your server so it will have access to internet and retry the tracert. Let me know.

I hate spam... really. You have just 2 solutions: http://www.untangle.com/Solutions/Package-Comparison-Matrix The free edition contains a SPAM filter which can control also outbound e-mails. Buy an appliance, for example Aladdin eSafe. Nothing else... sorry...

I don't understand your problem. If I type: http://www.accesscontrolsystems.co.nz/ I can see a website called template with 2 girls. If I type: http://www.guitaronline.co.nz/ I can see the phpinfo() information's page. Where's the problem?

there's something wrong with bindings or routing, but actually I can't figure out what is the exact problem.

Hi, It's an easy stuff if you have Vista / 7 s clients, for XP is a bit different. The GPO you are looking for is called FOLDER REDIRECTION which is located under USER. You have 3 choices on that policy: Not configured, Redirect to specific folder (so you MUST create a folder), Redirect to profile folder (this will automatically create a folder).

Yep, in some way yes... But let's start from the beginning. You started a traceroute from 10.0.0.X to 10.0.0.1? You should be a bit more precise :)

Well done :) Good for you that you have universities in network, here in Switzerland are all for programmers -.-

Yes, it is correct. You must add the account(s) to the LOCAL ADMINISTRATORS GROUP (on the server side, where you can access shares only with Administrator's account).

Yeeeeep, VLAN is a VLAN, Virtual Network is a Virtual Network :P So now it's a bit more clear. I just want to know WHERE it stops, this can be made only by issuing a tracert command.

VLANs are used to SEPARATE networks, it's like having two NICs, one goes to X and the other goes to Y but one doesn't know anything about the other. Now, if you say that VLAN take an IP from the LAN, there's something wrong. VLAN cannot communicate with LAN unless you UNtag the packet. If you have a VLAN is to separate things, so, WHY you should put everything back together? Every switch / router has its own config, but from what I know, a switch MUST be programmable (and programmed) to manage VLANs. VLANs are easy: when the packet arrives, it's tagged with the VLAN ID, somewhere it will be UNTAGGED to come back. What I think is that when you configure your network, everything works because of you have the same IP (10.0.0.X) on every server and everything is on the same network. When you restart, the "real" configuration is applied and your switch doesn't know HOW to manage the VLAN tag. You can do a test: when you have lost connectivity to internet, try to ping 192.168.1.101, then ping 192.168.0.1 then traceroute the ip 8.8.8.8. In other words run the following command in the command prompt and post results: ping 192.168.0.101 && ping 192.168.0.1 && tracert 8.8.8.8

try to completely remove IIS: Step 1: Remove IIS To remove IIS, follow these steps: In Control Panel, double-click Add or Remove Programs. Click Add/Remove Windows Components. Click Application Server, and then click Details. Click Internet Information Services (IIS), and then click Details. Click to clear the check boxes for all subcomponents except Common Files, click OK two times, and then click Next. Follow the instructions to complete the process. (from KB: http://support.microsoft.com/kb/320202)

For me the problem is still the VLAN. VLan is used for separate physical LANs, the point is that your switch MUST support VLAN tagging (protocol 802.11q). I cannot test your solution, but actually I don't think you can have a LAN with IP 10.0.0.0 and a VLAN with the same address. Are you sure your switch supports VLAN TAGGING?