Re: Does this sound like a bad nic?

Tech-Archive recommends: Speed Up your PC by fixing your registry

On Aug 5, 6:07 pm, "Merv Porter [SBS-MVP]"
<mwport@xxxxxxxxxxxxxxxxxxx> wrote:
Is the Linux box a web server?

--
Merv  Porter   [SBS-MVP]
============================

"Nick Mirro" <nickmi...@xxxxxxxxx> wrote in message

news:ee7382c3-3ebb-43d2-a645-2ce68767f1fc@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Aug 5, 4:20 pm, "Merv Porter [SBS-MVP]"



<mwport@xxxxxxxxxxxxxxxxxxx> wrote:
You appear to have 3 public IPs set up on your external NIC. Is this by
design?

Normally, in an SBS network, a 2 NIC scenario would look
like:http://www.smallbizserver.net/Articles/tabid/266/articleType/ArticleV...

--
Merv Porter [SBS-MVP]
============================

"Nick Mirro" <nickmi...@xxxxxxxxx> wrote in message

news:633f2fac-417b-4998-9a60-99dadbc3c98e@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Aug 5, 9:21 am, Jim Behning SBS MVP

<jimbehn...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
On Tue, 4 Aug 2009 16:35:33 -0700 (PDT), Nick Mirro

<nickmi...@xxxxxxxxx> wrote:
On Aug 4, 6:10 pm, Nick Mirro <nickmi...@xxxxxxxxx> wrote:
On Aug 4, 5:46 pm, Nick Mirro <nickmi...@xxxxxxxxx> wrote:

On Aug 4, 4:27 pm, "Dave Nickason [SBS MVP]"

<gwdib...@xxxxxxxxxxxxxxxxxxxxxx> wrote:
To start with, what errors are you seeing in your system and
application
logs?

Can you please provide some more information about your setup and
how you're
using VPN and RDP? Do you have ISA? Do you normally run with one
NIC or
two? Any other connectivity issues, or does everything else seem
to
be
working normally? What's the exact error message or other result
when VPN
or RDP fail to connect? After the server reboots, are all the
expected
services running, or does something fail to start? When you are
at
a client
PC and are unable to connect to the SBS using RDP, can you ping
the
server,
see shares, and otherwise access server resources as expected?

Have you checked to see if there's a diagnostic utility offered
for
the NIC?

"Nick Mirro" <nickmi...@xxxxxxxxx> wrote in message

news:ce1f0b05-515a-4a82-a0c7-5b78b951912c@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Hi. Our vpn and rdp both fail whenever the sbs 03 server is
rebooted.
It was intermittent but now is predictable.

(There are 2 nics, one built into the mb and another pci. -
Normally,
the terminal server connection is set to use 'all' devices with
the
protocol.)

To resolve it, I first delete/recreate the TS connection. If I
set
the TS connection to use the built-in card, rdp works within
the
network (that cards physical connection) but of course the vpn
and
remote rdp don't work.

Setting it back to "all" nics does not resolve it until I have
repeated a few deletion/recreations of the connection and
reboots.
Does this sound like a bad nic? I don't have a spare on hand to
test
with.- Hide quoted text -

- Show quoted text -

Thanks for helping. Yes we are running ISA. Normally we use two
nic's, one to the cablemodem and the other to a lan/wireless
switch.
There is no diagnostic utility available for the installed nic's..
Just swapped out the ethernet cables and they were fine.

Rdp connection error: "This computer can't connect to the remote
computer. Try again... "

Rdp won't work locally or remotely. Regular internet traffic is
normal from all machines. Exchange still works within the network
(over the wired and wireless).

Here are 2 errors:

Event Type: Warning
Event Source: Microsoft ISA Server Web Proxy
Event Category: None
Event ID: 14148
Date: 8/4/2009
Time: 3:35:25 PM
User: N/A
Computer: HALBERT-SBS
Description:
The Web Proxy filter failed to bind its socket to 67.78.36.243 port
443. This may have been caused by another service that is already
using the same port or by a network adapter that is not functional.
To
resolve this issue, restart the Microsoft Firewall service. The
error
code specified in the data area of the event properties indicates
the
cause of the failure.

For more information, see Help and Support Center
athttp://go.microsoft.com/fwlink/events.asp.
Data:
0000: 1d 27 07 80 .'.?

