Need Help Quickly

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Joseph - 30 Dec 2003 21:59 GMT

Running a test environment of our soon to be installed new
server, PC's and Software.

We have a test server of Windows2000 SBS. All clients are
to be windows2000 and all licences etc for Exchange in
place.

Our problem is this.
-----------------------------------------------------------
We have a win2K SBS server installed and tried to connect
a new windows2000 PC to the server via a switch.
The new PC can see the server name (TestServer) in network
neighbourhood. However......

What i will do is list the problems and see if someone can
explain to me what's going on here.

From the windows2k pc.
1- We can see the servername (TestServer) in here, However
when we double click the testserver name we get the error
message "unable to browse network"
2- We can't ping the server IP Address of 192.168.16.2 it
says request timed out.
3 - When do do an IPCONFIG on the windows2000 PC the
address assigned to the PC is 192.168.16.21 and the name
of the DHCP assigning server is 192.168.16.2

From Server
1 - If we do an IPCONFIG we see the address of
192.168.16.2
2 - If we ping 192.168.16.21 we get "Destination host
unreachable"
3 - We can however ping it's own address of 192.168.16.2

Please if anyone can help with a speediant response to my
problem i would very much appreciate it.

Reply to this Message

Marina Roos - 31 Dec 2003 01:23 GMT

Can you post the complete ipconfig from the server and the client? How many
nics in the server? Did you join the workstation to the domain?

--
Regards,

Marina

> Running a test environment of our soon to be installed new
> server, PC's and Software.
[quoted text clipped - 32 lines]
> Please if anyone can help with a speediant response to my
> problem i would very much appreciate it.

Reply to this Message

Mark Mancini - 31 Dec 2003 01:40 GMT

your default gateway should be in there are your router but it shouldn't
give you DHU unless there was some other issue. Make sure that the machines
are not plugged into the first or last port of the hub which is usually for
uplink. Second, Network Neighborhood does NOT test connectivity and should
not even be looked at. Make sure subnet mask is 24 bits on both. But I'm
betting it's a hardware issue.

Signature

Sincerely,
Mark Mancini, CCA, CCNA, Master CIW&CI, CNE 4&5, MCSE+I 4&2000
www.MCSE2000.com
www.AppLauncher.com

Reply to this Message

Cris Hanna \(SBS-MVP\) - 31 Dec 2003 10:07 GMT

I would tend to agree that this is probably hardware.

How many nics in your Server??
The correct answer should be two
One connected to your switch
IP 192.168.16.2 Subnet Mask 255.255.255.0 GW should be blank
DNS Address should be 192.168.16.2

Second NIC should be connected to your internet connection, either with a
static live routeable IP or if you are getting a dynamic IP from your ISP,
then a router from Linksys, DLink, Netgear etc, with DHCP function turned
off and a static IP assigned to that second nic to match the IP scheme of
the router (typically 192.168.0.2 Subnet Mask 255.255.255.0 Gateway
192.168.0.1 Preferred DNS should be the IP of the INTERNAL NIC)

once you've confirmed all that, assign a static IP address to your
workstation, 192.168.16.100 Sub 255.255.255.0 Gateway 192.168.16.2
Preferred DNS 192.168.16.2

Reboot the server, then the workstation

Can they talk to each other now...if not
either you have a bad nic in the server, bad cable, (can the server ping its
own internal IP, if yes these two are probably ok) Same for workstation.

If they both can ping themselves, but have trouble with each other, go buy a
cheap 4 port hub and test again ( you can always return that)

Don't you just love the detective work

Signature

Cris Hanna [SBS-MVP]
-------------------------
Please do not directly to me but rather reply to the newsgroup so that all
may benefit from the information.

Reply to this Message