Static IP Address problem

[Chris]

I am setting up a copy of Server 2003 in an enviroment
that includes several NT4 servers and many Win98 clients.
They have Wins, Netbeui, workgroup and use hosts files .
The problem right now is that when I set up the server
with a static IP address I cannot find any of the servers
in network neighborhood or by searching on network
neighborhood. However I can ping by name, so it looks like
wins is working. I did enable NetBios over TCP in the
Static setup. If I change the NIC to DHCP and allow the
existing DHCP server to assign the IP address (gateway
wins etc) I can find the original NT4 machines with search
and browseing Network Neighborhood. I have carefully
matched the WINs servers in the static setup but still no
luck.

What else can I do here?

Chris

 

[Steve Perry]

Are you specifying DNS on you Static Addressing? Do you have an internal
DNS server on your network? Even though your 2003 server has use NetBios
over TCP, it still uses TCP/IP to resolve names.

Steve Perry

 

[Guest]

I have specified my ISP's DNS and I have added (the way we
are configured now) DNS to this server with itself as the
DNS of choice. In both cases the same results.

Chris

 

[Steve Perry]

If this is your DNS server, it should be configured as the primary DNS
server and you should have no other DNS servers listed except it on your
network or in your settings. It is a good idea to have a second one set up
that is a secondary.

If this machine is your primary DNS server your DNS listing should be just
it, and if you have one a secondary listing. All of your machines on your
network should only have this machine and any other secondary DNS server on
your network.

Steve Perry

 

[Guest]

Ok, the only thing I did not do was give the NT4 machine
the ip address of the 2003 machine as DNS server. I did
set 2003 up as primary, I used Forwarders to access the
outside world and I added a static mapping ("a" record )
for the NT machine I was interested in. I also added a
record for my WINs servers.

I will test again, but will add the ip address of 2003 to
the NT4 machine's DNS entry in the IP setup area.

Chris

 

[Bob Qin [MSFT]]

Hi Chris,

Did you check what was the browser master in your network when you set
static IP on the Windows Server 2003?

It looks like to be a browsing issues. In Windows network environment,
there is a service called "browser service" which is responsible for
maintaining a "computer list" in the network.

You can see other computers from the "my network place", which is actually
the list.

If you can not see other computers, it does not mean you can not access it.
In many cases, you can still access a computer via its UNC path like
<\\serverip\sharename>.

The detailed theory is more complex. We can refer to the following document
for details:

Windows 2000 Browser Service
http://www.microsoft.com/windows2000/techinfo/reskit/en-us/default.asp?url=/
windows2000/techinfo/reskit/en-us/cnet/cnfi_brs_MNQP.asp

The browser service troubleshooting is always time-consuming. I recommend
that you refer to the following article to troubleshoot browsing issues.

188305 Troubleshooting the Microsoft Computer Browser Service
http://support.microsoft.com/?id=188305

Have a nice day!

Regards,
Bob Qin
Product Support Services
Microsoft Corporation

Get Secure! - www.microsoft.com/security

====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.