Re: RWW not connecting to desktop BOSS

Hello,

Thank you for your post.
My name is Gary Wang, and it is my pleasure to work with you on this issue!
Please allow me to confirm that my understandings are correct. As I
understand it, the issue is:

You client's IP address PTR record not update correctly which caused RWW
remote desktop cannot work properly.

If I have misunderstood your concerns please feel free to let me know.

Suggestion :
==============
According to your description, I think this issue may due to the DNS server
is not performing dynamic update. I would like to suggest that you check
the following:

1. Check DHCP server's dynamical update configuration.

a. Open DHCP server, right click the server's FQDN and select Properties.
b. Navigate to DNS tab.
c. Select the "Dynamically update DNS A and PTR records only if requested
by the DHCP clients" check box.

2. Make sure dynamical update is allowed on your DNS server.

To configure the zone to permit dynamic updates, follow these steps:

a. Click Start, point to Programs, point to Administrative Tools, and then
click DNS.
b. Expand the server that you want to work with, and then expand Forward
Lookup Zones or Reverse Lookup Zones.
c. Right-click the zone that you want to work with, and then click
Properties.
d. On the General tab, click Non-secure and secure in the Dynamic updates
box, and then click OK.

You can also verify the configuration of the zone by using the Dnscmd.exe
command-line tool. Dnscmd.exe is included in the Windows Server 2003
Support Tools package. To display the current configuration of a zone,
follow these steps:

a. Click Start, click Run, type cmd, and then click OK..
b. At the command prompt, type dnscmd / ZoneInfo ZoneName, and then press
ENTER.

Note: ZoneName is a placeholder for the name of the zone whose
configuration you want to display.


3. Make sure the local name server's SOA service record has a correct name
server listed. To verify that the server responds and that the response is
accurate, use the nslookup command.
To use the nslookup command to verify that the client's configured DNS
servers correctly answer queries, follow these steps:

a. Click Start, click Run, type cmd, and then click OK..
b. At the command prompt, type nslookup, and then press ENTER.
c. At the prompt, type set query=SOA, and then press ENTER.
d. At the prompt, type TargetZone, where TargetZone is the name of the zone
that you want to verify.

For example, if you specify reskit.com as the target zone, the information
that is returned may look similar to the following:Server:
name-server.dev.reskit.com
Address: 134.67.123.245

Non-authoritative answer: reskit.com
primary name server = dns-server.reskit.com
responsible mail addr = admin
serial = 2413358
refresh = 900 (15 minutes)
retry = 600 (10 minutes)
expire = 86400 (1 day)
default TTL = 3600 (1 hour)

dns-server.reskit.com Internet address = 134.66.1.11

To verify whether the response is accurate, consider the following
questions:

a. Is the SOA data in the response of the server accurate?
b. Is the authoritative DNS server that is identified in the SOA record
correct?
c. If the DNS server is correct, is the IP address that is listed for the
server also accurate?

If the server does not respond or the data that the server returns is not
accurate, address these issues before you continue.


4. The server may not accepting dynamic updates because the target zone is
currently being transferred. To determine if this is the cause of a
unsuccessful DNS update, check the DNS log in Event Viewer. Specifically,
look for zone transfer events that occurred at the time that the client
tried to perform an update. Typically, zone transfers are operations that
require short periods of time. Because of this behavior, it is unlikely
that an attempt by a client to dynamically update a DNS zone can be
prevented two times in a brief interval because of zone transfers. To
eliminate zone transfers as the cause of an unsuccessful dynamic update,
run the ipconfig /registerdns command on a client shortly after the client
cannot successfully update a DNS zone. Record the time, and check the DNS
event log to determine if a zone transfer was performed at the same time
that you ran the command.

Another method to eliminate zone transfers as the cause of unsuccessful
dynamic updates is to stop zone transfers for the target zone on the server
that the client is using to make the update. To do this, follow these steps:

a. Click Start, point to Programs, point to Administrative Tools, and then
click DNS.
b. Expand the server that you want to work with, and then expand Forward
Lookup Zones or Reverse Lookup Zones.
c. Right-click the zone that you want to work with, and then click
Properties.
d. On the Zone Transfers tab, click to clear the Allow zone transfers check
box, and then click OK.

You can also use the Dnscmd.exe command-line tool to stop zone transfers.
To stop zone transfers to or from a specific zone, follow these steps:

a. Click Start, click Run, type cmd, and then click OK..
b. At the command prompt, type dnscmd /ZoneResetSecondaries reskit.com.
/NoXfr, and then press ENTER.

When zone transfers are stopped, determine whether dynamic updates are
still unsuccessful. If dynamic updates are still unsuccessful, use the
other suggestions in this article to troubleshoot the problem.


If we cannot resolve the issue after we perform the above steps, please
help me collect some information for further investigation:

