Re: RWW not connecting to desktop BOSS

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: RWW not connecting to desktop BOSS
    ... RWW problem solved. ... desktop BOSS appears to be a DHCP issue, as both the server and desktop ADMIN ... I was able to use Remote Desktop Connection to ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW not connecting to desktop BOSS
    ... 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. ... Desktop Connection to connect and to log into BOSS (by specifying ...
    (microsoft.public.windows.server.sbs)
  • Re: Ohio Presidential Debate
    ... will know what these workers are up to, ... It's very easy to spot the connection, ... her boss has no clue as to what she is up to. ... Calling an illegal alien an "undocumented worker" is like calling a ...
    (comp.security.firewalls)
  • Re: Ohio Presidential Debate
    ... It's very easy to spot the connection, ... woman who surfs through my proxy, from her work, and ... her boss has no clue as to what she is up to. ... Oh, you're a lady's man too, a lover and a womanizer on the Internet -- ...
    (comp.security.firewalls)
  • Remote desktop connection over internet
    ... How to find my boss's PC is behind a firewall/NAT/router ... How to find out my PC's and my boss PC's permanent IP ... >I got two computer in lan connection using Windowsxp OS. ... >While connecting (Remote desktop connection) I am ...
    (microsoft.public.windowsxp.work_remotely)
Loading