WINS & VLANS

  • Thread starter Thread starter B3
  • Start date Start date
B

B3

After setting up VLANs on Intel Pro adapter on Windows
2000 server, replication stops. What I found on Intel's
website was WINS replication will only take place on the
first VLAN. The problem is that WINS server by its own
takes up the last VLAN's IP Address. I uninstalled WINS
service & reinstalled it but nothing does the trick. Is
there any way where I can force the WINS server to have a
particular IP Address rather than it picking on its own??
Any help will be appreciated.
 
It's generally considered bad practice to have WINS running on any kind of
multi-homed system. If at all possible, I'd run WINS on another box with
one NIC and one IP address.

Out of interest, what are you trying to achieve with the multiple VLANs?

Oli
 
You cannot do this with a WINS server and expect it to work. Netbios can
only bind to one interface and one day it will be one and the next it will
be the other. You may try playing with the binding order but this could be a
headache. Do yourself a favor and put WINS on a box with one nic.
 
Which means, I'll have to have one more Win2K DC installed
on the network just running WINS???
 
Who said anything about it being a DC? Number one rule: do not run WINS on
a box with more than one NIC or IP address. You're free to ignore that
advice if you wish. If you want your network to work properly, though, just
run with it.

Oli
 
I installed WINS on a seperate box with just one NIC -
Windows 95 clients still cannot logon to AD!!!
 
Its a Windows 2000 domain but we have a few older 95
workstations.
-----Original Message-----
I installed WINS on a seperate box with just one NIC -
Windows 95 clients still cannot logon to AD!!!
Click to expand...

Windows 95?? Is it a 2003 Domain? (I don't have your earlier posts).

811497 - Error Message When Windows 95 or Windows NT 4.0 Client
Logs On to Windows Server 2003 Domain
http://support.microsoft.com/default.aspx?scid=kb;en- us;811497


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


.
Click to expand...
 
In my experience, Windows 95 was always a bit funny when the PDC didn't
reside on the same subnet.

Having said that, I haven't touched a Windows 95 box for at least five
years.

Oli
 
Well, without WINS it isn't going to work. If this Win95 machine isn't using
the proper WINS Server that the DC is also using it isn't going to work.
You need to see both the DC and the Win95 box listed in the WINS's database.

It doesn't matter if it is normal LAN Ethernet or VPN, the same principles
apply.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


B3 said:
Its a Windows 2000 domain but we have a few older 95
workstations.
-----Original Message-----
I installed WINS on a seperate box with just one NIC -
Windows 95 clients still cannot logon to AD!!!
Click to expand...

Windows 95?? Is it a 2003 Domain? (I don't have your earlier posts).

811497 - Error Message When Windows 95 or Windows NT 4.0 Client
Logs On to Windows Server 2003 Domain
http://support.microsoft.com/default.aspx?scid=kb;en- us;811497


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


.
Click to expand...
Click to expand...
 
Back
Top