Search results for query: *

Selina lengoo is correct if you are using a private IP address class for your LAN you will need to setup a NAT (Network Address Translation) rule on your fire. The private IP Address ranges are as follows. 192.168.0.0 - 192.168.255.255 172.16.0.0 - 172.31.255.255 10.0.0.0 - 10.255.255.255 The...

If you have a firewall you might check to see if Port 80 is being blocked on the Wan interface. If you are using one of the private IP address ranges internally you may also need to setup a NAT rule to point to the IIS server. What Version of Exchange are you running? If you could please post...

zbnet, I unchecked the "Disable Automatic Replies to the Internet". Restarted the service and it is still doing the same thing. Thanks JC

zbnet yes it is. It it also ticked on the old one IMS connector. I'll untick it and see if that solves it. I did notice the the GWART0.MTA routing table in the MTADATA directory has the old connector listed first. Could that be causing this issue? Thanks, JC

I have a situation where I need to rebuild our current Exchange 5.5 box. I have joined an additional Exchange 5.5 server to the site and successfully moved all of the mail boxes over to the new server. I created a second IMS connector on the new server and then pointed my firewalls SNAT rule to...

Have your verified that the service SMTP service is running?

Is this correct or is it a miss print?? WAN IP Address: 70.21.206.187 Subnet Mask: 255.0.0.0 Default Gateway: 10.5.12.1 If it is I do not see how you can be hitting the internet at all. The first octet should be the same for both the WAN IP anf Default Gateway. Can you post the...

Not to mention if you start using address's that are already leased to somebody you would be exposing your company to a possible lawsuit. You setup a linux SNAT box on an extra system for a very reasonable rate and you could use the 172.16.0.0 range.

In a class C subnet there are a total of 256 address , but only 254 are usable. Let's look at the subnet the you are using. 192.1.1.0 is used for network identification. 192.1.1.1 - 192.1.1.254 can be assigned to clients (nodes) 192.1.1.255 is used for network broadcasts Since you are using a...

Have you verified the the patch cables are good? On the linksys are the desired ports open for use from the LAN? Have you tried hitting the reset on the linksys I have seen them lockup? When you pinged the FQDN of your DNS server as Seaspray suggested and if you have did it work? Can you access...

Can you ping any other systems from the server in question? Do you have link lights on the servers nic(s)? Have you verified the the patch cables are good?

What are the IP settings on the router?

What happens when you ping the Linksys from the server?

What subnet mask are you using? Thanks JC

Here a link that might help you. http://www.eventid.net/display.asp?eventid=675&eventno=62&source=Security&phase=1

Have you verified that your IP settings are correct on the nic that is connected to the DSL router?

Try using the /enforce option with secedit this will usually work. secedit /refreshpolicy user_policy /enforce If for some reason it does not work look in the event viewer and post any errors here. JC

You need to uninstall the Terminal Server Liscensing. When you installed the Terminal Server Licsensing your TS installtion turned on the Application Mode which does require that you setup a licensing server and you would need to get a pin from MS. Since you are only using TS for server...

You need to create a sysprep answer file. You will find the information of how to do that on the installation cd under Support > Tools in the Deploy.cab file. There is a tool in that cab named Setup Manager. You can use it to create the answer file for you. You will need to open the file after...

You could try to create a logon script that maps to the printers. Put all of the users on the new subnet into a seperate OU and apply the logon script policy to the new OU.