RE: Unable to connect to RWW from anyplace other than server

Tech-Archive recommends: Fix windows errors by optimizing your registry



What URL are you typing into the browser when trying to access RWW externally
from your LAN?

Post another ipconfig from the server and a client for me to double-check.

--
Regards,
David Hartry
--


"DQ" wrote:

OK David, I beleive that I have all of my IP config issues squared away. I
am now able to see all my client machines on the network, and can
successfully connect to both RWW and ComanyWeb from anywhere on the LAN. My
remaining problem though, is that I am not able to connect from outside of
the LAN to the RWW sessions. I have opened ports 4125 and 443 on my router,
but still no luck. I have attempted to go through some of the other threads
to see if I can find my answer, but things seem to get out of my area of
knowledge rather quickly. This is the very first time I have set this up,
and don't understand a lot of the ins and outs (obviously). Would you have
any 'dumbed down' suggestions on how I might be able to get RWW access to my
server from outside of the LAN, where I am just connecting through the
internet? Thanks in advance...

DQ

"David Hartry" wrote:

I'm afraid you have quite a few issues with your IP configuration.

First of all the server is getting a DHCP address. That is not good. Did
you send the output of ipconfig to a text file or just copy the details and
type them in up here? Because the SBS really shouldn't be getting a DHCP
address, and the IP addresses all look very strange.

To redirect the ipconfig output to a text file run the following command on
both your server and workstation, then find the c:\ipconfig.txt file and post
the results up here again:

ipconfig /all>c:\ipconfig.txt

--
Regards,
David Hartry
--


"DQ" wrote:

Thank you for your reply David. Here is what I have done based on your
response: Went to a client PC, and changed my DNS server from Dynamically
assign, to the IP address of my SBS server. Once I did that, I lost all
internet connectivity, so was once again unable to connect to the remote
page. Here is an output from the server and a sample client machine:

SERVER:
DHCP Enabled: Yes
Autoconfiguration Enabled: Yes
IP addy: (DHCP) 192.168.168.6
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.168.168
DHCP Server: 192.168.168.168
DNS Server: 192.168.1.254
Pri. WINS Server: 192.168.1.14

CLIENT PC:
DHCP Enabled: Yes
Autoconfiguration Enabled: Yes
IP Addy: 192.168.1.8
Subnet mask: 255.255.255.0
Default Gateway: 192.168.1.254
DHCP Server: 192.168.1.254
DNS Servers: 192.168.1.254

What is sticking out to me so far is that my default gateway is different
between the two. What does that ultimately need to be set to for the server
and the client pcs? Thanks again in advance...

DQ

"David Hartry" wrote:

Ensure the client PC's have the SBS as their DNS server. Post an IPCONFIG
from the server and one of the clients on here for me to check.

--
Regards,
David Hartry
--


"DQ" wrote:

I am trying to set up some RWW connections for the first time, and am running
into problems. I am pretty sure I have set something up incorrectly, but I
am not sure where to look to resolve.

When I try to connect to https:\\myservername\remote from a client
workstation, I am unable to connect to the page. However, if I use the same
url from the server itself, I am able to get to the login screen just fine.
What have I done incorrectly that is preventing my clients from connecting?
Thank you in advance for any suggestions\help.

DQ
.



Relevant Pages

  • Re: My Server is not anymore seen on network plese help ?
    ... here is the client ipconfig. ... wich as adress 192.168.1.102 which it is not reachable for some reason ... As you can see the DHCP ... Microsoft Windows Small Business Server 2003 Best Practices Analyzer ...
    (microsoft.public.windows.server.sbs)
  • Re: Application Hang
    ... Back to DHCP, what about the client ipconfig without the DG ip address? ... When the old server crashed, it required a new motherboard and CPU. ... You should see at least,006 DNS servers, 003 Router. ...
    (microsoft.public.windows.server.networking)
  • Re: Windows Server 2003 DHCP server - Does not release IP Addresses
    ... on the SWITCH or the ROUTER. ... the clients will not know which server to go for DHCP REQUEST. ... And, if that Switch had some issues, how will the other DHCP server ... This error is usually received when the client booting up via PXE is ...
    (microsoft.public.windows.server.general)
  • Re: DHCP handles Naks one one vlan differently
    ... If the problem is on the network with the DHCP server, ... Frame 156 ... Your (client) IP address: 0.0.0.0 ...
    (comp.dcom.sys.cisco)
  • Re: Sending hostname with DHCP
    ... default route and the default dns host. ... Below is my /etc/resolv.conf created by the dhcp client. ... > This seems to depend on the client as much as the server. ...
    (Fedora)