Re: Can't find Server in Network Neighborhood

From: Les Connor [SBS Community Member - SBS MVP] (les.connor_at_DEL.cfive.ca)
Date: 02/22/05 

Date: Mon, 21 Feb 2005 20:45:03 -0600

binding order ? (for get my other post, I see you haven't got a router -
which is a shame). 

-- 
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
"Brendan" <Brendan@discussions.microsoft.com> wrote in message 
news:B8DF7FCF-E714-4C3B-87A9-2CEEB3C30CAF@microsoft.com...
>I confirmed that the WINs IP is 192.168.16.2... and filled in that
> information on the local NIC and then ran the CEICW.
>
> My problem still persists... interestingly... I checked the log file for 
> the
> CEICM (icwdetails.htm) and it seems to have the wrong IP addresses???
> However, DHCP dishes out the correct WINS server and IP Info to clients as
> confirmed in looking at the client IP info I included in previous 
> message -
> What does this info in the log mean? - Is the log file just not being 
> updated
> - or could this provide another clue to my problem.  The internal NIC is 
> set
> to 192.168.16.2 but the log shows it as being set to 192.168.254.226????? 
> I
> am lost... but have been for a while now.
>
> Any direction you can provide would be greatly appreciated...
>
> I have pasted the info from the icwdetails.htm file here in case that 
> helps:
>
> Router connection information:
> Local IP address of the router: 192.168.254.254
> Preferred DNS server: 66.250.49.2
> Alternate DNS server: 66.250.49.3
>
> Connection information for the network adapter used to
> connect to your local network:
>
> Local network connection name: Server Local Area
> Connection
>
> Local network connection IP address:
> 192.168.254.226
>
> Local network connection subnet mask: 255.255.255.0
>
> The Default Gateway for the network adapter used to
> access the local network is cleared so that network traffic
> is routed correctly.
>
> Routing and Remote Access will be configured as follows:
>
> Enable the service as a router for the local area
> network to route network traffic to the Internet.
> Enable IP routing to route network traffic to the
> Internet.
> Enable broadcast name resolution.
> Enable Basic Firewall on the demand-dial interface.
> Disable the option to automatically assign IP
> addresses by using the DHCP allocator because DHCP is
> provided by your server's DHCP server.
> Disable the option to resolve IP address for clients
> using DNS because DHCP is provided by your server's DHCP
> server.
>
> Disable File and Print Sharing for Microsoft Networks for
> the network adapter or modem used to connect to your ISP.
> This reduces the chance of a malicious attack by limiting
> the ability to browse the network and to connect to file
> shares and network printers.
>
> Unbind remote procedure call (RPC) from the network adapter
> or modem used to connect to your ISP. This reduces the
> chance of a malicious attack by limiting the ability to
> connect to this service.
>
> Bind the DHCP Server service to the IP address of the local
> network adapter so that your server's DHCP server does not
> provide DHCP addresses to computers on the Internet.
> Configure the DHCP scope to assign IP addresses to client
> computers using the following scope options:
>
> Set the router option (003) to 192.168.254.226 to
> define the default gateway used by client computers.
>
> Set the DNS server option (006) to 192.168.254.226
> to provide client computers with name resolution services
> for the local network.
>
> Set the DNS domain name option (015) to
> scidomain.local.
>
> Set the Windows Internet Name Service (WINS) server
> option (044) to 192.168.254.226.
>
> Set the WINS node type option (046) to h-node.
> Set forwarders to 66.250.49.2 and 66.250.49.3 so that name
> resolution requests intended for the Internet are forwarded
> to the DNS servers at your ISP.
>
> Set the DNS Server service to listen to the IP address of
> the local network adapter to ensure that the DNS server is
> not responding to DNS request from the Internet.
>
> Enable dynamic and secured updates to allow client computers
> to update DNS, but not allow DHCP to update DNS. This allows
> client computers to update the DNS table when they are
> turned on.
>
> Modify the binding order so that the local network adapter
> has the highest priority to route network traffic to the
> Internet.
>
> Set Internet Explorer to never dial a connection, to not use
> proxy settings, and set the home page to the address of the
> computer running Windows Small Business Server.
>
>
>
> "Marina Roos [SBS-MVP]" wrote:
>
>
>> Hi Brendan,
>>
>> WINS should be installed default and thus running. You go to the internal
>> nic properties, TCP/IP, Advanced, tab WINS, fill in the server IP. 
>> NetBIOS
>> over TCP/IP should be enabled.
>> Then go to the external nic properties and make sure that NetBIOS over
>> TCP/IP is disabled (external doesn't need WINS).
>>
>> Rerun CEICW.
>>
>> -- 
>> Regards,
>>
>> Marina
>> Microsoft SBS-MVP
>> One of the Magical M&M's
>>
>> "Brendan" <Brendan@discussions.microsoft.com> schreef in bericht
>> news:6C93CACA-34DF-4DD9-AD95-E488053EDDBE@microsoft.com...
>> > Thanks for your patience and willingness to help me out.  Here is the
>> > complete IP info from the server and a client - I have to install WINS 
>> > on
>> the
>> > internal NIC - is there a wizard to do so? :
>> >
>> > SERVER INFO:
>> >
>> > Windows IP Configuration
>> >    Host Name . . . . . . . . . . . . : SCIDNS
>> >    Primary Dns Suffix  . . . . . . . : scidomain.local
>> >    Node Type . . . . . . . . . . . . : Unknown
>> >    IP Routing Enabled. . . . . . . . : Yes
>> >    WINS Proxy Enabled. . . . . . . . : Yes
>> >    DNS Suffix Search List. . . . . . : scidomain.local
>> >
>> > Ethernet adapter Local Area Connection:
>> >    Connection-specific DNS Suffix  . :
>> >    Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
>> Connection
>> >    Physical Address. . . . . . . . . : 00-0F-1F-F9-B7-C6
>> >    DHCP Enabled. . . . . . . . . . . : No
>> >    IP Address. . . . . . . . . . . . : 192.168.16.2
>> >    Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> >    Default Gateway . . . . . . . . . :
>> >
>> >    DNS Servers . . . . . . . . . . . : 192.168.16.2
>> >
>> > Ethernet adapter Internet NIC - To ISP:
>> >    Connection-specific DNS Suffix  . :
>> >    Description . . . . . . . . . . . : Netgear Gigabit UTP Adapter
>> >    Physical Address. . . . . . . . . : 00-09-5B-8D-54-7C
>> >    DHCP Enabled. . . . . . . . . . . : No
>> >    IP Address. . . . . . . . . . . . : 192.168.254.225
>> >    Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> >    Default Gateway . . . . . . . . . : 192.168.254.254
>> >    DNS Servers . . . . . . . . . . . : 192.168.16.2
>> >
>> >
>> >
>> > CLIENT INFO:
>> >
>> > Windows IP Configuration
>> >         Host Name . . . . . . . . . . . . : POWERSPEC
>> >         Primary Dns Suffix  . . . . . . . : scidomain.local
>> >         Node Type . . . . . . . . . . . . : Hybrid
>> >         IP Routing Enabled. . . . . . . . : No
>> >         WINS Proxy Enabled. . . . . . . . : No
>> >         DNS Suffix Search List. . . . . . : scidomain.local
>> >
>> > Ethernet adapter Local Area Connection:
>> >         Connection-specific DNS Suffix  . : scidomain.local
>> >         Description . . . . . . . . . . . : VIA Compatable Fast 
>> > Ethernet
>> > Adapter
>> >         Physical Address. . . . . . . . . : 00-E0-4C-C9-DD-6F
>> >         Dhcp Enabled. . . . . . . . . . . : Yes
>> >         Autoconfiguration Enabled . . . . : Yes
>> >
>> >         IP Address. . . . . . . . . . . . : 192.168.16.13
>> >         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. . . . . . . . . . : Sunday, February 20, 2005
>> > 5:44:47 PM
>> >         Lease Expires . . . . . . . . . . : Monday, February 28, 2005
>> > 5:44:47 PM
>> >
>> >
>> > "Marina Roos [SBS-MVP]" wrote:
>> >
>> > > Hi Brendan,
>> > >
>> > > Please post the complete output of ipconfig/all here, as we are 
>> > > missing
>> some
>> > > details. You will need to set WINS on the internal nic.
>> > >
>> > > -- 
>> > > Regards,
>> > >
>> > > Marina
>> > > Microsoft SBS-MVP
>> > > One of the Magical M&M's
>> > >
>> > > "Brendan" <Brendan@discussions.microsoft.com> schreef in bericht
>> > > news:5D3A16EF-CB43-4777-846D-CF0D6D68E184@microsoft.com...
>> > > > Server IP Info:
>> > > >
>> > > > Internal NIC
>> > > >
>> > > > IP Address:  192.168.16.2
>> > > > Subnet:  255.255.255.0
>> > > > Default Gateway: Blank
>> > > >
>> > > > DNS: 192.168.16.2
>> > > >
>> > > >
>> > > > External NIC
>> > > >
>> > > > IP Address:  192.168.254.225
>> > > > Subnet:  255.255.255.0
>> > > > Default Gateway: 192.168.254.254
>> > > >
>> > > > DNS: 192.168.16.2
>> > > >
>> > > >
>> > > > Any help that you can offer would be greatly appreciated - I am
>> getting
>> > > > desperate here!
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > "Marina Roos [SBS-MVP]" wrote:
>> > > >
>> > > > > Hi Brendan,
>> > > > >
>> > > > > Please post the ipconfig/all from the server and one from a 
>> > > > > client.
>> > > > >
>> > > > > -- 
>> > > > > Regards,
>> > > > >
>> > > > > Marina
>> > > > > Microsoft SBS-MVP
>> > > > > One of the Magical M&M's
>> > > > >
>> > > > > "Brendan" <Brendan@discussions.microsoft.com> schreef in bericht
>> > > > > news:E28845DC-52FF-4218-8972-A01C0CB01583@microsoft.com...
>> > > > > > Did you ever resolve your issue?  I have the same situation 
>> > > > > > where
>> I
>> > > cannot
>> > > > > > find the DNS server (windows Small Biz 2003) under My Network
>> Places
>> > > on
>> > > > > the
>> > > > > > clients.  Also, in the My Network Places on the server I am 
>> > > > > > unable
>> to
>> > > > > expand
>> > > > > > the domain name and view any clients.
>> > > > > >
>> > > > > > Can you offer any advice?
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > "Ken Gardner" wrote:
>> > > > > >
>> > > > > > > I am unable to see my server in our domain via network
>> neighborhood.
>> > > > > When I
>> > > > > > > do a search computer by name, its resolved and I can click on 
>> > > > > > > it
>> and
>> > > get
>> > > > > to
>> > > > > > > the shares.  This has not happened before and I'm wondering 
>> > > > > > > why
>> it
>> > > is
>> > > > > now and
>> > > > > > > what I need to change to allow the server to be seen via 
>> > > > > > > Network
>> > > > > Neighborhood.
>> > > > > > > Any help would be greatly appreciated.
>> > > > > > >
>> > > > > > > BTW - I'm running an SBS 2003 Premium Ed. server.
>> > > > > > >
>> > > > > > > Thanks.
>> > > > >
>> > > > >
>> > > > >
>> > >
>> > >
>> > >
>>
>>
>>

Relevant Pages

  • Re: computer browser service wont start
    ... I've noticed that dnsApi is sometimes one of the things that starts early before everything it needs is actually working, e.g. the TCP/IP and network stack. ... In the situations I've seen the Event Log entry from dnsApi that you report, the computer did successfully register itself later. ... This assumes that the targetted DNS server can accept Dynamic registrations and the computer doing the dynamic registration is permitted to do so. ...
    (microsoft.public.windows.server.general)
  • Re: Cant find Server in Network Neighborhood
    ... I think you might be selecting the wrong connection type in CEICW. ... DHCP dishes out the correct WINS server and IP Info to clients as ... > Connection information for the network adapter used to ... > Local network connection name: ...
    (microsoft.public.windows.server.sbs)
  • Re: oops again
    ... open on the Firewall, and the default should be none. ... Since you intend to install IIS purely as a test server for your ASPX pages ... Make sure that IIS is only listening on the local network (192.168.x.y ...
    (microsoft.public.inetserver.iis)
  • Re: Cant find Server in Network Neighborhood
    ... > Preferred DNS server: 66.250.49.2 ... This isn't your lan connection, ... > Connection information for the network adapter used to> connect to your local network: ...
    (microsoft.public.windows.server.sbs)
  • Re: The PC name ends up with DNS name appended.
    ... but the router gets configured by the ISP to be the DNS server ... If the resulting DNS name does not resolve, ... Wins Proxy in the network card properties. ...
    (microsoft.public.windowsxp.network_web)