Cant Browse network

SBS 2000,

After removing NetBEUI from our network no one can see any of the workgroups or expand the domain group within My Network Places. All computers can be found by IP and by Name.

Jim
Sun Nov 30 09:44:38 CST 2003

Do you have option 46 in your server's dhcp to 0x8? Also the
workstation should have their tcp advanced properties wins set to use
netbios of tcp. Thjey should get this infor from the dhcp server but.
Netbios is still very important for working with Server 2000 but
neteui is not installed on any of my SBS installs.


"RobGMiller" <robgmiller@petrolinks.com> wrote:

>SBS 2000,
>
>After removing NetBEUI from our network no one can see any of the workgroups or expand the domain group within My Network Places. All computers can be found by IP and by Name.

Jim B. SBS MVP
remove the mvp to send email

Marina
Sun Nov 30 09:41:44 CST 2003

How many nics in the server? Can you post the ipconfig/all?
Does the ipconfig/all from the clients show that everything is pointing to
your server-IP? Got File and printersharing loaded?

Marina

"RobGMiller" <robgmiller@petrolinks.com> schreef in bericht
news:88A4CB37-95E3-438B-92D3-072A75C305B0@microsoft.com...
> SBS 2000,
>
> After removing NetBEUI from our network no one can see any of the
workgroups or expand the domain group within My Network Places. All
computers can be found by IP and by Name.

anonymous
Sun Nov 30 13:36:08 CST 2003

Thanks for your reply.

There is only 1 NIC on the Server.
The File and Printer sharing is enabled on the server
NETBios Over TCP/IP is enabled on both the server and most if not all the stations/clients.
Option 46 of the DHCP server was not on but I have turned it on and rebooted the Server.
BINGO, that seems to have worked.
I will check all the stations.

Thanks for your suggestions.

anonymous
Sun Nov 30 16:01:08 CST 2003

I hate to say this but now the Clients are not working too well.

Setting the DHCP option 46 to 0x8 seems to have made browsing possible on the server. Just after I restarted the server one of the stations that was not browsing before began to browse ok. The next client could not and now the first one cannot either. Additionally, the drives mapped to shares on the server are not as responsive. I have to click on the drive listing two or three times to get to see the folders it contains.

The other options on the DHCP Server are as follows.

005 = 192.168.1.15
006 = 192.168.1.15
046 = 0x8

Here are the IPConfig output you requested previously.

The following is the IPCONFIG from the SBS server.

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : DELL
Primary DNS Suffix . . . . . . . : Rlink.PDC
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Rlink.PDC

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet Adapter (10/100)
Physical Address. . . . . . . . . : 00-06-5B-3D-11-39
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.15
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.15
Primary WINS Server . . . . . . . : 192.168.1.15

PPP adapter RAS Server (Dial In) Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.201
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 127.0.0.1

The following is the IPCONFIG from one of the Clients.

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : ROB2000
Primary DNS Suffix . . . . . . . : Rlink.PDC
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Rlink.PDC

Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139(A)-based PCI Fast Ethernet Adapter #3
Physical Address. . . . . . . . . : 00-50-BA-42-7B-75
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.113
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.15
DNS Servers . . . . . . . . . . . : 192.168.1.15
Primary WINS Server . . . . . . . : 192.168.1.15
Lease Obtained. . . . . . . . . . : Sunday, November 30, 2003 13:40:29
Lease Expires . . . . . . . . . . : Tuesday, December 02, 2003 13:40:29

Merv
Sun Nov 30 16:40:23 CST 2003

Reference Document...

How to Configure a SBS for Full Time Internet Access with a Single Network
Adapter
http://support.microsoft.com/?kbid=309633

Note: The 046 setting inthis document says 0x1. It should be 0x8.

The "preferred" configuration for SBS is the 2 NIC scenerio: (you can then
run ISA in Firewall mode as an added security feature)

Network setup procedures:
http://www.smallbizserver.net/sbs2000/network.aspx

Did you reboot the workstations after changing the DHCP parameters?

