netbios name no longer working after IP address change

We have a simple network of mostly composed of Win98/WinXP computers and a
"server" running Win2K pro with "computer name" fbasvr1
I made a change to the network that involved using a DSL router as an
internet gateway, NAT server and DHCP server.

- before, I was using fbasvr1 as a dhcp server handing out address
192.168.0.###
- Now the router is handing out addresses like 10.0.0.#
- fbasvr1 used to have address 192.168.0.24 now it has address 10.0.0.2

Everything is working fine except that computers on the network still think
that fbasvr1 has the 192. address instead of the 10. address.

Also, when I ghost machine on the network and use a boot CD "Ultimate Book
Disk" to gain network access. I used to be able to do:
net use g: \\fbasvr1\ghost

this also no longer works. There is no "wins" server running on the
network.

Questions:

- Why do computer on the network still think that fbasvr1 has the old
address?
- Is there a "standard procedure" for make the changes that I needed to
make?

any help would be appreciated.

gkelly

Hi GKelly,

You really have two options here.

1. Stop the DHCP service on the router and tell it that its internal network
is your 192.168.0.0/24 (I am assuming the subnet mask is normal for a class
C)

2. Turn off DHCP on the "server" make sure that there are no references to
the 192.168.0.0/24 network in your DNS or LMHOSTS files. You would then
either need to make DNS entries for the 10.0.0.0/8 network or try to rely on
the NetBIOS MasterBrowser for naming.

Go with option 1 if possible. It'll be easier.

--
Ryan Hanisco
MCSE, MCDBA
Flagship Integration Services

"gkelly" wrote in message
...
We have a simple network of mostly composed of Win98/WinXP computers and a
"server" running Win2K pro with "computer name" fbasvr1
I made a change to the network that involved using a DSL router as an
internet gateway, NAT server and DHCP server.

- before, I was using fbasvr1 as a dhcp server handing out address
192.168.0.###
- Now the router is handing out addresses like 10.0.0.#
- fbasvr1 used to have address 192.168.0.24 now it has address 10.0.0.2

Everything is working fine except that computers on the network still
think
that fbasvr1 has the 192. address instead of the 10. address.

Also, when I ghost machine on the network and use a boot CD "Ultimate Book
Disk" to gain network access. I used to be able to do:
net use g: \\fbasvr1\ghost

this also no longer works. There is no "wins" server running on the
network.

Questions:

- Why do computer on the network still think that fbasvr1 has the old
address?
- Is there a "standard procedure" for make the changes that I needed to
make?

any help would be appreciated.

gkelly

Hi GKelly,

You really have two options here.

1. Stop the DHCP service on the router and tell it that its internal network
is your 192.168.0.0/24 (I am assuming the subnet mask is normal for a class
C)

2. Turn off DHCP on the "server" make sure that there are no references to
the 192.168.0.0/24 network in your DNS or LMHOSTS files. You would then
either need to make DNS entries for the 10.0.0.0/8 network or try to rely on
the NetBIOS MasterBrowser for naming.

Go with option 1 if possible. It'll be easier.

--
Ryan Hanisco
MCSE, MCDBA
Flagship Integration Services

"gkelly" wrote in message
...
We have a simple network of mostly composed of Win98/WinXP computers and a
"server" running Win2K pro with "computer name" fbasvr1
I made a change to the network that involved using a DSL router as an
internet gateway, NAT server and DHCP server.

- before, I was using fbasvr1 as a dhcp server handing out address
192.168.0.###
- Now the router is handing out addresses like 10.0.0.#
- fbasvr1 used to have address 192.168.0.24 now it has address 10.0.0.2

Everything is working fine except that computers on the network still
think
that fbasvr1 has the 192. address instead of the 10. address.

Also, when I ghost machine on the network and use a boot CD "Ultimate Book
Disk" to gain network access. I used to be able to do:
net use g: \\fbasvr1\ghost

