ICTCity

Let's say that I don't have an answer. This is my though: Don't disable the loopback check, actually it's not causing problem... right? What you could do is to specify NTLM host names, which is easy and safe. I really don't know which is the best solution. I had just one time this problem and I resolved with NTLM host names but I didn't make any test to understand which scenario is better.

Also if you don't use / have IIS, check this KB: http://support.microsoft.com/kb/896861/en-us

In which way are you connected to the server? It's a remote desktop connection?

You are almost done with your job... To configure DHCP there's the wizard (when you add the DHCP role), doesn't matter the external interface, when asked, select the internal interface (private, LAN). Anyway if you want a step-by-step... Regarding the sharing... actually you are not sharing the connection, or at least you don't have to... you can easily ROUTE the connection from NIC 1 to 2. Once again to set up ROUNTING in server 2008 there's a wizard which is really easy (your scenario is not complicated), but if you need a step-by-step...

Can you post the result of ipconfig /all on the computer / server which has this problem?

Welcome!

Right... and post the network config (DNS, Server + Workstations config).

You can create a cluster of webserver with a proxy. Once you need to reboot a server, your proxy forwards all the requests to the only alive server. Usually a proxy is made with linux and it doesn't need so much updates.

Everything depends on you set up the permission on root and sub folders. When you assign a permission you can open the advanced tab of that folder and select EFFECTIVE permission and specify the username or group to determine which permission is applied. Remember: the most restrictive is applied.

I don't know if it is right... I mean... yes it's right at network level, but I don't know if the 192.168.0.200 is a DNS server... but if it is... ok no problem. I only hope that yours servers have a static IP. If you need more help, try to be a bit more specific.

OK, it's the same scenario? Domain users? The file server is also the DC? Or you use the "old" DC? Try to enable the security and folder auditing to determine why your user cannot access that folder. Other that, run a EFFECTIVE PERMISSIONS on that folder for that user. Maybe we can understand something more.

Yes it is. But in most cases you assign just the internal DNS, then is the internal DNS itself that forward request to root servers.

this is the only traffic you can't see?

Which is not a protocol... You connect via HTTPS? VPN? How this connection works? Anyway the best thing is to add another Nic on your server, connected in front of the router, so you will have both interfaces sniffing inside and outside.

The remote connection is on which protocol? if there's a tunnel you could not see that traffic.

That means you have 2 dhcp server or one but misconfigured. Check under SCOPE of your windows dhcp server if there's the correct DNS server, if it is correct, well you have somewhere another dhcp server. Check this article to better understand how to setup the dhcp server: http://www.windowsnetworking.com/articles_tutorials/How-to-Install-Configure-Windows-Server-2008-DHCP-Server.html

Hi, You should tell me more... Let's say you have this situation: Server: NIC 1 = LAN NIC 2 = WAN Terminal service running on both interfaces. You want that users can logon ONLY via NIC 1 (or NIC 2), right?

Well... if you can't see some traffic from WAN to server this is normal, because actually it doesn't reach your switch. The problem is that you should see all the traffic if your switch is mirroring in the right way. What are you using to monitor your traffic? How can you say: "I'm still missing lots of traffic"?

Who is providing addresses? in other words, who is your dhcp server? If it is under windows: under DHCP settings, you can easily assign the DNS ip.

try to un-join domain and re-join.

Yes but this will control ONLY the traffic from the switch to internet and viceversa. Internal communications (pc to pc) will not be seen. Check if your switch has port mirroring or something like that, so you can resend all the traffic in your switch to a single port and then sniff it.

yes. But I don't think this is a credentials problem. Try (just a test) to share a folder with FULL CONTROL in both, ntfs and share permissions. Try if changes something.

Hi, I'm quite sure there's a policy where you can allow "anonymous" autentication but this is only needed when you can't connect to windows server 2008. IN your case I think the problem is a compatibility, unlucky this OS (win 95) is no longer supported by microsoft so I can't even open a ticket. I just think there's not a solution because this is not a "policy" setting, but it looks like your client doesn't know how to handle the way windows server 2k8 gives shares to you.

Select the folder, security > advanced > effective permission and select the user which can't write. Verify the permissions are correct. I think there's another inheritance somewhere.

I don't understand... WHO is failed?!