--
Merv Porter [SBS MVP]
===================================
"RobGMiller" <anonymous@discussions.microsoft.com> wrote in message
news:AAA2298D-F8DB-43F8-B27B-B5EBDEF0CAEB@microsoft.com...
> I hate to say this but now the Clients are not working too well.
>
> Setting the DHCP option 46 to 0x8 seems to have made browsing possible on
the server. Just after I restarted the server one of the stations that was
not browsing before began to browse ok. The next client could not and now
the first one cannot either. Additionally, the drives mapped to shares on
the server are not as responsive. I have to click on the drive listing two
or three times to get to see the folders it contains.
>
> The other options on the DHCP Server are as follows.
>
> 005 = 192.168.1.15
> 006 = 192.168.1.15
> 046 = 0x8
>
> Here are the IPConfig output you requested previously.
>
> The following is the IPCONFIG from the SBS server.
>
> Windows 2000 IP Configuration
>
> Host Name . . . . . . . . . . . . : DELL
> Primary DNS Suffix . . . . . . . : Rlink.PDC
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : Yes
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : Rlink.PDC
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet Adapter
(10/100)
> Physical Address. . . . . . . . . : 00-06-5B-3D-11-39
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.15
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.15
> Primary WINS Server . . . . . . . : 192.168.1.15
>
> PPP adapter RAS Server (Dial In) Interface:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
> Physical Address. . . . . . . . . : 00-53-45-00-00-00
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.201
> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . : 127.0.0.1
>
> The following is the IPCONFIG from one of the Clients.
>
> Windows 2000 IP Configuration
>
> Host Name . . . . . . . . . . . . : ROB2000
> Primary DNS Suffix . . . . . . . : Rlink.PDC
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : Rlink.PDC
>
> Ethernet adapter Local Area Connection 3:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Realtek RTL8139(A)-based PCI Fast
Ethernet Adapter #3
> Physical Address. . . . . . . . . : 00-50-BA-42-7B-75
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.1.113
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . . . . : 192.168.1.15
> DNS Servers . . . . . . . . . . . : 192.168.1.15
> Primary WINS Server . . . . . . . : 192.168.1.15
> Lease Obtained. . . . . . . . . . : Sunday, November 30, 2003 13:40:29
> Lease Expires . . . . . . . . . . : Tuesday, December 02, 2003 13:40:29
>
>
>

Marina
Sun Nov 30 18:23:11 CST 2003

005? Typo? You meant 003 I hope?
Also options 015 and 044 should be there.

Marina

"RobGMiller" <anonymous@discussions.microsoft.com> schreef in bericht
news:AAA2298D-F8DB-43F8-B27B-B5EBDEF0CAEB@microsoft.com...
> I hate to say this but now the Clients are not working too well.
>
> Setting the DHCP option 46 to 0x8 seems to have made browsing possible on
the server. Just after I restarted the server one of the stations that was
not browsing before began to browse ok. The next client could not and now
the first one cannot either. Additionally, the drives mapped to shares on
the server are not as responsive. I have to click on the drive listing two
or three times to get to see the folders it contains.
>
> The other options on the DHCP Server are as follows.
>
> 005 = 192.168.1.15
> 006 = 192.168.1.15
> 046 = 0x8
>
> Here are the IPConfig output you requested previously.
>
> The following is the IPCONFIG from the SBS server.
>
> Windows 2000 IP Configuration
>
> Host Name . . . . . . . . . . . . : DELL
> Primary DNS Suffix . . . . . . . : Rlink.PDC
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : Yes
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : Rlink.PDC
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet Adapter
(10/100)
> Physical Address. . . . . . . . . : 00-06-5B-3D-11-39
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.15
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.15
> Primary WINS Server . . . . . . . : 192.168.1.15
>
> PPP adapter RAS Server (Dial In) Interface:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
> Physical Address. . . . . . . . . : 00-53-45-00-00-00
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.201
> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . : 127.0.0.1
>
> The following is the IPCONFIG from one of the Clients.
>
> Windows 2000 IP Configuration
>
> Host Name . . . . . . . . . . . . : ROB2000
> Primary DNS Suffix . . . . . . . : Rlink.PDC
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : Rlink.PDC
>
> Ethernet adapter Local Area Connection 3:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Realtek RTL8139(A)-based PCI Fast
Ethernet Adapter #3
> Physical Address. . . . . . . . . : 00-50-BA-42-7B-75
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.1.113
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . . . . : 192.168.1.15
> DNS Servers . . . . . . . . . . . : 192.168.1.15
> Primary WINS Server . . . . . . . : 192.168.1.15
> Lease Obtained. . . . . . . . . . : Sunday, November 30, 2003 13:40:29
> Lease Expires . . . . . . . . . . : Tuesday, December 02, 2003 13:40:29
>
>
>