this also no longer works. There is no "wins" server running on the
network.

Questions:

- Why do computer on the network still think that fbasvr1 has the old
address?
- Is there a "standard procedure" for make the changes that I needed to
make?

any help would be appreciated.

gkelly

DHCP is no longer running on the server (fbasvr1) and we do not run our own
dns server nor have I hardcoded entries in the lmhosts files.
I'll try the other solution though. thanks.
gkelly

"Ryan Hanisco" wrote in message
...
Hi GKelly,

You really have two options here.

1. Stop the DHCP service on the router and tell it that its internal
network
is your 192.168.0.0/24 (I am assuming the subnet mask is normal for a
class
C)

2. Turn off DHCP on the "server" make sure that there are no references to
the 192.168.0.0/24 network in your DNS or LMHOSTS files. You would then
either need to make DNS entries for the 10.0.0.0/8 network or try to rely
on
the NetBIOS MasterBrowser for naming.

Go with option 1 if possible. It'll be easier.

--
Ryan Hanisco
MCSE, MCDBA
Flagship Integration Services

"gkelly" wrote in message
...
We have a simple network of mostly composed of Win98/WinXP computers and
a
"server" running Win2K pro with "computer name" fbasvr1
I made a change to the network that involved using a DSL router as an
internet gateway, NAT server and DHCP server.

- before, I was using fbasvr1 as a dhcp server handing out address
192.168.0.###
- Now the router is handing out addresses like 10.0.0.#
- fbasvr1 used to have address 192.168.0.24 now it has address 10.0.0.2

Everything is working fine except that computers on the network still
think
that fbasvr1 has the 192. address instead of the 10. address.

Also, when I ghost machine on the network and use a boot CD "Ultimate
Book
Disk" to gain network access. I used to be able to do:
net use g: \\fbasvr1\ghost

this also no longer works. There is no "wins" server running on the
network.

Questions:

- Why do computer on the network still think that fbasvr1 has the old
address?
- Is there a "standard procedure" for make the changes that I needed to
make?

any help would be appreciated.

gkelly

DHCP is no longer running on the server (fbasvr1) and we do not run our own
dns server nor have I hardcoded entries in the lmhosts files.
I'll try the other solution though. thanks.
gkelly

"Ryan Hanisco" wrote in message
...
Hi GKelly,

You really have two options here.

1. Stop the DHCP service on the router and tell it that its internal
network
is your 192.168.0.0/24 (I am assuming the subnet mask is normal for a
class
C)

2. Turn off DHCP on the "server" make sure that there are no references to
the 192.168.0.0/24 network in your DNS or LMHOSTS files. You would then
either need to make DNS entries for the 10.0.0.0/8 network or try to rely
on
the NetBIOS MasterBrowser for naming.

Go with option 1 if possible. It'll be easier.

--
Ryan Hanisco
MCSE, MCDBA
Flagship Integration Services

"gkelly" wrote in message
...
We have a simple network of mostly composed of Win98/WinXP computers and
a
"server" running Win2K pro with "computer name" fbasvr1
I made a change to the network that involved using a DSL router as an
internet gateway, NAT server and DHCP server.

- before, I was using fbasvr1 as a dhcp server handing out address
192.168.0.###
- Now the router is handing out addresses like 10.0.0.#
- fbasvr1 used to have address 192.168.0.24 now it has address 10.0.0.2

Everything is working fine except that computers on the network still
think
that fbasvr1 has the 192. address instead of the 10. address.

Also, when I ghost machine on the network and use a boot CD "Ultimate
Book
Disk" to gain network access. I used to be able to do:
net use g: \\fbasvr1\ghost

this also no longer works. There is no "wins" server running on the
network.

Questions:

- Why do computer on the network still think that fbasvr1 has the old
address?
- Is there a "standard procedure" for make the changes that I needed to
make?

any help would be appreciated.

gkelly