Urgent! Windows sbs 2003 network problem

  • Thread starter Thread starter Charles Collette
  • Start date Start date
C

Charles Collette

Hello to you all,

Did install Windows Small Business Server 2003 on a HP Proliant g3.
Everything worked fine but than..... no warning in any event log but
no network connections anymore.

I think I have checked everything there is to check, but who knows I
might have missed something. Checked cable, switch, drivers,
even-logs, did a repear install, reboot several times and even
installed Linux on this machine (and as expected, no problems in Linux
- so this doesn't seem to be a hardware problem).

But Windows SBS 2003 won't connect to anything. Can ping localhost and
its own ip-address but that's about it.

Have seen messages about this type of behavior (don't know yet if it
is an error) in lots of placed accross the internet, but didn't see
any solution, well apart from reinstalling the whole thing.

So, please if you know or have any idea how to solve this, please
please let me know, soon.

TIA,
Charles Collette
 
Charles Collette said:
Did install Windows Small Business Server 2003 on a HP Proliant g3.
Everything worked fine but than..... no warning in any event log but
no network connections anymore.

I think I have checked everything there is to check, but who knows I
might have missed something. Checked cable, switch, drivers,
even-logs, did a repear install, reboot several times and even
installed Linux on this machine (and as expected, no problems in Linux
- so this doesn't seem to be a hardware problem).
Click to expand...

Drive maybe? IP address not really the same?
But Windows SBS 2003 won't connect to anything. Can ping localhost and
its own ip-address but that's about it.
Click to expand...

That is pretty much evidence of cable, NIC, driver, or IP address
failure -- IP failed to initialize and bind to an adapter if you cannot
ping 127.0.0.1

You tested cable & NIC with Linux which leaves drive and misconfiguration.

Why don't you post your IPCONFIG /ALL output?
Have seen messages about this type of behavior (don't know yet if it
is an error) in lots of placed accross the internet, but didn't see
any solution, well apart from reinstalling the whole thing.
Click to expand...

It's likely a misconfiguration -- so if that's what you mean by
"type of error" it's almost certainly something you typed incorrectly
in the NIC properties OR a bad driver (based on your report.)
 
Drive maybe? IP address not really the same?


That is pretty much evidence of cable, NIC, driver, or IP address
failure -- IP failed to initialize and bind to an adapter if you cannot
ping 127.0.0.1

You tested cable & NIC with Linux which leaves drive and misconfiguration.

Why don't you post your IPCONFIG /ALL output?


It's likely a misconfiguration -- so if that's what you mean by
"type of error" it's almost certainly something you typed incorrectly
in the NIC properties OR a bad driver (based on your report.)
Click to expand...

Here are the results of ipconfig and ping. Doing a ping to anything
outside the server gives time-outs and pinging the server from any
machine in the local network also gives time-outs.

C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : WINSERVER
Primary Dns Suffix . . . . . . . : vvv-Wymbrits.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : vvv-Wymbrits.local

Ethernet adapter Server Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : BCM5703 Gigabit Ethernet
Physical Address. . . . . . . . . : 00-0E-7F-B4-EF-5C
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.100.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.100.2
DNS Servers . . . . . . . . . . . : 192.168.100.1
Primary WINS Server . . . . . . . : 192.168.100.1

C:\Documents and Settings\Administrator>ping localhost

Pinging WINSERVER.vvv-Wymbrits.local [127.0.0.1] with 32 bytes of
data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>ping 192.168.100.1

Pinging 192.168.100.1 with 32 bytes of data:

Reply from 192.168.100.1: bytes=32 time<1ms TTL=128
Reply from 192.168.100.1: bytes=32 time<1ms TTL=128
Reply from 192.168.100.1: bytes=32 time<1ms TTL=128
Reply from 192.168.100.1: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>ping winserver

Pinging WINSERVER.vvv-Wymbrits.local [192.168.100.1] with 32 bytes of
data:

Reply from 192.168.100.1: bytes=32 time<1ms TTL=128
Reply from 192.168.100.1: bytes=32 time<1ms TTL=128
Reply from 192.168.100.1: bytes=32 time<1ms TTL=128
Reply from 192.168.100.1: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
 
Back
Top