Moishe
Sun Nov 30 23:32:19 CST 2003

Do you have SBS Service Pack 1 or 1A installed?
"RobGMiller" <robgmiller@petrolinks.com> wrote in message
news:88A4CB37-95E3-438B-92D3-072A75C305B0@microsoft.com...
> SBS 2000,
>
> After removing NetBEUI from our network no one can see any of the
workgroups or expand the domain group within My Network Places. All
computers can be found by IP and by Name.

anonymous
Mon Dec 01 08:51:07 CST 2003

All the latest windows update were installed when I started this. SBS SP
appears to contain a bunch of previously released service packs.

anonymous
Mon Dec 01 08:56:05 CST 2003

The current DHCP setting is no

003, 006, 044,045 contain the IP addresss of the SBS serve
015 contains the name of the DOMAIN i.e. Rlink.PD
046 contains 0x

The clients that pickup the NetBIOS setting from the DHCP server can no
browse the network and the ones who have NetBIOS over TCP/IP se
specifically can. I've only looked at Win2000 pro clients for now. We als
have a Win98 and WinMe as well as an ever increasing number of XP-Pr
Clients. Oh yes, there is a couple of Win2000 servers and a couple o
Win2003 servers soon

Have you any idea why it should be this tricky to get all the differen
windows operating systems talking to each other when Name Server technolog
and standards as well as the TCP/IP protocol has been around for so long

One would think that this problem has something to do with the Name Servers
There appears to be two of them running on this Network. It seems to me tha
a client looking for the names of all the computers available via it
connected environment behind a firewall should do a request from the neares
Name Server which should return the computer names and the workgroups an
domains they belong to and the client software should display tha
information

Could there be conflicting information between the WINS server and the DN
server. They both appear to have the same computer names listed. Should
get rid of one of them. Perhaps there is another DNS server listin
conflicting information on another computer. Do windows stations have Name
Servers running. As far as I know none of the other servers we have ar
setup as domain controllers but perhaps I am wrongly assuming that there ar
no Name or WINS servers running on them for that reason.

Marina
Mon Dec 01 17:35:21 CST 2003

What this 045 option doing here?
What do you mean with 2 nameservers running?

Marina

"RobGMiller" <anonymous@discussions.microsoft.com> schreef in bericht
news:D41B085F-C85C-42AE-BC2B-63ED86E1F4D2@microsoft.com...
> The current DHCP setting is now
>
> 003, 006, 044,045 contain the IP addresss of the SBS server
> 015 contains the name of the DOMAIN i.e. Rlink.PDC
> 046 contains 0x8
>
> The clients that pickup the NetBIOS setting from the DHCP server can not
> browse the network and the ones who have NetBIOS over TCP/IP set
> specifically can. I've only looked at Win2000 pro clients for now. We also
> have a Win98 and WinMe as well as an ever increasing number of XP-Pro
> Clients. Oh yes, there is a couple of Win2000 servers and a couple of
> Win2003 servers soon.
>
> Have you any idea why it should be this tricky to get all the different
> windows operating systems talking to each other when Name Server
technology
> and standards as well as the TCP/IP protocol has been around for so long.
>
> One would think that this problem has something to do with the Name
Servers.
> There appears to be two of them running on this Network. It seems to me
that
> a client looking for the names of all the computers available via its
> connected environment behind a firewall should do a request from the
nearest
> Name Server which should return the computer names and the workgroups and
> domains they belong to and the client software should display that
> information.
>
> Could there be conflicting information between the WINS server and the DNS
> server. They both appear to have the same computer names listed. Should I
> get rid of one of them. Perhaps there is another DNS server listing
> conflicting information on another computer. Do windows stations have
Names
> Servers running. As far as I know none of the other servers we have are
> setup as domain controllers but perhaps I am wrongly assuming that there
are
> no Name or WINS servers running on them for that reason.

