Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

I.P. problem

Status
Not open for further replies.

shannanl

IS-IT--Management
Apr 24, 2003
1,071
US
I have a computer at work that has 2 nics in it. One is set up for the LAN and the other is set up for a small network of printers and other stuff. They are on different subnets, etc. Everything works fine with this arrangement except for one thing. Every now and then the computer's lan connection stops working. The i.p., gateway and dns, etc. are all in there and can be viewed by ipconfig. All the settings seem fine but it will not connect to the LAN. Simply changing the i.p. address to another and changing it back to its original will cause the connection to start working again. There seems to be no pattern as to when it stops. It is completely random.

Any suggestions would be greatly appreciated.

Shannan
 
Every single power manage feature on MOBO and all cards is disabled. Not sure what the subnet needs to be but it was on 255.255.255.0 and was doing same thing new subnet didnt seem to do anything
 
okay new update

Isolated it down to the router basically everything works on the LAN, IIS RDP everything.

As soon as you try to access IIS or RDP from the WAN then it fails.

If you try to access IIS or RDP from the LAN on that IP it will all pull up just fine.

The funny thing is RDP and all other services work on that router going to different ips, only that one specific IP is jammed for the router. If I reboot the router it works again. What can this be is it a SPI Firewall
 
Hmm okay NOT the routers, took them both off and it still happens so its some kind of conflict with the 2 cards in on e box.

They dont share IRQs

Windows IP Configuration

Host Name . . . . . . . . . . . . : webserver
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : jewelry4cars

Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Compaq NC3121 Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-08-C7-2A-C6-6B
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.105
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : jewelry4cars
Description . . . . . . . . . . . : 3Com 3C920B-EMB-WNM Integrated Fast Ether
net Controller
Physical Address. . . . . . . . . : 00-0E-A6-C0-69-5D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 142.179.114.60
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . : 142.179.114.60
DHCP Server . . . . . . . . . . . : 64.114.195.133
DNS Servers . . . . . . . . . . . : 154.11.128.187
154.11.128.59
Lease Obtained. . . . . . . . . . : Tuesday, August 15, 2006 7:03:11 AM
Lease Expires . . . . . . . . . . : Tuesday, August 22, 2006 7:03:11 AM

----

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 08 c7 2a c6 6b ...... Compaq NC3121 Fast Ethernet NIC
0x10004 ...00 0e a6 c0 69 5d ...... 3Com 3C920B-EMB-WNM Integrated Fast Ethernet
Controller
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 142.179.114.60 142.179.114.60 10
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.105 10
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
142.179.112.0 255.255.252.0 142.179.114.60 142.179.114.60 10
142.179.114.60 255.255.255.255 127.0.0.1 127.0.0.1 10
142.179.255.255 255.255.255.255 142.179.114.60 142.179.114.60 10
192.168.0.0 255.255.255.0 192.168.0.105 192.168.0.105 10
192.168.0.105 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.0.255 255.255.255.255 192.168.0.105 192.168.0.105 10
224.0.0.0 240.0.0.0 142.179.114.60 142.179.114.60 10
224.0.0.0 240.0.0.0 192.168.0.105 192.168.0.105 10
255.255.255.255 255.255.255.255 142.179.114.60 142.179.114.60 1
255.255.255.255 255.255.255.255 192.168.0.105 192.168.0.105 1
Default Gateway: 192.168.0.1
===========================================================================
Persistent Routes:
None

Any ideas on why this config would randomly go down?
 
Did we not much earlier discuss the problems related to having automatic metrics?

Set manual metrics on both adapters.

 
This is how it works

Telus gives me 2 ips through DHCP which are static DCHP ips

Telus ADSL Model
Crossover into a HUB
Hub -> Router - pulls Ip1 - > Nic #1
Description . . . . . . . . . . . : Compaq NC3121 Fast
Physical Address. . . . . . . . . : 00-08-C7-2A-C6-6B
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.105
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1


Hub -> Nic#2 - pulls Ip2
Physical Address. . . . . . . . . : 00-0E-A6-C0-69-5D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 142.179.114.60
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . : 142.179.114.60
DHCP Server . . . . . . . . . . . : 64.114.195.133
DNS Servers . . . . . . . . . . . : 154.11.128.187
154.11.128.59

All nics and gateways are set to 10 metering as you can see in the routing table.


 
To further explain these 2 nics each serve 1 website on IIS
each needs its own IP for HTTPS. So both sites work just fine for hours under http and https then will just go down randomly and need a reboot.

When its just ONE nic the site never goes down for months. As soon as I added the HUB and second NIC, now it randomly locks up.
 
I want the route to be the way it comes in is the way it goes out.

Ie

HTTP request on NIC#1 - > IIS -> OUT NIC#1

HTTP request on NIC#2 -> IIS -> OUT NIC#2

So I dont want either one to be dominant.
 
And it doesnt explain why it all work for 8 hours then all of a sudden doesn't
 
You are not making a great deal of sense. Why would adjusting the metrics change what interface responded to a request?

 
I am not looking at changing the metrics. Your the one who brought it up as a potential problem if metrics are equal. But in this case there are 2 gateways each with a 10. So since they dont share gateways the metics shouldn't make any differnce.

 
Thanks its not the metrics anyways, unless I have to put both nics on the same subnet and set 1 as as the default gateway OUT is all I can think of
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top