ICTCity

But this problem happens on each client? Anyway, a TTL of 55 secs is not a good idea...

try this: nslookup server 192.168.1.3 set query=all yourdomain.local.whatever Post results.

Well... actually yes but this is not logic. The problem is that you have 1 public IP, which is fine, but your clients are behind a NAT. Now, if you want to enable RDP for each pc, you must modify every single port and... REMEMBER IT! So, once you open RDP you must type: MyPublicIpAddress:PORT and the value PORT will be different for each host. If you have a network firewall, this is painful, because you must open EVERY port. Anyway, to modify the RDP port do the following: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\ select PortNumber and edit, select DECIMAL as value, and add your custom port. If you have a firewall, remember that you need to enable this port.

Here's the problem: So, let's check some settings. Right click "COMPUTER" > Properties and select the tab COMPUTER NAME. Check if FULL COMPUTER name matches with DOMAIN. Example: full name: mycomputer.mydomain.local.private domain: mydomain.local.private. This is OK. If you have something like this: full name: mycomputer.mydomain.local.private domain: mydomain.private. This is a DNS SUFFIX MISMATCH. Anyway, once you have checked these settings, type ipconfig /all on a command prompt and check the entry "Connection-specific DNS Suffix" if this is different from the domain you found in "computer name tab", right click on your network connection, properties > TCP/IP (v4) > properties > advanced > general and modify the DNS suffix.

Hi, The fastest way is to create a TRUST relationship: http://technet.microsoft.com/en-us/library/cc754626.aspx This will allow users to communicate from domain A to B and viceversa. You can do the same by adding and configuring ADFS, but actually it's not really easy.

I don't understand what are you trying to do. If you enable RDP on a client, you can connect to it by typing its IP address. If you are talking about an EXTERNAL connection this is different, and... no, you CANNOT. Or, at least, you must have a single public IP for each client...

Hi, 1) This is used only when there's a router between your DHCP server and your clients. Requests are in broadcast, broadcast doesn't pass routers. 2) No problem, assign them a static IP and they will never receive a DHCP address. 3) There's not the best answer. Let's say that if you network has 10 clients, you can set a lease of 1 hour and everything is ok, but if you have 100 clients the story changes. If your clients are almost the same everyday, you can set a lease of 6 days which is ok. 4) No, but pay attention to the scope. For example, if you set a static IP to your server (let's say 10.0.0.100) and in your DHCP you set a pool from 10.0.0.50 to 10.0.0.120, the dhcp server can assign the IP 10.0.0.100 which is in use by your server. This prevent users from accessing the server (IP conflict). You must exclude static IP from DHCP range. You DHCP DOES NOT KNOW anything about your network, it simply give an IP (if there's one free) when requested. 5) ??? can you describe your problem? 6) - waiting for answer from point "5" :P -

The problem is your DNS server, I don't know what, but you can check the event viewer for errors. Something cannot be resolved. Are you sure you've installed AD properly?

Try to disable IPv6 (from advanced configuration of your NIC)

I don't know why setting the registry via GP is not working... that's odd. Now, if you run a script to add registry key, by default it ask for confirmation. To avoid this you can change a key in regedit: HKEY_CLASSES_ROOT\regfile\shell\open\command change the value of DEFAULT to: regedit.exe /s %1? This is really unsecure because each .reg file can be executed silently. To troubleshoot the registry key not applied, take a look here: http://technet.microsoft.com/en-us/library/cc940322.aspx It's quite easy, from client run gpresult /V and check if there're any "REGISTRY KEY" received.

Hi, good question. Everything depends on what you want to do. If you need external access, mobile devices, calendars, rooms, integration with other apps and so on. These are some programs: Microsoft exchange IBM lotus notes Postfix If you need more details let me know

Where is the problem?

Double post, topic closed. http://freepchelp.forum/topic/1552-remote-desktop/page__pid__4218

Go to your server: Right click on computer > properties > (on the left) REMOTE SETTINGS > you have 3 settings: don't allow connection, allow connection (less secure), allow connection (more secure). Select the second radio button. Apply and enjoy. If you want you can install this on your windows XP (must have the SP3 installed): http://www.microsoft.com/downloads/details.aspx?FamilyId=72158b4e-b527-45e4-af24-d02938a95683 Let me know.

Ohhhh that's lovely! This is a... known bug... since 2009. But luckly this has been fixed with the hotfix that you can find in here: http://support.microsoft.com/kb/977944/en-us (already posted before). THE SADDEST part is that there's no fix for XP machines. You MUST create this key: HKEY_CURRENT_USER\Control Panel\Desktop\WallPaper and set the current path. You can do this with a script: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Control Panel\Desktop] "Wallpaper"=path

Static route :)

Hi, This is odd, anyway open task manager, click on RESOURCE MONITOR and expand everything. The most important graphic is the DISK. Start the transfer and see what happens. Maybe start with 10 GB not 350 :P. Once completed, disable your anti virus and retry, let me know if you see any difference. Just a suggestion: DC should be a DC, not a file server. You can use it as a DNS / DHCP server, but not as a File Server (security purpose).

You should be able to do this with robocopy with option /copy:datso Anyway, you can use this tool: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=10268 Good luck.

Hi there! Enjoy your stay!

probably the permissions weren't updated...

lovely ^^ I like these kind of problems XD

Are you sure you haven't confused the screenshots? The first 2 should block WILLIAM, the second two should allow him to browse folder. Anyway, can you please post the EFFECTIVE permissions by settings permissions like in the first 2 screenshot and select user WILLIAM? Thanks.

Assuming you are not trying to connect via RDP (TS), check this: http://www.grouppolicy.biz/2011/03/best-practice-using-group-policy-to-configure-desktop-wallpaper-background/ The only thing is that you are trying to connect via terminal server, and this policy cannot be applied correctly.

When you specify specific permission to a folder, you must map the directory itself. Remember that if you want to be able to list folder, there's the appropiate policy. If you can provide more details (examples) like: folder name, user name it's easier to solve the issue.

I didn't tell you to specify the domain because from your picture there was the word "SERVER\UserName" so I tought that SERVER was your domain... Anyway, take a look here: http://support.microsoft.com/kb/977944/en-us