Mark
Mon Dec 01 20:59:33 CST 2003

why do you have 2 NICs on the same network?!!?!?!? Also, on the server go
to the registry and set IsDomainMAster to TRUE in both places.

--
Sincerely,
Mark Mancini, CCA, CCNA, Master CIW&CI, CNE 4&5, MCSE+I 4&2000
www.MCSE2000.com
www.AppLauncher.com



"RobGMiller" <anonymous@discussions.microsoft.com> wrote in message
news:AAA2298D-F8DB-43F8-B27B-B5EBDEF0CAEB@microsoft.com...
> I hate to say this but now the Clients are not working too well.
>
> Setting the DHCP option 46 to 0x8 seems to have made browsing possible on
the server. Just after I restarted the server one of the stations that was
not browsing before began to browse ok. The next client could not and now
the first one cannot either. Additionally, the drives mapped to shares on
the server are not as responsive. I have to click on the drive listing two
or three times to get to see the folders it contains.
>
> The other options on the DHCP Server are as follows.
>
> 005 = 192.168.1.15
> 006 = 192.168.1.15
> 046 = 0x8
>
> Here are the IPConfig output you requested previously.
>
> The following is the IPCONFIG from the SBS server.
>
> Windows 2000 IP Configuration
>
> Host Name . . . . . . . . . . . . : DELL
> Primary DNS Suffix . . . . . . . : Rlink.PDC
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : Yes
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : Rlink.PDC
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet Adapter
(10/100)
> Physical Address. . . . . . . . . : 00-06-5B-3D-11-39
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.15
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.15
> Primary WINS Server . . . . . . . : 192.168.1.15
>
> PPP adapter RAS Server (Dial In) Interface:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
> Physical Address. . . . . . . . . : 00-53-45-00-00-00
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.201
> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . : 127.0.0.1
>
> The following is the IPCONFIG from one of the Clients.
>
> Windows 2000 IP Configuration
>
> Host Name . . . . . . . . . . . . : ROB2000
> Primary DNS Suffix . . . . . . . : Rlink.PDC
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : Rlink.PDC
>
> Ethernet adapter Local Area Connection 3:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Realtek RTL8139(A)-based PCI Fast
Ethernet Adapter #3
> Physical Address. . . . . . . . . : 00-50-BA-42-7B-75
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.1.113
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DHCP Server . . . . . . . . . . . : 192.168.1.15
> DNS Servers . . . . . . . . . . . : 192.168.1.15
> Primary WINS Server . . . . . . . : 192.168.1.15
> Lease Obtained. . . . . . . . . . : Sunday, November 30, 2003 13:40:29
> Lease Expires . . . . . . . . . . : Tuesday, December 02, 2003 13:40:29
>
>
>

anonymous
Mon Dec 01 21:06:19 CST 2003

The 045 is for NetBios over TCP/IP NBDD. Since the system seems to require NetBios over TCP/IP but does not seem to acquire this property from the DHCP server I thought I'd see if this has an effect but it does not. The Clients still cannot browse the network unless The NetBios over TCP/IP is enable specifically.

Isn't the WINS server a name server of sorts. Lets say that a name listed in the WINS database points to a different IP than the same name listed in the DNS server on the same network. Would that cause a problem or would the client acquire the first address it can resolve. This is just musing of course, I really have no idea how a station acquires a list of all computer names and groups on its network. Does it rely on the Name servers or does each station broadcast that information.

In any case, the current status is that, even wth the 045 option set, the clients can only browse the nework if their NetBios over TCP/IP is turned is enabled from the WINS Screen on the network connection Properties.

I will remove the 045 and try it again.

Kathy
Tue Dec 02 04:11:52 CST 2003