Information Need
==============
1. Check event viewer on both SBS server and client for related
information, if there are any, please help save it to *.evt and send to me
at v-gzwang@xxxxxxxxxxxxxx
2. Run the command "ipconfig /all > c:\ipconfig_sbs.txt" on SBS, send the
files c:\ipconfig_sbs.txt at v-gzwang@xxxxxxxxxxxxx
3. Run command "ipconfig /all > c:\ipconfig_client.txt" on problematic
client, send the files c:\ipconfig_client.txt to me at
v-gzwang@xxxxxxxxxxxxxx
4. Is there any other client has the same problem?

Additional Information
==============

Using DNS servers with DHCP
http://technet2.microsoft.com/windowsserver/en/library/d0e19b57-c368-46c2-b0
17-caf25ae150ec1033.mspx?mfr=true


How to troubleshoot Windows Server 2003 Domain Name System Dynamic Update
problems
http://support.microsoft.com/default.aspx?scid=kb;EN-US;842200


I look forward to your reply. Also, if you have any questions or concerns,
please do not hesitate to let me know. I am happy to help. :-)

Thank you for your time and cooperation!

Best regards,

Gary Wang(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: RWW not connecting to desktop BOSS
| thread-index: Aci3aAu/KoSJ9LbTSVirlNOWFoknQA==
| X-WBNR-Posting-Host: 207.46.19.197
| From:
=?Utf-8?B?R3JlZyBLaXJrcGF0cmljayBbU0JTQyxNQ1RTLVZpc3RhLE1DSVRQXQ==?=
<greg@xxxxxxxxxxxxxxxxxxxxxxxx>
| References: <DA16606A-C21A-427A-9229-40E81E79F139@xxxxxxxxxxxxx>
<OINbGkqyHHA.5380@xxxxxxxxxxxxxxxxxxxx>
<D7665B52-F9BD-4349-B551-19B759EAB0F2@xxxxxxxxxxxxx>
<5D8D4BD5-B309-48AE-AF3F-30A709E723A2@xxxxxxxxxxxxx>
<18FA582F-1415-4D2F-93EA-38B1C2E3B929@xxxxxxxxxxxxx>
<44E0BA80-924B-4515-92C7-876BA1912D47@xxxxxxxxxxxxx>
<FB00DDA5-ADC2-4723-9B72-FDE62592249E@xxxxxxxxxxxxx>
| Subject: Re: RWW not connecting to desktop BOSS
| Date: Fri, 16 May 2008 08:18:08 -0700
| Lines: 121
| Message-ID: <FD0E9B60-D0A8-4A45-8085-70E55D2313DD@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:108069
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| A followup to this:
|
| When looking at DNS (from Administrative Tools) recently, and looking at
the
| Reverse Lookup entries, I noticed that BOSS was still, incorrectly,
pointed
| to an old address -- 192.168.16.19 -- when in fact its current IP was
| 192.168.16.29 -- so I deleted the erroneous entry. I have no idea why
the
| server would retain an old entry like that, but it did, and it would seem
| that was the cause of the "ping by name" error.
|
|
| "Greg Kirkpatrick" wrote:
|
| > RWW problem solved. At one point, RWW stopped working, then following
a
| > restart of the server, it worked again. The problem with connection to
| > desktop BOSS appears to be a DHCP issue, as both the server and desktop
ADMIN
| > thought BOSS was at 192.168.16.19, when it actually was at
192.168.16.17.
| > Manually placing BOSS at .19 "fixed" the RWW issue, so it wasn't a
firewall
| > or RWW problem at all.
| >
| > "Greg Kirkpatrick" wrote:
| >
| > > I was able, this weekend, to use Remote Web Workplace (from outside
the
| > > office) to access desktop ADMIN, but I could not connect to desktop
BOSS.
| > > When I tried to ping BOSS, from ADMIN, it tried to look for it at
| > > 192.168.16.19 -- which is wrong (it's on .17).
| > >
| > > Today, their office is closed.
| > >
| > > When I tried to use RWW (from outside the office) again today, I
could not,
| > > nor could I ping the server. I was able to use Remote Desktop
Connection to
| > > connect to and log into the server, and from there, I was able to use
Remote
| > > Desktop Connection to connect and to log into BOSS (by specifying
| > > 192.168.16.17).
| > >
| > > From server:
| > >
| > > Ethernet adapter Internet Network Connection:
| > >
| > > Connection-specific DNS Suffix . :
| > > Description . . . . . . . . . . . : NVIDIA nForce Networking
Controller
| > > Physical Address. . . . . . . . . : 00-E0-81-5D-A8-04
| > > DHCP Enabled. . . . . . . . . . . : Yes
| > > Autoconfiguration Enabled . . . . : No
| > > IP Address. . . . . . . . . . . . : w.x.y.z
| > > Subnet Mask . . . . . . . . . . . : 255.0.0.0
| > > Default Gateway . . . . . . . . . :
| > > DHCP Server . . . . . . . . . . . : 192.168.1.254
| > > DNS Servers . . . . . . . . . . . : 192.168.16.2
| > > NetBIOS over Tcpip. . . . . . . . : Disabled
| > > Lease Obtained. . . . . . . . . . : Monday, July 23, 2007 1:30:17
PM
| > > Lease Expires . . . . . . . . . . : Monday, July 23, 2007 1:32:17
PM
| > >
| > > Ethernet adapter Server Local Area Connection:
| > >
| > > Connection-specific DNS Suffix . :
| > > Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet
| > > Physical Address. . . . . . . . . : 00-E0-81-5D-A8-03
| > > DHCP Enabled. . . . . . . . . . . : No
| > > IP Address. . . . . . . . . . . . : 192.168.16.2
| > > Subnet Mask . . . . . . . . . . . : 255.255.255.0
| > > Default Gateway . . . . . . . . . :
| > > DNS Servers . . . . . . . . . . . : 192.168.16.2
| > > Primary WINS Server . . . . . . . : 192.168.16.2
| > >
| > > From desktop BOSS:
| > >
| > > Windows IP Configuration
| > >
| > > Host Name . . . . . . . . . . . . : BOSS
| > > Primary Dns Suffix . . . . . . . : mycompany.local
| > > Node Type . . . . . . . . . . . . : Hybrid
| > > IP Routing Enabled. . . . . . . . : No
| > > WINS Proxy Enabled. . . . . . . . : No
| > > DNS Suffix Search List. . . . . . : mycompany.local
| > > mycompany.local
| > >
| > > Ethernet adapter Local Area Connection:
| > >
| > > Connection-specific DNS Suffix . : mycompany.local
| > > Description . . . . . . . . . . . : Broadcom NetXtreme 57xx
Gigabit
| > > Controller
| > > Physical Address. . . . . . . . . : 00-11-11-E3-C0-3B
| > > Dhcp Enabled. . . . . . . . . . . : Yes
| > > Autoconfiguration Enabled . . . . : Yes
| > > IP Address. . . . . . . . . . . . : 192.168.16.17
| > > Subnet Mask . . . . . . . . . . . : 255.255.255.0
| > > Default Gateway . . . . . . . . . : 192.168.16.2
| > > DHCP Server . . . . . . . . . . . : 192.168.16.2
| > > DNS Servers . . . . . . . . . . . : 192.168.16.2
| > > Primary WINS Server . . . . . . . : 192.168.16.2
| > > Lease Obtained. . . . . . . . . . : Saturday, July 21, 2007
8:15:18 PM
| > > Lease Expires . . . . . . . . . . : Sunday, July 29, 2007
8:15:18 PM
| > >
| > > "Greg Kirkpatrick" wrote:
| > >
| > > > Well, I would have said that was too obvious, but the ping failed
from SERVER
| > > > to BOSS by IP and by Name. I am going onsite tomorrow to ensure
it's up &
| > > > running.
| > > >
| > > > "Henry Craven {SBS-MVP}" wrote:
| > > >
| > > > > Ipconfig /all from server and desktop ?
| > > > > Ping BOSS by IP And Name ?
| > > > >
| > > > > --
| > > > > Henry Craven {SBS-MVP}
| > > > >
| > > > >
| > > > > "Greg Kirkpatrick" <GregKirkpatrick@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in
| > > > > message news:D7665B52-F9BD-4349-B551-19B759EAB0F2@xxxxxxxxxxxxxxxx
| > > > > > Control Panel / System / Remote has a check in the Remote
Desktop box.
| > > > > >
| > > > > > Windows Firewall is superseded by ISA 2004, but Remote Desktop
is listed
| > > > > > as
| > > > > > "Yes" under Exceptions (though grayed-out disallowing changes.)
| > > > > >
| > > > > > No other firewalls are present.
| > > > > >
| > > > > > Internal RDP connection to desktop BOSS also fails.
| > > > >
| > > > >
|

.

Relevant Pages

  • RE: exchange server cannot mount mailbox store
    ... What's the exact detailed DNS Events ... Type desired internal IP address of your SBS server. ... it will delete the reverse lookup zone if the zone no longer ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Event 4515 :another copy of zone has been found
    ... running on the old 2000 server. ... I then installed DNS on ... I seem to remember hearing that if you just delete/remove the zone it ... Container), the Configuration Partition, and the Schema Partition. ...
    (microsoft.public.windows.server.dns)
  • Re: Replication between parent child domains
    ... install dns before i run the dcpromo on the melbourne server. ... DNS server will forward any query it can't answer, Checks zone ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replication between parent child domains
    ... DNS server will forward any query it can't answer, Checks zone ... DNS Servers) all queries will go to tld DNS server (including Internet ... Stub zones: Stub zones contain a read-only copy with specific records ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS Redesign Issue
    ... -Using DNS console you can right-click the zone and export to a File, ... -To export a Zone and import that Zone in another DNS Server you need to use ... Create a child zone dallas on the DNS server in the child domain ...
    (microsoft.public.windows.server.dns)