Event Type: Error
Event Source: TermService
Event Category: None
Event ID: 1036
Date: 8/4/2009
Time: 3:35:44 PM
User: N/A
Computer: HALBERT-SBS
Description:
Terminal Server session creation failed. The relevant status code
was
0x2740.

For more information, see Help and Support Center
athttp://go.microsoft.com/fwlink/events.asp.-Hidequotedtext-

- Show quoted text -

Here is some info from the registry based on this article:

http://support.microsoft.com/kb/555382

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-
E325-11CE-BFC1-08002BE10318}\{1E29B5A3-229C-4122-AF31-81E17E1DB710}

There are 3 keys like this. Each has a "Connection" subkey. They have
the names:

Server Area Connection
Local Area Connection2
Local Area Connection

In "Network Connections" Server Area Connection is bound to the PCI
nic. There is no listing here for "Local Area Connection2."- Hide
quoted text -

- Show quoted text -

I apologize for replying to my own post. No edit ability here.

The connection is working again. This time the steps were pinned
down.

1. Disable TS connection
2. Disconnect both ethernet cables
3. Restart server
4. Restart TS connection
5. Reconnect both ethernet cables

Does this shed any light on things. Thanks again for any help.

Nick

No but ipconfig/all from server and workstation might.
See what SBS support is working
onhttp://blogs.technet.com/sbs/default.aspx
Check your SBS with the SBS Best Practices
Analyzerhttp://blogs.technet.com/sbs/archive/tags/BPA/default.aspx-Hide
quoted text -

- Show quoted text -

Here is ipconfig from a workstation:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\documents and settings\dr mirro\my documents>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : halbert3
Primary Dns Suffix . . . . . . . : MirroSoft.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : MirroSoft.local
MirroSoft.local

Ethernet adapter Linksys Wireless-N:

Connection-specific DNS Suffix . : MirroSoft.local
Description . . . . . . . . . . . : Linksys Wireless-N PCI
Adapter WMP30
0N #2
Physical Address. . . . . . . . . : 00-18-39-11-51-C5
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.24
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.103
DHCP Server . . . . . . . . . . . : 192.168.0.103
DNS Servers . . . . . . . . . . . : 192.168.0.103
Primary WINS Server . . . . . . . : 192.168.0.103
Lease Obtained. . . . . . . . . . : Sunday, August 02, 2009
9:09:13 AM
Lease Expires . . . . . . . . . . : Monday, August 10, 2009
9:09:13 AM

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-
E Gigabit
Ethernet Controller
Physical Address. . . . . . . . . : 00-1E-8C-89-77-94

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Bluetooth Device (Personal
Area Netw
ork)
Physical Address. . . . . . . . . : 00-12-5A-9C-FE-3E

and here it is from the server

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\documents and settings\dr mirro\my documents>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : HALBERT-SBS
Primary Dns Suffix . . . . . . . : MirroSoft.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : MirroSoft.local

PPP adapter RAS Server (Dial In) Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.19
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet
Adapter
Physical Address. . . . . . . . . : 00-50-8D-6A-4D-7F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.103
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.0.103
Primary WINS Server . . . . . . . : 192.168.0.103

Ethernet

...

read more »- Hide quoted text -

- Show quoted text -

Yes. It uses apache. A few website run from it. Also ftp, its own
mail and ssh.
.

Relevant Pages

  • Re: Cannot connect client to server 2003
    ... you need to reconfigure the IP schema of your SBS ... On the SBS 2003 Server open the Server Management console. ... On the Connection Type page, click Broadband, and then click Next. ... Alternate DNS server, type the IP addresses that are provided by your ISP ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... seleting full time broadband connection. ... Les Connor [SBS Community Member - SBS MVP] ... check the router as well and unless I missed a firewall setting on it, ... Anyway the Server Ipconfig /all is this... ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... it certainly appears to be something about the SBS configuration. ... Meridian.local Ethernet adapter Local Area Connection: ... Windows SMALL BUSINESS SERVER 2003 Windows IP Configuration ... 192.168.254.254) directly to a port on the router and then ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Anyway the Server Ipconfig /all is this... ... Server Local Area Connection: ... Les Connor [SBS Community Member - SBS MVP] ... First Page of the Internet Connection Wizard, ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... it certainly appears to be something about the SBS configuration. ... Meridian.local Ethernet adapter Local Area Connection: ... Windows SMALL BUSINESS SERVER 2003 Windows IP Configuration ... 192.168.254.254) directly to a port on the router and then ...
    (microsoft.public.windows.server.sbs)