BTW If a WINS server has 2 NICS on the same network, your name resolution
will be stuffed. There is a Q article on this. DNS doesn't give out a list
of work groups and clients as you suggest - that's the job of the browse
master for old clients (NT and 9x) and AD for 2k and XP. It can take around
30 minutes (more on a large network) for machines to appear in the browse
list. 2k and XP use host name resolution before Netbios resolution. BTW If
you have set 046 to H node (8), it tries WINS first, then broadcast.

If you have WINS and DNS running and the WINS server gives out a different
IP address from DNS for a particular machine, a static IP address in DNS is
wrong. That's because the client registers its IP address with both WINS and
DDNS - it can only register the one it has, so if they are different, the
address must have been entered as a static address in DNS. Of course, if you
have two NICs on the same network, you might well get this problem.

You will also have problems if entries in your hosts or lmhosts files don't
match reality (DDNS/WINS). Have you checked that the clients are registering
with DDNS?

You might find this list of articles useful
http://www.labmice.net/networking/browsersrvc.htm

and this webcast
http://support.microsoft.com/default.aspx?scid=/servicedesks/webcasts/wcd121100/wcdblurb121100.asp

Kathy

"RobGMiller" <anonymous@discussions.microsoft.com> wrote in message
news:26A5ABBC-71D0-4AB1-9B13-EB22B9FA5513@microsoft.com...
> The 045 is for NetBios over TCP/IP NBDD. Since the system seems to require
NetBios over TCP/IP but does not seem to acquire this property from the DHCP
server I thought I'd see if this has an effect but it does not. The Clients
still cannot browse the network unless The NetBios over TCP/IP is enable
specifically.
>
> Isn't the WINS server a name server of sorts. Lets say that a name listed
in the WINS database points to a different IP than the same name listed in
the DNS server on the same network. Would that cause a problem or would the
client acquire the first address it can resolve. This is just musing of
course, I really have no idea how a station acquires a list of all computer
names and groups on its network. Does it rely on the Name servers or does
each station broadcast that information.
>
> In any case, the current status is that, even wth the 045 option set, the
clients can only browse the nework if their NetBios over TCP/IP is turned is
enabled from the WINS Screen on the network connection Properties.
>
> I will remove the 045 and try it again.
>
>

anonymous
Tue Dec 02 05:26:08 CST 2003

I was wondering why 2 NICs show up in the Ipconfig output myself. The second NIC (201) appears to be assigned by the RAS. Is this not a standard occurance when the SBServer is used for RAS connection?

The RAS does appear to connect our external clients throught VPN adequately althought they cant browse the network either. The IP's assigned, I presume by the RAS, are in the 200+ range. In fact the VPN connected clients cant event find the main domain name workgroup. They can only display their own workgroup and the only computer listed within it is itself. However, they can access all computers with the correct level of permission if connected by Name or IP address specifically.

anonymous
Tue Dec 02 08:11:06 CST 2003

Actually it was not a suggestion, it was just an expression of confusion -ckl. Your explanation on what the AD does and the articles you suggested have served to point me in the right direction. Thanks.

I will make the observation that prior to setting the 046 option to 0x8 the SBServer itself could not browse properly. Now, it can, with no missing workgroups or computers. If the clients cannot see the same picture does this not suggest that the AD is in fact aware of all the proper browse information but the clients just cant retrieve that information adequately.

I have just checked another computer and it is set for NetBios over TCP/IP. It can only see the main domain group called Rlink but if I try to expand it, the returned message is "Rlink is not accessible The remote computer is not available". On the other hand the directory shortcut is available from My Network Places (Win2k OS) and will display the Rlink Domain Icon and, if expanded, will show all the Computers and users on the domain. That indicates that the Active Directory is accessible from the client. It just wont return an accurate browser listing.

Yesterday, I observed that IF the NetBios over TCP/IP was set on the clients, they could browse adequately, that is not the case today. The situation seems to be changing. The only change I've made since yesterday was to remove the 045 option from the DHCP settings and I rebooted the SBServer.

I have set IsDomainMaster to TRUE in both places in the registry as suggested by Mark Mancini.

Do we think the two NICs condition is a problem and if so, how should the RAS be configured to avoid it.

anonymous
Tue Dec 02 17:11:05 CST 2003

