trouble to access web base

[kayjaig]

i have trouble to access the web base (XP is used). IP is correct, printing has no problem.

[Llama God]

Haven't you asked the same question here: http://www.copytechnet.com/forums/ri...se-3035-a.html

That should help, but log in as supervisor and you can change the administrator passwords.

[kayjaig]

correction for the question.

thanks llama,
what i mean for this one is the web page cannot display.
it shows web page error.
please advice.

[Llama God]

Ok, try pinging the device, then unplug it and try pinging it again in case it's a duplicate IP.

I take it that you can access other webpages from the PC? What is the device plugged into, eg a Cat5 point on the wall, a switch etc...?

[aabarnes1]

web access

sp 582891 enables web monitor-make sure this is set to 1

[imaginemoko]

what model are we talking about Sir?

[Jomama46]

Try turning off any firewalls,i.e. Nortons, Macafee, etc.

[iMind]

Try turning off any firewalls,i.e. Nortons, Macafee, etc.

[KopyKat]

This may sound odd but I ran up against this with one of my customers just last month. I was trying to do some phone support and he had printed out the config page to get the IP addy. It was something like 192.168.110.050. He was entering it exactly as printed on the config page and could not access the Web interface...it would come up with a search page. WTF?? So I had him enter it as 192.168.110.50 (leaving out that extra '0' before 50) and it worked just fine. Don't ask me why. I have since tried it both ways on different networks and some work either way and some don't.

[Jomama46]

This may sound odd but I ran up against this with one of my customers just last month. I was trying to do some phone support and he had printed out the config page to get the IP addy. It was something like 192.168.110.050. He was entering it exactly as printed on the config page and could not access the Web interface...it would come up with a search page. WTF?? So I had him enter it as 192.168.110.50 (leaving out that extra '0' before 50) and it worked just fine. Don't ask me why. I have since tried it both ways on different networks and some work either way and some don't.

I have run into this too, with Win2K and XP. For some reason( and not always) an OS will interpret a 3 digit octet as a hex number instead of binary. WTF?