Move from NT 4 to SBS 2003 VPN netbios issues

I am in the middle of moving from an NT 4 sp6a server(static ip 192.168.1.11) to SBS 2003 standard ed(static ip 192.168.1.10). Before I can complete the move I must verify that a remote client can run an application on SBS 2003 server. Currently the SBS server is the DHCP running WINS. Originally the NT server was the DHCP running WINS. WINS is still running on the NT server. There is an existing ipsec tunnel (watchguard firebox 700 branch office manual ipsec tunnel to soho 6.). The client (win 98) can ping both the NT server and the SBS 2003 ip addresses. I have also been able to map drives to both servers and access the files. However, I can ping the netbios name of the NT Server but I can't ping the Netbios name of the SBS. The critical app requires netbios name resolution. What do I need to configure to resolve the netbios names. Do I need to do a static mapping to the new server?

The Win98 machine is probably still using the WINS on NT4 which doesn't have
the record in it for the new server. If it is recieving all this via DHCP,
then make sure the NT box isn't still giving out DHCP configs and then use
WINIPCFG on the Win98 machine to force a refresh of the network config so
that it is then using the right WINS server setting.

Also make sure that the new server is also using its own WINS server in its
own network settings or it will not have itself listed in its own WINS
records. Aside from static entries, the only machines listed in WINS are
the machines that also use the WINS.


--

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


"pk1234" <(E-Mail Removed)> wrote in message
news:920117B1-789E-45CD-BB84-(E-Mail Removed)...
> I am in the middle of moving from an NT 4 sp6a server(static ip
192.168.1.11) to SBS 2003 standard ed(static ip 192.168.1.10). Before I can
complete the move I must verify that a remote client can run an application
on SBS 2003 server. Currently the SBS server is the DHCP running WINS.
Originally the NT server was the DHCP running WINS. WINS is still running
on the NT server. There is an existing ipsec tunnel (watchguard firebox 700
branch office manual ipsec tunnel to soho 6.). The client (win 98) can
ping both the NT server and the SBS 2003 ip addresses. I have also been
able to map drives to both servers and access the files. However, I can
ping the netbios name of the NT Server but I can't ping the Netbios name of
the SBS. The critical app requires netbios name resolution. What do I need
to configure to resolve the netbios names. Do I need to do a static mapping
to the new server?

The NT server has DHCP turned off (SBS required this
during installation). DHCP is definately being handled
by the SBS 2003 server. WINS is installed on the new
server (it is listed in its own WINS record) and is
functioning for the internal network (behind the Firebox
700)as the new server can be pinged by name by all PCs
(mixture of Win 98, 2000, and XP) and is also visible and
can be accessed in Network Neighborhood of NT server.
Once found in network neighborhood the NT server can also
ping the new server by name. The problem seems to be the
client on the other end of the ipsec tunnel (behind the
Soho 6 box). Is it an either or situation? Do I have to
turn off WINS on the NT Server in order for it to pick up
the netbios name of the new server?
>-----Original Message-----
>The Win98 machine is probably still using the WINS on
NT4 which doesn't have
>the record in it for the new server. If it is recieving
all this via DHCP,
>then make sure the NT box isn't still giving out DHCP
configs and then use
>WINIPCFG on the Win98 machine to force a refresh of the
network config so
>that it is then using the right WINS server setting.
>
>Also make sure that the new server is also using its own
WINS server in its
>own network settings or it will not have itself listed
in its own WINS
>records. Aside from static entries, the only machines
listed in WINS are
>the machines that also use the WINS.
>
>
>--
>
>Phillip Windell [MCP, MVP, CCNA]
>www.wandtv.com
>
>
>"pk1234" <(E-Mail Removed)> wrote in
message
>news:920117B1-789E-45CD-BB84-
(E-Mail Removed)...
>> I am in the middle of moving from an NT 4 sp6a server
(static ip
>192.168.1.11) to SBS 2003 standard ed(static ip
192.168.1.10). Before I can
>complete the move I must verify that a remote client can
run an application
>on SBS 2003 server. Currently the SBS server is the
DHCP running WINS.
>Originally the NT server was the DHCP running WINS.
WINS is still running
>on the NT server. There is an existing ipsec tunnel
(watchguard firebox 700
>branch office manual ipsec tunnel to soho 6.). The
client (win 98) can
>ping both the NT server and the SBS 2003 ip addresses.
I have also been
>able to map drives to both servers and access the
files. However, I can
>ping the netbios name of the NT Server but I can't ping
the Netbios name of
>the SBS. The critical app requires netbios name
resolution. What do I need
>to configure to resolve the netbios names. Do I need to
do a static mapping
>to the new server?
>
>
>.
>

But what WINS Server IP# is the 98 client actually recieving? Don't worry
about what it should receive but look at what it is actually receiving. Use
WINIPCFG on the 98 box to find out. If it gets the wrong one or is just
staying blank then it may be the problem. It should get both a DNS entry
and a WINS entry.

Also make sure the new server has "Netbios over TCP/IP" enabled.

Also your Watchguard box is acting as a VPN router , correct? Then I would
assume these are different subnets on each side of it? Then since DCHP
requests don't cross subnets, the routing device (Watchguard VPN box in this
case) must froward those DHCP requests to the right place,...are you sure
that it is still working right with the new server. I know with HP routing
devices you must specify the exact IP# of the DHCP server or it doesn't
work, so if the IP# of the DHCP server changes, it has to be adjusted in the
routing devices as well.

--

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