After setting the IsDomainMaster and bebooting both the Server and a station it was able to get a normal view of the network. I left it for a while and after a few hours that station has stopped being able to browse the network. The server however, can still see everything. On the other hand, it does take time to come up with the display. About 7 seconds to show the 3 groups and about 14 seconds to show the computers within the main domain group. There are only 10 computers listed. Its is possible that some of the computers that are listed as part of this domain are no longer on the network. I'll have to check that out.

Marina
Tue Dec 02 18:30:04 CST 2003

Rob,

What exactly do you mean with the 3 groups?
Aren't all computer member of the same domain?

Marina

"RobGMiller" <anonymous@discussions.microsoft.com> schreef in bericht
news:B223982B-A507-4305-ADF1-977E9E4699CD@microsoft.com...
> After setting the IsDomainMaster and bebooting both the Server and a
station it was able to get a normal view of the network. I left it for a
while and after a few hours that station has stopped being able to browse
the network. The server however, can still see everything. On the other
hand, it does take time to come up with the display. About 7 seconds to show
the 3 groups and about 14 seconds to show the computers within the main
domain group. There are only 10 computers listed. Its is possible that some
of the computers that are listed as part of this domain are no longer on the
network. I'll have to check that out.

anonymous
Wed Dec 03 21:11:13 CST 2003

Hi Marina

No, some computers are members of different groups and not members of the primary domain. These are computers used to test our software which is supposed to run on stand alone servers. One is a Linux box running samba to connect to our network. It was setup at a time when we had an NT4 Server with a different main domain group. I just left it that way because we just use it to support an Oracle Server. We dont need to access its drives directly.

anonymous
Wed Dec 03 21:16:11 CST 2003

Are you saying that we cannot have some stations or servers on our network that are not part of the SBS controlled domain.

I will try to disconnect them all to see if the rest of the network will start operating normally.

I will also try to do the edits in 292822

anonymous
Sat Dec 06 09:01:06 CST 2003

This is my third try at a reply.

I did the edits suggested in the 292822 article. It seems to have worked. The SBServer does browse much faster and all stations that are part of the Domain or not can see all other stations on the network.

The second IP of 201, as described using Ipconfig is still generated by the RAS/VPN.

I was wondering if you think that I should keep working towards changing this condition. The Clients external cannot see the rest of the network when connected by VPN.

Thanks for your time, it is much appreciated.

Merv
Sat Dec 06 09:39:38 CST 2003

Rob:

In the VPN connectoid of the remote computers, under TCP/IP...Advanced,
point the DNS and WINS settings to the IP address of the SBS server. If
that doesn't allow for network browsing, change the name of the workgroup on
the remote computer to match the domain name of the SBS (if your SBS domain
is "company.local", use "company" as the workgroup name on the remote
computer). Then log onto the remote computer with a username/password that
is valid in the SBS domain and has dial-in permissions. If the remote
workstations are Win9x, you may also need to configure a Lmhosts file on
them that point to the SBS server IP.

--
Merv Porter [SBS MVP]
===================================

"RobGMiller" <anonymous@discussions.microsoft.com> wrote in message
news:757B6390-2289-48F0-9546-8A1B8891107F@microsoft.com...
> This is my third try at a reply.
>
> I did the edits suggested in the 292822 article. It seems to have worked.
The SBServer does browse much faster and all stations that are part of the
Domain or not can see all other stations on the network.
>
> The second IP of 201, as described using Ipconfig is still generated by
the RAS/VPN.
>
> I was wondering if you think that I should keep working towards changing
this condition. The Clients external cannot see the rest of the network when
connected by VPN.
>
> Thanks for your time, it is much appreciated.

anonymous
Sat Dec 13 10:46:05 CST 2003

Just came back to thank you all for helping me with this issue.

The last fix did work well all computers can now browse the newtwork and see all computers with all workgroups weather they are authenticated by the domain or not.

The only remaining issue has to do with the VPN via RAS connected clients who cant see any network computers and only the domain group wth no computers listed in it. This may be the preferred way to connect to a SBServer. In any case, it is good enough since the clients can find the shares by IP and can access the Exchange server on the SBServer

Thanks again