 |
|
|
|
|
|
|
 |
08-11-2007, 12:36 PM
|
#1
|
|
Guest
|
Problem with *one* NAT translation
Have a BMgr 3.8 box with NAT working successfully for two out of three secondary addresses bound to the public interface. Have had the two nat-ed addresses working successfully for a couple of years, just added a new device that needs to be accessible from the public side.
I bound the new public IP to the public interface on the BM box; it is right in the same list with the other two, it is in the same range as them (actually right between them), so no problems with being on a diff. network. Set the NAT translation identical to the other two (just diff. addresses, of course), rebooted the server. Could not ping the new public IP from the public side. Went physically off site and could not access the new device. Checked bindings again, checked NAT again, rebooted server again, checked bindings/NAT again, everything looks perfect except for the fact that it doesn't work.
All devices are on the same switches/wires, so if I can ping one, I should be able to ping the other two. There's only one router with one set of access rules, so it's all for one and one for all. I can access the device just fine from on site, but zero access from off site.
Thanks for any help!
tony
|
|
|
|
08-11-2007, 12:55 PM
|
#2
|
|
Guest
|
Re: NEVER MIND Problem with *one* NAT translation
Sheesh...would help if I would read the other posts first and remember what to check. You know, if Novell products were like the "other guys" and would constantly suffer corrupt/missing files and otherwise break and need to be reinstalled, I'd remember all this...it's that dratted 654 days consecutive uptime that kills me every time...
tony
>>> Anthony Shaffer<tony@not.myrealaddress.com> 8/11/2007 11:36 AM >>>
Have a BMgr 3.8 box with NAT working successfully for two out of three secondary addresses bound to the public interface. Have had the two nat-ed addresses working successfully for a couple of years, just added a new device that needs to be accessible from the public side.
I bound the new public IP to the public interface on the BM box; it is right in the same list with the other two, it is in the same range as them (actually right between them), so no problems with being on a diff. network. Set the NAT translation identical to the other two (just diff. addresses, of course), rebooted the server. Could not ping the new public IP from the public side. Went physically off site and could not access the new device. Checked bindings again, checked NAT again, rebooted server again, checked bindings/NAT again, everything looks perfect except for the fact that it doesn't work.
All devices are on the same switches/wires, so if I can ping one, I should be able to ping the other two. There's only one router with one set of access rules, so it's all for one and one for all. I can access the device just fine from on site, but zero access from off site.
Thanks for any help!
tony
|
|
|
|
08-30-2007, 01:20 PM
|
#3
|
|
Guest
|
Re: NEVER MIND Problem with *one* NAT translation
In article <BZkvi.241$pG6.193@prv-forum2.provo.novell.com>, Anthony Shaffer
wrote:
> .it's that dratted 654 days consecutive uptime that kills me every time..
>
Does tend to make one forget how it was configured!
Did you happen to get a screenshot of the uptime?
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
Adobe Newsgroups | Software Newsgroups
Powered by: vBulletin Version 3.0.7 Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.
© 2003-2004 All Rights Reserved GroupBrowser LLC.
|
 |