We help IT Professionals succeed at work.

Users cannot access companyweb

TDiscart
TDiscart asked
on
Medium Priority
648 Views
Last Modified: 2012-06-27
Users are working in domain (windows 2003 SBS) but after changing the server ip adress (and also DNS) the companyweb is not accessible anymore.
Comment
Watch Question

When you changed the DNS for your server, did you also change the DNS entry for companyweb?

Test by running "nslookup companyweb" at the command prompt, and make sure that it resolves to the correct IP address.

Another thing to check for, is the IP assigned to the "Companyweb" website in IIS.

Open IIS Admin, Expand the Server tree, Expand "Web Sites", and find the "companyweb" website.

Right-click the "companyweb" and go to Properties.  On this Properties window, there will be a "Web Site" tab.  Go to that tab, and check the IP Address field.

Author

Commented:
Hi Russel124,
1.
I did the nslookup test.
*** Can't find server name for address 192.168.254.2: non-existing domain
server: Unknown
address: 192.168.254.2

***unknown can't find companyweb: non-existing domain

2.
IP assigned to the companyweb
ip address: 192.168.254.2
tcp port: 80
ssl port: 444

I think the DNS is not right configured?


It looks like you need to create a new dns entry for companyweb in your DNS.

Open the DNS Server Snap in, Expand the tree under your server name, expand the "Forward Lookup Zone", and select the folder that corresponds with your internal domain (I.E. acme.local).

When you are on your domain forward lookup zone, you should see some entries on the right pane of the admin console.  Make sure there is a "Host (A)" type entry for your server, and that it has the proper IP address.  There should be one already, but it is good to double check.

Assuming there is a host record already for your server, you need to create a new "Alias (CNAME)" record.

Right-Click on the right pane of the admin console, and select the option for "New Alias"

In the window that appears, enter "companyweb" for the Alias name.  The first FQDN automatically be filled with your internal domain name (companyweb.acme.local).  Finally, enter the FQDN for the target host.  I don't remember exactly, but I think there is an option to browse for your server on this final field.

If not, enter it as follows:

For example, if your server was named "sbs-server-1" in the "acme.local" domain, the FQDN for target host would be:

sbs-server-1.acme.local.

Very important to note the trailing period after the .local, you need that for the FQDN.

Click OK, and close down.  Double check that companyweb resolves with nslookup.

Now whenever you lookup "companyweb", your dns server will just point it to the server that was specified in the CNAME entry.

Daniel KruegerCS Student

Commented:
Where is the DNS Server Snapin?
The DNS Server snapin should be located in the "Administrative Tools" folder on your server.  You can find the Administrative tools in the "Control Panel".  Once in the Administrative tools folder, there will be an object titled "DNS".  That is the DNS management console, which can be called a Snap-In.  

If you are creating your own Management Consoles, when you add the different management tools, such as DNS, DHCP, Active Directory Users and Computers etc, they are referred to as snap-ins.  

All of the links in the "Administrative Tools" are just single, stand alone snap-ins in their own MMC console.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.