[masky]

Hello, I am new here and I need big help. I have this problem at the office.

The PC going out to internet is connected thru a modem/router, internet connection exists, but i have problems where it loses signal after some time, then it will be down. i have a static IP provided by my ISP and am using it to go out, eg x.x.x.33, problem is this pc is running the internal mail server software, and i run a dns check to find out that mail.myoffice.com.xx points to x.x.x.33, does this means this PC running the internal mail software must go out thru x.x.x.33? I ran the internet thru another PC standalone, without any problems at all, so couldnt be the internet line problem. thing is with the former PC running the mail, it works fine connected to internet and after some time, voila, there's no signal at all, but i am still connected.
could it be the internet network settings, or the network card problem? but what i dont understand is, it works fine for some time before going kapoot on me, or is there such thing as a timer set to it?

Real blurred!

[Advertisements]

when an isp assigns you a static ip...that ip is for your modem...so if they gave you say 192.168.2.42 as your static ip...that's what your modem's ip is....on the inside of the network..your ip can be anything you want it to be...and internally usually desktops are dhcp assigned ips and servers are static...soo

in your situation

your modem's ip is xxx.xxx.xxx.33....your mailserver's ip should be a static ip...any ip as long as it's on your network range internally....then in the router you need to set up a translation rule to translate the .33 ip, directly to the correct port (depends on your mail protocol) for the server's ip....that way all traffic coming in that is let's say smpt traffic...will automatically get picked up by the router and sent directly to the server

i'm suspecting that right now what's happening is that your modem's ip is .33 but you also set the server's ip to .33 the reason the connection is dropping is because you have two devices on the same network with the same ip..

[dsenette]

when an isp assigns you a static ip...that ip is for your modem...so if they gave you say 192.168.2.42 as your static ip...that's what your modem's ip is....on the inside of the network..your ip can be anything you want it to be...and internally usually desktops are dhcp assigned ips and servers are static...soo

in your situation

your modem's ip is xxx.xxx.xxx.33....your mailserver's ip should be a static ip...any ip as long as it's on your network range internally....then in the router you need to set up a translation rule to translate the .33 ip, directly to the correct port (depends on your mail protocol) for the server's ip....that way all traffic coming in that is let's say smpt traffic...will automatically get picked up by the router and sent directly to the server

i'm suspecting that right now what's happening is that your modem's ip is .33 but you also set the server's ip to .33 the reason the connection is dropping is because you have two devices on the same network with the same ip..

[masky]

Thks for your reply dsenette. Funny thing is the internet is running fine during work hours and signal most of the time dies after work hours, when I come in next morning, its dead, but internet still connected. I am running Surgemail in my internal mail server and I did a dns check on my domain, I see the MX records for the mail points to eg. 202.222.22.66 which is a 1 of the 5 static IP provided by my ISP, does this means this mail server must go out to the internet at 66? or I could use another static IP to go out and still get the mail server running??? Or could it be the timeout for the internet after work hours is set by a domain controller in the office? The domain controller is running Win2000 Server, is there such a setting where it cuts off the signal?? Problem is I am real blur, the previous guy left without providing any documentation or structure of the network in the office, so I am the guinea pig now.

Any reply appreciated.

Thanks again dsenette.