This is possible, on my lynksys the DHCP range of addresses starts at 192.168.1.100, the lynksys has IP 192.168.1.1, so 192.168.1.2 - 192.168.1.99 are available for static devices, choose any of these and that should be fine.

Right.
As long as you choose an IP address that is out of the DHCP scope of the router (but still within the same subnet, obviously), you shouldn't have an address conflict.

Excellent. If I remember correctly we have 3 free static IP addresses. I'll try one of those first chance I get.

I'll do that just as soon as I can, maybe tomorrow or day after, but soon.

I'll post my results just as soon as I get that done.

Thanks for your help...hope it works.

Give it a shot and keep us posted.

Well guys, we tried assigning a static IP, no luck, or we did it wrong.

So it looks like my company is going to spring for a tech guy to address other company needs as well as my computer.

All your help was appreciated.

I'll leave this thread open, just incase one of you gets a fresh idea, because there is no telling how long before we get someone in here.

You sure you haven't got a two hour lease on your DHCP settings. If the renewal is syncronised the server may time out on an increase of traffic at that time. Check it out and increase it as required.

Could it be a power problem on the router, although I'm clutching at straws there.

Let us know the problem if the tech guy fixes it, it sounds interesting.

Our DHCP settings are set to zero which is to be equal to all day/24hrs., never the less we went ahead and assigned to 1,440 min./24hrs. to see if that would make a difference...nope.

Nothing seems to make a difference.

Looks like I have no choice but to wait for my company to bring outside help...wonder when that will be.

I'm still hoping someone out there might have a solution, so feel free to keep them coming.

You might want to have a look in your application and system logs to see if whatever is causing this is also logging some indication of its activity there.

Use the Event Viewer utility in your Administrative Tools folder to display the logs and let us know if you find any possibly relevant messages in them.

Here is what I found in the event viewer under system right after losing and regaining connection that seem to relate to each other

1st: Source MRxSmb
(The redirector failed to determine the connection type)This message appears 11 times in the hr. prior up to ten minutes before loss of network connection.

Then at the point I lose my network connection, these are the messages I get.
2nd Source: E100B
Adapter Intel(R) PRO/100 VM Network Connection #2: Adapter Link Down

3rd Source TCIP
The system detected that network adapter \DEVICE\TCPIP_{EB2F07B5-DCF3-4ADD-98B0-F247FE64F82A} was disconnected from the network, and the adapter's network configuration has been released. If the network adapter was not disconnected, this may indicate that it has malfunctioned. Please contact your vendor for updated drivers.

4rth Source Dnsapi With a Waring Icon
The system failed to update and remove host (A) resource records (RRs) for network adapter
with settings:

Adapter Name : {EB2F07B5-DCF3-4ADD-98B0-F247FE64F82A}
Host Name : robert
Primary Domain Suffix : crcbakcorp.com
DNS server list :
192.168.1.10, 206.13.29.12, 206.13.30.12
Sent update to server : 192.1.1.1
IP Address(es) :
192.168.1.100

The reason the update request failed was because of a system problem. For specific error code, see the record data displayed below.

0000: 51 27 00 00 Q'..

5th Source E100B
Adapter Intel(R) PRO/100 VM Network Connection #2: Adapter Link Up

6th Source TCIP
The system detected that network adapter \DEVICE\TCPIP_{EB2F07B5-DCF3-4ADD-98B0-F247FE64F82A} was connected to the network, and has initiated normal operation over the network adapter.

7th and final one - Source DCHP With Error Icon
The IP address lease 192.168.1.100 for the Network Card with network address 0008027DDC84 has been denied by the DHCP server 192.168.1.1 (The DHCP Server sent a DHCPNACK message).

All this happened inside of 1 second.

Thanks for the details. Information on the "MRxSmb" log entry and possible fixes for the problem can be found in some of the following links:

http://www.google.com/search?hl=en&l...22&btnG=Search

Messages #2 - #4 are cascading results of the error indicated in the initial MRxSmb message, messages 5 & 6 are the result of your system trying to recover fron the initial error and reconnect to the DHCP server (the router in this case), and message 7 indicates that the router is rejecting that request.


Earlier, you posted:
You should try that again, and this time also disable the DHCP client service on the machine in question when you do. I can post details on that later (I don't have time right now), but unless your network card or perhaps the router have gotten confuzzled (yes, "confuzzled" is a valid technical term), this really sounds like a DHCP issue.