Sammy
Guest
|
 Posted:
Wed Jan 26, 2005 4:29 pm Post subject:
Computer name not seen... |
|
|
My network is setup in the following way:
ISP -> DSL Modem -> Switch#1 -> Firewall Box -> Switch#2 -> Several Windows
XP machines.
There is one machine running Windows 2003 Server, that has two NICs. NIC#1
is connected to Switch#1 and has a static IP provided by my ISP. Hence,
NIC#1 provides the internet connection to the server. NIC#2 is connected to
Switch#2. The reason I did this, is so that the XP machines behind the
firewall can see the Win2003 Server machine and be able to file share with
it.
1- Is this the right way to do it?
2- I can't see the server machine from any XP machine by its name, only it's
IP. So if I remote connect to 192.168.111.2 (NIC#2 DHCPed address of the
server) it works, but if I try to remote connect to MYWINSERVER it tells me
it can't find it. Why is that?
Thank you very much,
Sammy |
|
Steven L Umbach
Guest
|
| Posted:
Thu Jan 27, 2005 12:26 am Post subject:
Re: Computer name not seen... |
|
|
If your firewall can do NAT, you probably would have better luck using NAT
to share internet access among all the computers and use the NAT/firewall as
the default gateway for all the computers and then you would need only one
nic in your W2003 Server. Your W2003 Server is probably the master browser
and when master browser's have more than one nic, browse list problems can
ensue. You still may be able to resolve it as is if you make sure that
Client for Microsoft Networks, netbios over tcp/ip, and file and print
sharing are DISABLED on the EXTERNAL nic only. Go to the adapter
properties/tcp ip/advances/wins and you can disable NBT there. After you are
done use nbtstat -n to make sure that the W2003 Server is still registering
at least three netbios names. Also in network connections/advanced settings
make sure that the internal lan nic is at the top of the priority list.
Another thing you could try is to disable the computer browser service on
the W2003 Server and then some other computer would need to take over the
master browser role. --- Steve
"Sammy" <sammy@picostation.com> wrote in message
news:OA0N1H5AFHA.1400@TK2MSFTNGP11.phx.gbl...
| Quote: | My network is setup in the following way:
ISP -> DSL Modem -> Switch#1 -> Firewall Box -> Switch#2 -> Several
Windows XP machines.
There is one machine running Windows 2003 Server, that has two NICs. NIC#1
is connected to Switch#1 and has a static IP provided by my ISP. Hence,
NIC#1 provides the internet connection to the server. NIC#2 is connected
to Switch#2. The reason I did this, is so that the XP machines behind the
firewall can see the Win2003 Server machine and be able to file share with
it.
1- Is this the right way to do it?
2- I can't see the server machine from any XP machine by its name, only
it's IP. So if I remote connect to 192.168.111.2 (NIC#2 DHCPed address of
the server) it works, but if I try to remote connect to MYWINSERVER it
tells me it can't find it. Why is that?
Thank you very much,
Sammy
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in