Re: Client Connection problems
From: Brian (anonymous_at_discussions.microsoft.com)
Date: 09/18/04
- Next message: Les Connor: "Re: Error with ICW"
- Previous message: Jair Bobys: "Re: Yet another SBS2K3 Backup problem"
- Maybe in reply to: Brian: "Client Connection problems"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 18 Sep 2004 16:59:13 -0700
Hi Wes,
There was a third-party firewall enabled on the client
computers, that was setup by a previous network
administrator; that I didn't even notice was there. Once I
put the ip-range of the intranet in the allowed zones, I
was able to connect to the server. How could I have missed
that..oh well, feel a little stupid, but thank you for the
help, I didn't even think to check if a 3rd party program
was running on the client pc. And thanks to Marina for all
the help with getting the internet sharing to work.
Thanks again,
Brian
>-----Original Message-----
>Hi Brian,
>
>The user account you are using does have access to the
server shares, right?
>Just checking.
>
>Have you got either a third-party firewall or the XP
firewall enabled on the
>client? If so, disable it and try again. Don't forget
that XP Service Pack
>2 enables the firewall by default.
>
>>From a command prompt, use the "net use" command to map
one of your shares.
>E.g. NET USE X: \\192.168.0.2
\sharename /user:domainname\username and type
>your password when prompted.
>
>Please let us know how you get on.
>
>Kind regards,
>
>Wes
>
>"Brian" <anonymous@discussions.microsoft.com> wrote in
message
>news:219601c49dc5$acd25480$a301280a@phx.gbl...
>>I can however access remote desktop from my xp home
>> machines, and I can access the companies internal
website
>> on SBS at the appropriate IP address; but if I try and
>> actually access the network shares from the mapping
>> wizard, or the run window, it tells me network path not
>> found. I did try adding the computer name to active
>> directory, but that didnt make any difference, since it
>> cant join the domain anyways.
>> Thanks again
>>>-----Original Message-----
>>>Hi Wes,
>>>
>>>My xp-pro machines can now join the domain, so now the
>>>only problem I'm having is with the XP-home. The problem
>>>Im still having is that when I enter
>>>\\ip address
>>>It tells me that this address isnt found
>>>The home clients have internet access, everything is
>>>properly checked off in the DNS settings, ipconfig shows
>>>that it is recieving the proper addresses. Thanks for
the
>>>help
>>>
>>>Brian
>>>>-----Original Message-----
>>>>Hi Brian,
>>>>
>>>>XP Home is always going to give you so much hassle that
>>>it is always better
>>>>to upgrade than to workaround the problem. Microsoft
>>>specifically designed
>>>>XP Home so that it would not connect to a domain,
>>>otherwise, we would all be
>>>>saving the extra cash and use Home instead of Pro. If
>>>you work out the
>>>>total cost of the man hours you have spent on the
>> problem
>>>so far, together
>>>>with all the extra administration that you will face in
>>>the future and
>>>>compare that to the cost of upgrading, I think that you
>>>will find that it
>>>>makes sense to upgrade as soon as possible.
>>>>
>>>>In the mean time, you should be able to get partial use
>>>out of your XP Home
>>>>boxes by carrying out the following on each one:
>>>>
>>>>Ensure that your clients get their IP and DNS
>> information
>>>via your SBS DHCP
>>>>Service.
>>>>
>>>>Add a DNS Suffix to each of your clients that match
your
>>>domain DNS suffix
>>>>and place ticks in both "Register this connection's
>>>addresses in DNS" and
>>>>"Use this connection's DNS suffix in DNS Registration"
>>>boxes.
>>>>
>>>>Change the local administrators password to match your
>>>domain administrators
>>>>password. (This helps you to connect to the XP Home
from
>>>the server or
>>>>another PC. But, you will never be able to use the
mange
>>>options from within
>>>>the SBS console.)
>>>>
>>>>Disable the Welcome screen and Fast switching on your
>>>clients to ensure that
>>>>your local user is using the same Username and Password
>>>as the corresponding
>>>>Domain Account.
>>>>
>>>>Go to Network Properties|Advanced|Network
Identification
>>>and change the
>>>>workgroup name to match your SBS NETBIOS name.
>>>>
>>>>Also ensure that NETBIOS over TCP/IP is enabled on your
>>>clients and SBS
>>>>Internal NIC.
>>>>
>>>>Now, first check that you can access your server shares
>>>by IP address by
>>>>clicking START|RUN and typing \\ipaddress and click OK
>> or
>>>press ENTER.
>>>>
>>>>You may be asked for a username and password and should
>>>be given the option
>>>>to "Save Password". Each user may have to do this each
>>>time the computer is
>>>>rebooted or the connection to the server is lost. But
>> you
>>>should still be
>>>>able to get a list of shares to open or map.
>>>>
>>>>If you cannot connect to the server then check your
>>>Client/Server IP
>>>>addresses. At this stage, you are not using WINS or
DNS.
>>>>
>>>>Next, do the same but substitute \\ipaddress for
>>>\\servername and \\FQDN and
>>>>troubleshoot WINS or DNS respectively if either fails.
>>>>
>>>>You may also find that your XP Home clients will not be
>>>able to view a list
>>>>of servers or computers using My Network Places. This
>> is
>>>due to WINS or
>>>>Computer Browser issues and really isn't that important
>>>if you can use
>>>>\\ipaddress instead. You may want to think about
>> placing
>>>some links on the
>>>>desktops to make it easier for each user.
>>>>
>>>>By the way, you need to make sure that your users do
not
>>>change their
>>>>passwords unless you do the same on the server.
>>>>
>>>>Alternatively, bite the bullet and buy XP Pro and let
>> the
>>>little wizard do
>>>>the job for you.
>>>>
>>>>Kind regards,
>>>>
>>>>Wes
>>>>
>>>>"Brian" <anonymous@discussions.microsoft.com> wrote in
>>>message
>>>>news:35ee01c49d17$71f97900$a601280a@phx.gbl...
>>>>> Hello,
>>>>>
>>>>> Yes, I'm aware Home can't actually join the domain,
at
>>>>> some point the business owner is going to updgrate to
>>>>> pro, but for now access to shares will be sufficient.
>>>But
>>>>> to this point I have not created the computeraccounts
>> in
>>>>> active directory, because they can't join the domain,
>>>but
>>>>> I will go ahead and try it to see if that corrects
the
>>>>> problem.
>>>>> Thanks again
>>>>>>-----Original Message-----
>>>>>>Hi Brian,
>>>>>>
>>>>>>You do know that XP Home can't join a domain, right?
>>>>>>
>>>>>>Have you created the computeraccounts on the SBS?
Looks
>>>>> to me a bit of a
>>>>>>weird name that this XP is having.
>>>>>>
>>>>>>--
>>>>>>Regards,
>>>>>>
>>>>>>Marina
>>>>>>Microsoft SBS-MVP
>>>>>>
>>>>>>"Brian" <anonymous@discussions.microsoft.com> schreef
>> in
>>>>> bericht
>>>>>>news:1c2701c49d07$cfc51c70$a301280a@phx.gbl...
>>>>>>> This is an ipconfig from an xp Home client, since
>> most
>>>>> of
>>>>>>> the clients are xp home, but my xp pro clients have
>>>the
>>>>>>> same problem.
>>>>>>> Windows IP Configuration
>>>>>>>
>>>>>>> Host Name . . . . . . . . . . . . :
>>>adfsphxdt01
>>>>>>> Primary Dns Suffix . . . . . . . :
>>>>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>>>>> IP Routing Enabled. . . . . . . . : No
>>>>>>> WINS Proxy Enabled. . . . . . . . : No
>>>>>>>
>>>>>>> Ethernet adapter Local Area Connection:
>>>>>>>
>>>>>>> Connection-specific DNS Suffix . :
ACLD.loc
>>>>>>> Description . . . . . . . . . . . : Intel
(R)
>>>>>>> PRO/100 VE Network Connecti
>>>>>>> on
>>>>>>> Physical Address. . . . . . . . . : 00-03-
47-
>>>>> FC-
>>>>>>> 96-DA
>>>>>>> Dhcp Enabled. . . . . . . . . . . : Yes
>>>>>>> Autoconfiguration Enabled . . . . : Yes
>>>>>>> IP Address. . . . . . . . . . . . :
>>>>> 192.168.0.11
>>>>>>> Subnet Mask . . . . . . . . . . . :
>>>>> 255.255.255.0
>>>>>>> Default Gateway . . . . . . . . . :
>>>192.168.0.2
>>>>>>> DHCP Server . . . . . . . . . . . :
>>>192.168.0.2
>>>>>>> DNS Servers . . . . . . . . . . . :
>>>192.168.0.2
>>>>>>> Primary WINS Server . . . . . . . :
>>>192.168.0.2
>>>>>>> Lease Obtained. . . . . . . . . . : Friday,
>>>>>>> September 17, 2004 8:19:23 A
>>>>>>> M
>>>>>>> Lease Expires . . . . . . . . . . :
Saturday,
>>>>>>> September 25, 2004 8:19:23
>>>>>>> AM
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Brian
>>>>>>>
>>>>>>> >-----Original Message-----
>>>>>>> >Hi Brian,
>>>>>>> >
>>>>>>> >Ipconfig from the server looks good. Can you post
>> one
>>>>>>> from a client?
>>>>>>> >
>>>>>>> >--
>>>>>>> >Regards,
>>>>>>> >
>>>>>>> >Marina
>>>>>>> >Microsoft SBS-MVP
>>>>>>> >
>>>>>>> >"Brian" <anonymous@discussions.microsoft.com>
>> schreef
>>>>> in
>>>>>>> bericht
>>>>>>> >news:28d801c49c44$6a068d60$a601280a@phx.gbl...
>>>>>>> >> Using your suggestions my clients are now able
to
>>>>>>> access
>>>>>>> >> the internet through the SBS server; however, I
>>>>> still
>>>>>>> cant
>>>>>>> >> actually see the domain controler (sbs server)
>> from
>>>>> my
>>>>>>> >> clients, to join the domain. I will post my new
>>>>>>> >> ipconfig /all, and nslookup for my server.
>>>>>>> >>
>>>>>>> >> Thanks again for all your help
>>>>>>> >> Microsoft Windows [Version 5.2.3790]
>>>>>>> >> (C) Copyright 1985-2003 Microsoft Corp.
>>>>>>> >>
>>>>>>> >> C:\Documents and Settings\Administrator>nslookup
>>>>>>> >> server01.acld.loc
>>>>>>> >> Server: server01.acld.loc
>>>>>>> >> Address: 192.168.0.2
>>>>>>> >>
>>>>>>> >> Name: server01.acld.loc
>>>>>>> >> Address: 192.168.0.2
>>>>>>> >>
>>>>>>> >>
>>>>>>> >> C:\Documents and
>>>>> Settings\Administrator>ipconfig /all
>>>>>>> >>
>>>>>>> >> Windows IP Configuration
>>>>>>> >>
>>>>>>> >> Host Name . . . . . . . . . . . . : server01
>>>>>>> >> Primary Dns Suffix . . . . . . . : ACLD.loc
>>>>>>> >> Node Type . . . . . . . . . . . . : Hybrid
>>>>>>> >> IP Routing Enabled. . . . . . . . : Yes
>>>>>>> >> WINS Proxy Enabled. . . . . . . . : No
>>>>>>> >> DNS Suffix Search List. . . . . . : ACLD.loc
>>>>>>> >>
>>>>>>> >> Ethernet adapter Intranet:
>>>>>>> >>
>>>>>>> >> Connection-specific DNS Suffix . :
>>>>>>> >> Description . . . . . . . . . . . : Intel(R)
>>>>>>> PRO/100 M
>>>>>>> >> Network Connection
>>>>>>> >> Physical Address. . . . . . . . . : 00-02-B3-
>> E9-
>>>>> 9B-
>>>>>>> 2B
>>>>>>> >> DHCP Enabled. . . . . . . . . . . : No
>>>>>>> >> IP Address. . . . . . . . . . . . :
192.168.0.2
>>>>>>> >> Subnet Mask . . . . . . . . . . . :
>>>255.255.255.0
>>>>>>> >> Default Gateway . . . . . . . . . :
>>>>>>> >> DNS Servers . . . . . . . . . . . :
192.168.0.2
>>>>>>> >> Primary WINS Server . . . . . . . :
192.168.0.2
>>>>>>> >>
>>>>>>> >> Ethernet adapter DSL:
>>>>>>> >>
>>>>>>> >> Connection-specific DNS Suffix . :
>>>>>>> >> Description . . . . . . . . . . . : Intel(R)
>>>>>>> PRO/1000
>>>>>>> >> CT Network Connection
>>>>>>> >> Physical Address. . . . . . . . . : 00-02-B3-
>> E9-
>>>>> 9B-
>>>>>>> 2A
>>>>>>> >> DHCP Enabled. . . . . . . . . . . : No
>>>>>>> >> IP Address. . . . . . . . . . . . :
192.168.1.2
>>>>>>> >> Subnet Mask . . . . . . . . . . . :
>>>>> 255.255.255.192
>>>>>>> >> Default Gateway . . . . . . . . . :
192.168.1.1
>>>>>>> >> DNS Servers . . . . . . . . . . . :
192.168.0.2
>>>>>>> >> NetBIOS over Tcpip. . . . . . . . : Disabled
>>>>>>> >>
>>>>>>> >> C:\Documents and Settings\Administrator>
>>>>>>> >> >-----Original Message-----
>>>>>>> >> >Hi Brian,
>>>>>>> >> >
>>>>>>> >> >What is this domain.actdsltmp dns suffix doing
in
>>>>> your
>>>>>>> >> ipconfig? You should
>>>>>>> >> >get rid of it.
>>>>>>> >> >
>>>>>>> >> >You intranet nic looks good, but it is missing
>> the
>>>>>>> WINS.
>>>>>>> >> That should be
>>>>>>> >> >pointing to your server IP 192.168.0.2 too.
Make
>>>>> sure
>>>>>>> >> that Netbios over
>>>>>>> >> >TCP/IP is enabled on the internal nic.
>>>>>>> >> >
>>>>>>> >> >Your external nic should not have that
>>>>>>> domain.actdsltmp
>>>>>>> >> dns suffix. Get rid
>>>>>>> >> >of it.
>>>>>>> >> >DNS should only point to your server-IP
>>>>> 192.168.0.2.
>>>>>>> >> >You should make the external nic static, not
DHCP
>>>>>>> >> dynamic. The gateway
>>>>>>> >> >should point to your router IP, in your case
the
>>>>>>> router
>>>>>>> >> has IP 192.168.1.1.
>>>>>>> >> >
>>>>>>> >> >Now make those changes, rerun CEICW and try
>> again.
>>>>>>> >> >
>>>>>>> >> >--
>>>>>>> >> >Regards,
>>>>>>> >> >
>>>>>>> >> >Marina
>>>>>>> >> >Microsoft SBS-MVP
>>>>>>> >> >
>>>>>>> >> >"Brian" <anonymous@discussions.microsoft.com>
>>>>> schreef
>>>>>>> in
>>>>>>> >> bericht
>>>>>>> >> >news:0fc001c49b87$fe48a340$a401280a@phx.gbl...
>>>>>>> >> >> The DSL Modem is a modem/gate/router; I have
>>>>> turned
>>>>>>> off
>>>>>>> >> >> DHCP and attempted to configure a static ip
on
>>>>> the
>>>>>>> DSL
>>>>>>> >> >> NIC; however, although the modem shows the
SBS
>>>>>>> server is
>>>>>>> >> >> accessing the internet, I can't actually go
>>>>> online.
>>>>>>> I
>>>>>>> >> have
>>>>>>> >> >> configured the modem/router in a different
>>>subnet
>>>>>>> than
>>>>>>> >> my
>>>>>>> >> >> local intranet, but am still having the same
>>>>>>> problem.
>>>>>>> >> >> Although my clients recieve an initial ip
>>>>> address,
>>>>>>> and
>>>>>>> >> >> show the server's ip for DNS,WINS,Gateway,
>>>>>>> etc..they can
>>>>>>> >> >> never actually repair the connection and
renew
>>>>>>> their ip
>>>>>>> >> >> from the server.
>>>>>>> >> >> If I turn the DSL Modem's DHCP on, and keep
the
>>>>> DSl
>>>>>>> >> modem
>>>>>>> >> >> NIC in a seperate subnet I can recieve
Internet
>>>>>>> access
>>>>>>> >> on
>>>>>>> >> >> the server, my clients still recieve their
>>>>>>> DHCP,DNS,WINS
>>>>>>> >> >> server addresses from my Server and not the
>>>>> modem,
>>>>>>> but I
>>>>>>> >> >> still cant renew the IP or actually see the
>>>>> domain
>>>>>>> >> >> controller.
>>>>>>> >> >> I have tried disabling the DSL NIC, for
>>>>>>> troubleshooting
>>>>>>> >> >> purposes, and the same problem remains. Here
>> is
>>>a
>>>>>>> look
>>>>>>> >> at
>>>>>>> >> >> my ipconfig /all from the server, as per
>>>Marina's
>>>>>>> >> request
>>>>>>> >> >>
>>>>>>> >> >> C:\Documents and
>>>>>>> Settings\Administrator>ipconfig /all
>>>>>>> >> >>
>>>>>>> >> >> Windows IP Configuration
>>>>>>> >> >>
>>>>>>> >> >> Host Name . . . . . . . . . . . . :
server01
>>>>>>> >> >> Primary Dns Suffix . . . . . . . :
ACLD.loc
>>>>>>> >> >> Node Type . . . . . . . . . . . . : Hybrid
>>>>>>> >> >> IP Routing Enabled. . . . . . . . : Yes
>>>>>>> >> >> WINS Proxy Enabled. . . . . . . . : No
>>>>>>> >> >> DNS Suffix Search List. . . . . . :
ACLD.loc
>>>>>>> >> >>
>>>>>>> domain.actdsltmp
>>>>>>> >> >>
>>>>>>> >> >> Ethernet adapter Intranet:
>>>>>>> >> >>
>>>>>>> >> >> Connection-specific DNS Suffix . :
>>>>>>> >> >> Description . . . . . . . . . . . : Intel
(R)
>>>>>>> PRO/100
>>>>>>> >> M
>>>>>>> >> >> Network Connection
>>>>>>> >> >> Physical Address. . . . . . . . . : 00-02-
>> B3-
>>>>> E9-
>>>>>>> 9B-2B
>>>>>>> >> >> DHCP Enabled. . . . . . . . . . . : No
>>>>>>> >> >> IP Address. . . . . . . . . . . . :
>>>>> 192.168.0.2
>>>>>>> >> >> Subnet Mask . . . . . . . . . . . :
>>>>> 255.255.255.0
>>>>>>> >> >> Default Gateway . . . . . . . . . :
>>>>>>> >> >> DNS Servers . . . . . . . . . . . :
>>>>> 192.168.0.2
>>>>>>> >> >>
>>>>>>> >> >> Ethernet adapter DSL:
>>>>>>> >> >>
>>>>>>> >> >> Connection-specific DNS Suffix . :
>>>>>>> domain.actdsltmp
>>>>>>> >> >> Description . . . . . . . . . . . : Intel
(R)
>>>>>>> PRO/1000
>>>>>>> >> >> CT Network Connection
>>>>>>> >> >> Physical Address. . . . . . . . . : 00-02-
>> B3-
>>>>> E9-
>>>>>>> 9B-2A
>>>>>>> >> >> DHCP Enabled. . . . . . . . . . . : Yes
>>>>>>> >> >> Autoconfiguration Enabled . . . . : Yes
>>>>>>> >> >> IP Address. . . . . . . . . . . . :
>>>>> 192.168.1.2
>>>>>>> >> >> Subnet Mask . . . . . . . . . . . :
>>>>>>> 255.255.255.192
>>>>>>> >> >> Default Gateway . . . . . . . . . :
>>>>> 192.168.1.1
>>>>>>> >> >> DHCP Server . . . . . . . . . . . :
>>>>> 192.168.1.1
>>>>>>> >> >> DNS Servers . . . . . . . . . . . :
>>>>> 192.168.1.1
>>>>>>> >> >>
>>>>> 205.171.3.65
>>>>>>> >> >> NetBIOS over Tcpip. . . . . . . . :
Disabled
>>>>>>> >> >> Lease Obtained. . . . . . . . . . :
>>>Wednesday,
>>>>>>> >> >> September 15, 2004 5:43:44 PM
>>>>>>> >> >> Lease Expires . . . . . . . . . . :
>> Thursday,
>>>>>>> >> September
>>>>>>> >> >> 16, 2004 5:43:44 PM
>>>>>>> >> >>
>>>>>>> >> >>
>>>>>>> >> >> At the time of this i have the DSL Nic set to
>>>>>>> recieve a
>>>>>>> >> >> DHCP address from the DSL Modem/Router.
>>>>>>> >> >>
>>>>>>> >> >> Thanks again
>>>>>>> >> >>
>>>>>>> >> >> >-----Original Message-----
>>>>>>> >> >> >Brian
>>>>>>> >> >> >You need a router between your internet nic
>> and
>>>>>>> your
>>>>>>> >> DSL
>>>>>>> >> >> modem.
>>>>>>> >> >> >
>>>>>>> >> >> >This will allow you to assign a static to
that
>>>>> NIC
>>>>>>> and
>>>>>>> >> >> place it in a different subnet from your
>>>intranet
>>>>>>> nic
>>>>>>> >> and
>>>>>>> >> >> this is required that they be in different
>>>>> subnets
>>>>>>> >> >> >
>>>>>>> >> >> >Then as Marina said, SBS should do all the
>>>>>>> supplying of
>>>>>>> >> >> IP Addresses, DNS etc for your lan clients,
not
>>>>>>> your DSL
>>>>>>> >> >> modem
>>>>>>> >> >> >
>>>>>>> >> >> >--
>>>>>>> >> >> >Cris Hanna (SBS-MVP)
>>>>>>> >> >> >_____________________
>>>>>>> >> >> >Please only respond in the Newsgroup and not
>>>>>>> directly
>>>>>>> >> to
>>>>>>> >> >> me, so that everyone can share the
information
>>>>>>> >> >> > "Brian"
>> <anonymous@discussions.microsoft.com>
>>>>>>> wrote
>>>>>>> >> in
>>>>>>> >> >> message news:250f01c49ac1$08afc880
>>>>>>> $a301280a@phx.gbl...
>>>>>>> >> >> > My question is what are possible solutions
>> to
>>>>> the
>>>>>>> >> >> problem
>>>>>>> >> >> > of my clients not being able to find my
>>>server
>>>>>>> on the
>>>>>>> >> >> > network, and what possible things can I do
>> to
>>>>>>> get the
>>>>>>> >> >> NAT
>>>>>>> >> >> > routing service to properly share my
>> internet
>>>>>>> >> >> connection
>>>>>>> >> >> > with my clients.
>>>>>>> >> >> > I did attempt to connect an XP-Pro laptop
to
>>>>> the
>>>>>>> >> >> network;
>>>>>>> >> >> > when trying to join the domain I recieve
an
>>>>>>> >> >> error "Domain
>>>>>>> >> >> > controller not found"; basically my
problem
>>>>> is my
>>>>>>> >> >> clients
>>>>>>> >> >> > cant locate my server.
>>>>>>> >> >> > Currently the DSL modem provides an ip
>>>>> address of
>>>>>>> >> >> > 192.168.0.x to my internet NIC; my
intranet
>>>>> NIC
>>>>>>> is
>>>>>>> >> >> > configured at 192.168.0.2, could this be
>>>>> causing
>>>>>>> the
>>>>>>> >> >> > conflict because of the overlap?
>>>>>>> >> >> > Thanks
>>>>>>> >> >> > >-----Original Message-----
>>>>>>> >> >> > >Not sure what your question is...
>>>>>>> >> >> > >This is never going to work the way it is
>>>>>>> supposed
>>>>>>> >> to
>>>>>>> >> >> if
>>>>>>> >> >> > you don't upgrade from XP Home to XP Pro
>>>>>>> >> >> > >
>>>>>>> >> >> > >--
>>>>>>> >> >> > >Cris Hanna (SBS-MVP)
>>>>>>> >> >> > >_____________________
>>>>>>> >> >> > >Please only respond in the Newsgroup and
>> not
>>>>>>> >> directly
>>>>>>> >> >> to
>>>>>>> >> >> > me, so that everyone can share the
>>>information
>>>>>>> >> >> > > "Brian"
>>>>> <anonymous@discussions.microsoft.com>
>>>>>>> >> wrote
>>>>>>> >> >> in
>>>>>>> >> >> > message news:0ca501c49a83$add8b3f0
>>>>>>> >> $a601280a@phx.gbl...
>>>>>>> >> >> > > I am running sbs in a windows xp home
>>>>>>> environment,
>>>>>>> >> >> so
>>>>>>> >> >> > none
>>>>>>> >> >> > > of my client computers can join the
>>>domain,
>>>>>>> so I
>>>>>>> >> >> have
>>>>>>> >> >> > > changed the name of the workgroup each
>>>>> client
>>>>>>> >> >> computer
>>>>>>> >> >> > is
>>>>>>> >> >> > > in to match the domain name. From the
>>>>> server
>>>>>>> I can
>>>>>>> >> >> > browse
>>>>>>> >> >> > > the network and see all of the client
>>>>>>> computers,
>>>>>>> >> the
>>>>>>> >> >> > > client computers have also accessed
>> leases
>>>>>>> from
>>>>>>> >> the
>>>>>>> >> >> > SBS
>>>>>>> >> >> > > DHCP server. SBS is configured as a
>> domain
>>>>>>> >> >> controller,
>>>>>>> >> >> > and
>>>>>>> >> >> > > the DNS server was automatically
>>>>> configured at
>>>>>>> >> >> > > installation, all fowarding appears to
>>>look
>>>>>>> >> >> > appropriate.
>>>>>>> >> >> > > However, my clients cannot actually see
>>>the
>>>>>>> server
>>>>>>> >> >> > when
>>>>>>> >> >> > > browsing the network, nor do they
recieve
>>>>> the
>>>>>>> >> shared
>>>>>>> >> >> > > internet access. The network
>>>infrastructure
>>>>>>> is DSL
>>>>>>> >> >> > Modem
>>>>>>> >> >> > > attached to SBS on one NIC, and sbs is
>>>>>>> attached to
>>>>>>> >> >> the
>>>>>>> >> >> > > network hub on another NIC, the
intranet
>>>>> NIC
>>>>>>> is at
>>>>>>> >> >> the
>>>>>>> >> >> > top
>>>>>>> >> >> > > of the browse list, and is configured
>> with
>>>>> ip
>>>>>>> >> >> address
>>>>>>> >> >> > and
>>>>>>> >> >> > > subnet, i Have left the default gateway
>>>>>>> settings
>>>>>>> >> >> > blank,
>>>>>>> >> >> > > and directed this NIC to look at itself
>>>for
>>>>>>> DNS.
>>>>>>> >> All
>>>>>>> >> >> > > clients are also recieving the SBS
server
>>>>> as
>>>>>>> their
>>>>>>> >> >> DNS
>>>>>>> >> >> > > server. SBS accesses the internet with
no
>>>>>>> >> problems.
>>>>>>> >> >> > > Clients also have difficulty renewing
the
>>>>> ip
>>>>>>> >> address
>>>>>>> >> >> > from
>>>>>>> >> >> > > the DHCP server. In addition although I
>>>can
>>>>>>> see
>>>>>>> >> >> > clients
>>>>>>> >> >> > > from the SBS, I cant actually access
>> them,
>>>>>>> >> although
>>>>>>> >> >> > the XP
>>>>>>> >> >> > > home clients can readily access one
>>>>> another. I
>>>>>>> >> have
>>>>>>> >> >> > also
>>>>>>> >> >> > > disabled the Domain Security Policy
>>>network
>>>>>>> server
>>>>>>> >> >> > > digitally sign communications {always}.
>>>>>>> >> >> > > Any suggestions would be appreciated
>>>>>>> >> >> > > Thanks,
>>>>>>> >> >> > > Brian
>>>>>>> >> >
>>>>>>> >> >
>>>>>>> >> >.
>>>>>>> >> >
>>>>>>> >
>>>>>>> >
>>>>>>> >.
>>>>>>> >
>>>>>>
>>>>>>
>>>>>>.
>>>>>>
>>>>
>>>>
>>>>.
>>>>
>>>.
>>>
>
>
>.
>
- Next message: Les Connor: "Re: Error with ICW"
- Previous message: Jair Bobys: "Re: Yet another SBS2K3 Backup problem"
- Maybe in reply to: Brian: "Client Connection problems"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
